Expand description
§Rocket I18N
A crate to help you internationalize your Rocket or Actix Web applications.
It just selects the correct locale for each request, and return the corresponding gettext::Catalog.
§Usage
First add it to your Cargo.toml:
[dependencies]
rocket_i18n = "0.4"
gettext-macros = "0.1" # Provides proc-macros to manage translationsThen, in your main.rs:
use gettext_macros::{compile_i18n, include_i18n, init_i18n};
init_i18n!("my_web_app", en, eo, it, pl);
fn main() {
rocket::ignite()
// Make Rocket manage your translations.
.manage(include_i18n!());
// Register routes, etc
}
compile_i18n!();Then in all your requests you’ll be able to use the i18n macro to translate anything.
It takes a gettext::Catalog and a string to translate as argument.
use gettext_macros::i18n;
use rocket_i18n::I18n;
#[get("/")]
fn route(i18n: I18n) -> &str {
i18n!(i18n.catalog, "Hello, world!")
}For strings that may have a plural form, just add the plural and the number of element to the arguments
i18n!(i18n.catalog, "One new message", "{0} new messages", 42);Any extra argument, after a ;, will be used for formatting.
let user_name = "Alex";
i18n!(i18n.catalog, "Hello {0}!"; user_name);When using it with plural, {0} will be the number of elements, and other arguments will start
at {1}.
Because of its design, rocket_i18n is only compatible with askama, ructe or compiled templates
in general.
You can use the t macro in your templates, as long as they have a field called catalog to
store your catalog.
Macros§
- Works the same way as
gettext_macros::i18n, but without needing to give agettext::Catalogas first argument.
Structs§
- Catalog represents a set of translation strings parsed out of one MO file.
- A request guard to get the right translation catalog for the current request.
- ParseOptions allows setting options for parsing MO catalogs.
Enums§
- Represents an error encountered while parsing an MO file.
Functions§
- Loads translations at runtime. Usually used with
rocket::Rocket::manage.