According to the CLDR documentation, we can specify a region overriding the region specified in the language identifier.

Does Globalize support this extension?

If yes, any help would be greatly appreciated.

Reproduction steps:

have a localization file, e.g. active.en.toml, with the content Test = "" and run the following command in your terminal in the appropriate directory:

goi18n merge active.*.toml

to generate your updated translate.*.toml files.

Analysis

The execution of the above mentioned command will cause a nil reference exception here
https://github.com/nick

Currently, DayPeriodFormatter only uses a locale's language code to determine the day period string. However, some rule sets have regional variations, such as es_cO, for "Spanish (Colombia)". These should be selected for matching locales.

This should be as straightforward as changing the current implementation to make two checks, first with and then without the region code. The only real tr

This should work:

cat test.txt | unic-inspector

Reading https://www.elastic.co/blog/boosting-the-power-of-elasticsearch-with-synonyms - we quickly see Emoji Search can benefit from the new POST /synonym_test/_reload_search_analyzers API.

Index-time synonyms have several disadvantages:

• The index might get bigger, because all synonyms must be indexed.
• Search scoring, which relies on term statistics, might suffer because synon

ICanBoogie\CLDR\Locale::format_list should accept pattern type only. One can use a non-localized ListFormatter with list patterns, the localized version should accept types only.

tl;dr: Let’s improve the docs! Please add doc requests or suggestions in the comments here.

The first goal of this project was to implement the standardized Unicode CLDR–based localized number formatting defined in UTS #35, Part 3: Numbers. Much of the CLDR::Number documentation, however, does not go into detail to describe functionalit