syeopite / lens Goto Github PK

I18next is another popular standard translation format. It's features includes:

• Plurals
• Interpolation
• Formatting
• Nesting
• Objects and arrays

So, I think it's a good candidate for next major backend Lens implements. Perhaps in 0.2?

In Lens, each of the backends currently have a slightly different behavior.

For instance, the Gettext family of backends returns the given ID when a translation is not found.

backend = Gettext::MOBackend.new("locales")
catalogue_hash = backend.create()
catalogue = catalogue_hash["en_US"]
catalogue.gettext("I don't exist") # => "I don't exist" 

Whereas the RubyI18n YAML backend would raise an LensExceptions::MissingTranslation

catalogue = RubyI18n::Yaml.new("locales")
catalogue.translate("en", "I  also don't exist") # => LensExceptions::MissingTranslation

Not to mention the fact that Gettext requires creating a catalogue object first while the other doesn't.

This discrepancy is intentional, in order to preserve the behaviors seen in their reference or intended implementations.

However, I do see merit in a potential way to configure these behaviors. It wouldn't change the API differences, but it would help resolve any unintended errors a developer might experience when swapping backends.

The basic infrastructure for implementing number formatting was introduced in Lens with commit 5997047. Since then, almost all features needed to format a number has been added. In fact, the formatter is actually present and working:

In commit 7e2d9f1 of master, this code produces the expected output of 10,00,00,000.124

rules, metadata = CLDR::Numbers::PatternParser.new("#,##0.##").parse
formatter = CLDR::Numbers::PatternFormatter(CLDR::Languages::EN).new(rules, metadata)

formatter.format(1000.129) # => 1,000.13
formatter.format(-1000.129) # => -1,000.13

However, despite all this there's still quite a few crucial features missing.

• Explicit plus signs and negative patterns
• Prefixes
• Suffixes
• Minimum grouping digits
• Significant digits
• Scientific notations
• Rounding
• Padding
• Currency symbols
• Fractional grouping

A better public API should then be constructed before we can push it out to version 0.2.