Load The Translations

Loading all those translations is the role of the load_locales! macro, just call this macro anywhere in your codebase and it will generate the code needed to use your translations.

#![allow(unused)]
fn main() {
// lib.rs/main.rs

leptos_i18n::load_locales!();
}

The i18n module

The macro will generate a module called i18n, this module contain everything you need you use your translations.

The Locale enum

You can find the enum Locale in this module, it represent all the locales you declared, for example this configuration:

[package.metadata.leptos-i18n]
default = "en"
locales = ["en", "fr"]

Generate this enum:

#![allow(unused)]
fn main() {
#[derive(Copy, Clone, Debug, Hash, PartialEq, Eq, Default)]
#[allow(non_camel_case_types)]
pub enum Locale {
    #[default]
    en,
    fr
}
}

The I18nKeys struct

This generated struct represent the structure of your translations, with each translation key being a key in this struct.

It contain an associated constant for each locale, where every field is populated with the values for the locale.

en.json

{
  "hello_world": "Hello World!"
}

fr.json

{
  "hello_world": "Bonjour le Monde!"
}

This will generate this struct:

#![allow(unused)]
fn main() {
pub struct I18nKeys {
  pub hello_world: &'static str,
}

impl I18nKeys {
  const en: Self = I18nKeys { hello_world: "Hello World!" };
  const fr: Self = I18nKeys { hello_world: "Bonjour le Monde!" };
}

```rust
leptos_i18n::load_locales!();

assert_eq!(i18n::I18nKeys::en.hello_world, "Hello World!");
assert_eq!(i18n::I18nKeys::fr.hello_world, "Bonjour le Monde!");
}

This way of accessing the values is possible but it's not practical and most importantly not reactive, we will cover the t! macro later, which let you access the values based on the context:

#![allow(unused)]
fn main() {
t!(i18n, hello_world)
}