Konstantin Haase
Konstantin Haase
Would you consider merging this into the [sinatra-contrib](https://github.com/sinatra/sinatra-contrib) an option? I really would like to promote it as a sane alternative to the wide-spread rack-flash.
* [x] Implement Parser * [ ] Implement Compiler * [x] Message Definition * [x] Attribute Definition * [x] Term Definition * [x] Function Call * [x] Number Literals *...
Luxembourgish needs more advanced logic for formatting a list (similar to Spanish/Hebrew). Expected: ``` ruby nii = Nii::Context.new :lb nii.format [1, 2] # => "1 an 2" nii.format ["du", "ech"]...
It would be great to support alternative Ruby implementations. But we're not compatible at the moment. A couple of modern Ruby features we use: • Better Unicode support (including relying...
It would be nice if inline translations were supported as well: ``` slim .example ${first-message} • ${second-message} ```
Both i18n and fast_gettext implement support for a database backend. Not sure which version we should target this for. Ideally this would be independent of the ORM used.
I've been thinking about adding a CLI. Features I can envision: * Sync messages between two locales (ie, copy all existing message keys with comments from English to another language)....
To reduce special character usage, it would be nice to have an opt-in mode which will cause nii-slim to attempt to translate any text content, not just the content prefixed...
Right now the only way to not trigger automatic formatting is either by explicitly formatting the value (which might still insert BiDI Unicode markers, but that shouldn't be an issue),...