cargo-i18n
cargo-i18n copied to clipboard
A Rust Cargo sub-command and libraries to extract and build localization resources to embed in your application/library
Consider making this optional? Consider this situation more carefully.
Different localization systems may have different representations for locale/language ids. Such as https://github.com/unicode-org/icu4x/tree/main/components/locid
I have a crate that contains several modules for which I want to embed the localization resources Suppose my crate is structured as: -- lib.rs -- mod1 ---- file1.rs I...
Observed on macOS Catalina and Big Sur, when the `LC_CTYPE` envrionment variable is set to `UTF-8` (seems like a default for macOS, at least in the terminal application). The DesktopRequester...
When I compiled my app on Linux(both Debug and Release) or Windows(only Release), then everything works fine. But when I started to use debug Windows builds(without any code change, except...
Right now the current language is set at application level. This causes tests to fail (#48) and makes it impossible to change languages for a single thread or worker (#59)....
This is an alternative implementation for #59 and is based on the code from #84. This PR adds a single new method: - lang This methods allows creating a shallow...
Provide a localization method that accepts strings coming from a dictionary via a `serde`, [nanoserde](https://github.com/not-fl3/nanoserde), [miniserde](https://github.com/dtolnay/miniserde), [microserde](https://github.com/cloudhead/microserde) format such as `json`, `yaml`, `toml`, `ron`, etc. Or perhaps also some binary...
It would be nice to have some kind of localization change tracking tool/library for fluent that can indicate when messages are out of date. Related to #31 Related to #83
This way cargo-i18n can also function a bit like a linter/compiler, checking the validity message formatting before the application even runs.