i18n
i18n copied to clipboard
ruby-i18n
Internationalization (i18n) library for Ruby
### What are you trying to accomplish? A step towards CLDR pluralization. Ref: https://github.com/ruby-i18n/i18n/issues/629 Previously, I put forth [a PR](https://github.com/ruby-i18n/i18n/pull/630), that was reverted in #633 since dropping [incorrect] support for...
`ruby-i18n/i18n` should ship with a pluralization backend compatible with CLDR. Especially when the [README advertises](https://github.com/ruby-i18n/i18n/blob/master/README.md#features) it as such: The default `I18n::Backend::Pluralization` does not support CLDR's pluralization rules. Differences with the...
The [uppercase equivalent](https://www.compart.com/en/unicode/U+1E9E) of [the German Eszett](https://www.compart.com/en/unicode/U+00DF) was released in a much later version of Unicode and isn't included as part of the first 190 diacritics of unicode between `0xC0`...
## What I tried to do Using the `InterpolationCompiler` as described in https://github.com/ruby-i18n/i18n/blob/master/lib/i18n/backend/interpolation_compiler.rb#L13 stopped working with i18n v1.9.1 ## What I expected to happen Should not lead to raising an...
I started from an `InvalidPluralizationData` error in my rails app, and realized that it isn't using the CLDR plural rules like I thought it was. Then I came across https://github.com/svenfuchs/i18n/wiki/Pluralizations:...
I'm a gem/Rails engine author that is using `with_locale` to step as lightly as possible within the parent Rails application. I've found an unexpected problem: `18n.with_locale` will raise an exception...
For long time I have a code like this: ``` STATES = I18n.t('states').with_indifferent_access.freeze ``` The yaml file is in UTF-8 and it has accents in some words: ``` pt-BR: states:...
In my opinion `InvalidPluralizationData` error is a kind of `MissingTranslation` error. `I18n::Backend::Fallbacks` exist to avoid `MissingTranslation` error and I don't figure out why fallbacks does not work for `InvalidPluralizationData`. This...
## What I tried to do ```ruby # frozen_string_literal: true require "i18n" I18n.backend = I18n::Backend::Simple.new I18n.backend.store_translations(:en, foo: :bar, bar: "%{baz}") puts(I18n.t("foo", baz: "%{qux}")) ``` ## What I expected to happen...
Hello, I'm not sure how to categorise this, as if a bug or a feature request, but certainly it is a bit of a missed expectation of how the fallback...
