Luke Frisken
Luke Frisken
This may rely on some ideas in #31 to be completely valid. ```rust i18n::SOME_KEY.fmt(loader, arg1, arg2); i18n::SOME_KEY.ATTRIBUTE.fmt(loader); ``` This does however lose some of the readability of the named arguments...
Closed in favour of #100
While working on https://github.com/kellpossible/avalanche-report , it's very annoying to edit or update translations, it requires a recompile. When working with localizations in dynamic templates which support live reload (via https://docs.rs/minijinja-autoreload/latest/minijinja_autoreload/...
The 1.0 release has been made http://blog.unicode.org/2022/09/announcing-icu4x-10.html
https://github.com/unicode-org/message-format-wg
Even better would be to detect availability of clipboard at runtime instead of crashing or requiring a custom build?
I also ran into this problem mocking a production service, specifically a trait that returned a boxed `Stream` with a lifetime parameter.
Hi @VorpalBlade , which localization system are you planning to use? Currently this library only supports gettext and fluent
I haven't tested yet, to be sure but I think maybe locale number formatting functionality is not yet available in the Rust implementation of `fluent`? Anyway I think you could...
As for gettext, I'm not sure, I haven't given any thought to the question yet. We currently use https://github.com/rust-locale/locale_config/ for https://docs.rs/i18n-embed/latest/i18n_embed/struct.DesktopLanguageRequester.html implementation, so if that library supports `LC_NUMERIC` then we...