2 unstable releases

0.2.0 Jun 1, 2020
0.1.0 Feb 11, 2020

#228 in Internationalization (i18n)

Download history 27/week @ 2024-07-24 20/week @ 2024-07-31 12/week @ 2024-08-07 6/week @ 2024-08-14 2/week @ 2024-08-21 6/week @ 2024-08-28 5/week @ 2024-09-18 5/week @ 2024-09-25 5/week @ 2024-10-02 5/week @ 2024-10-09 20/week @ 2024-10-16 51/week @ 2024-10-23 23/week @ 2024-10-30 15/week @ 2024-11-06

110 downloads per month

MIT license

11KB
113 lines

ctl10n

ctl10n (compile time localization) provides you a simple way to embed messages into binary file without embedding them into source. Internally, ctl10n generates a simple macro_rules! macro tr!() from the provided a TOML file with strings.

Basic usage

Add ctl10n to your build-dependencies in your Cargo.toml. If you want to use include_strings you'll need it in dependencies as well.

[package]
name = "example"
version = "0.1"
edition = "2018"

[build-dependencies]
ctl10n = "0.1.0"

[dependencies]
ctl10n = "0.1.0"

Add the following to your build.rs:

use ctl10n;

fn main() {
    println!("cargo:rerun-if-changed=build.rs");
    println!("cargo:rerun-if-changed=strings.toml");
    if let Err(err) = ctl10n::convert_default_strings_file() {
        panic!("{}", err);
    }
}

This will generate the file $OUT_DIR/strings.rs from strings.toml. The TOML file with strings must be a table where all values are strings. Example strings.toml:

message = "Some message"
message-with-args = "Some message with {arg}"

You should include strings.rs somewhere (for example, in lib.rs) to use the generated macro. You can do this by calling the macro ctl10n::include_strings!() or manually, using include!(). After including the macro it can be used like this:

use ctl10n;

ctl10n::include_strings!();

fn main() {
    // `tr!()` with one argument will be translated to string literal
    println!(tr!("message"));
    println!(tr!("message-with-args"), arg = "foobar");
    // `tr!()` with multiple arguments will be translated to formatted `&String`
    println!("{}", tr!("message-with-args", arg = "foobaz"))
}

Output of this code (assuming strings.toml from above):

Some message
Some message with foobar
Some message with foobaz

Trying to use an unknown key or wrong format arguments is a compile-time error.

Multiple locales

You can use environment variables to provide a different locale at compile time:

use ctl10n;
use std::env;

fn main() {
    println!("cargo:rerun-if-changed=build.rs");
    println!("cargo:rerun-if-changed=locales/*.toml");
    if let Err(err) = ctl10n::convert_strings_file(
        format!(
            "locales/{}.toml",
            &env::var("LOCALE").unwrap_or("en".to_string())
        ),
        "strings.rs",
    ) {
        panic!("{}", err);
    }
}

LOCALE=de cargo build

Dependencies

~245–530KB
~11K SLoC