fluent-i18n

Crates.iofluent-i18n
lib.rsfluent-i18n
version0.1.0-rc.2
created_at2025-08-04 08:48:23.283942+00
updated_at2025-09-19 10:43:15.775762+00
descriptionA declarative and ergonomic internationalization for Rust using Fluent
homepagehttps://gitlab.archlinux.org/orhun/fluent-i18n
repositoryhttps://gitlab.archlinux.org/orhun/fluent-i18n
max_upload_size
id1780473
size98,585
Orhun ParmaksΔ±z (orhun)

documentation

https://docs.rs/fluent-i18n/

README

fluent-i18n πŸ—£οΈπŸ”₯

docs.rs Crates.io MSRV License: MIT License: Apache-2.0

A declarative and ergonomic internationalization for Rust using Fluent.

Built on top of fluent-templates and inspired by the simplicity of rust-i18n.

Features

Example

use fluent_i18n::{i18n, t};

i18n!("locales", fallback = "en-US");

println!("{}", t!("greeting"));
println!("{}", t!("welcome", { "name" => "Orhun" }));

Place your localization files in locales/en-US/main.ftl:

greeting = Hello, world!
welcome = Welcome, { $name }!

See the Fluent syntax for more details about FTL files.

Usage

Installation

Add fluent-i18n to your Cargo.toml:

cargo add fluent-i18n

Initialization

At the entry point of your application (e.g., main.rs or lib.rs), invoke the i18n!() macro to initialize the localization system:

i18n!("locales");

Or with a fallback locale:

i18n!("locales", fallback = "en-US");

This will expose a static loader named LOCALES that will be used by the t!() macro for translations throughout your application.

You can also dynamically change the locale at runtime using the set_locale() function:

use fluent_i18n::{set_locale, get_locale};

set_locale(Some("tr"))?;

let current_locale = get_locale()?;

Running set_locale(None) will detect the system locale automatically.

Lookup

To look up a translation for a given key, use the t!() macro:

t!("greeting");

With parameters:

t!("count-items", { "count" => 3 })
t!("key", { "arg1" => value1, "arg2" => value2 })

The given parameters should be one of the supported types.

Supported Types

The t!() macro interpolates values into the message using the ToFluentValue trait.

The following types implement the ToFluentValue trait:

  • String, &'static str, Cow<'static, str>
  • Integer and float primitives (usize, u32, i64, etc.)
  • Path, PathBuf
  • Option<T> where T implements ToFluentValue

You can extend support for your own types by implementing this trait:

use fluent_i18n::{FluentValue, ToFluentValue};

impl ToFluentValue for MyType {
    fn to_fluent_value(&self) -> FluentValue<'static> {
        FluentValue::from(self.to_string())
    }
}

Locale Layout

You can organize .ftl files per locale, and shared files like core.ftl will be included in all locales.

locales/
β”œβ”€β”€ core.ftl
β”œβ”€β”€ en-US/
β”‚   └── main.ftl
β”œβ”€β”€ fr/
β”‚   └── main.ftl
β”œβ”€β”€ zh-CN/
β”‚   └── main.ftl
└── zh-TW/
    └── main.ftl

The directory names should adhere to the Unicode Language Identifier. It also respects any .gitignore or .ignore files present.

See the Fluent syntax for more details about FTL files.

Testing

In tests, you can access the translations as usual without reinitialization:

use fluent_i18n::t;

#[test]
fn test_translation() {
    assert_eq!(t!("greeting"), "Hello, world!");
}

Debugging

When raw mode is enabled, translations will return the key itself instead of looking up the translation. This is useful for debugging purposes to see which keys are being requested.

use fluent_i18n::{t, set_raw_mode};

set_raw_mode(true);

let raw_message = t!("some-translation-key"); // "some-translation-key"

You could also follow this workflow for translating missing strings:

  • Run the program and navigate to the area you want to test.
  • Enable raw mode with set_raw_mode(true).
  • Look for untranslated output (the raw key will be shown instead of the translation).
  • Copy that key.
  • Search for it in the project.
  • Add the missing translation.

Security

Unicode directional isolate characters (U+2068, U+2069) are disabled as default to prevent potential security issues like bidirectional text attacks. This also gives clean output without unexpected characters in translations.

Also, please note that this is only applicable for mixed-script languages such as Arabic, Hebrew, and Persian.

License & Contributions

This project can be used under the terms of the Apache-2.0 or MIT. Contributions to this project, unless noted otherwise, are automatically licensed under the terms of both of those licenses.

πŸ¦€ γƒŽ( ΒΊ _ ΒΊ γƒŽ) - respect crables!

Feel free to open issues or PRs for improvements, bug fixes, or ideas!

Acknowledgements

This library was originally developed as part of the ALPM project and later extracted for general-purpose use.

Commit count: 0

cargo fmt