Some general first questions

[cw789]

Hi, looks very promising. We soon will start to be a consumer.

• default_locale why is the default en and not en-001?
• supported_locales using coverage-level keyword, I would more likely expect the results within effectiveCoverageLevels of coverageLevels.json - is this expectation just wrong?

[kipcole9]

@cw789, looking forward to supporting you if you adopt localize (and I hope you do). To answer your questions:

• I choose :en as the system, end of days, save me from myself locale because the commuting world - including Elixir - speaks American English. In addition, :en-001 does not have as complete data as :en either. I'm Australian, I'd pick :en-AU if it was up to me! Anyway, you can always configure config :localize, default_locale: :en in runtime.exs or call Localize.put_default_locale/1 at runtime if you prefer something else.
• The coverage level data is indeed sourced from coverageLevels.json. I have a build pipeline that does quite a lot of work to build the content that is ultimately consumed by localize, but that's the ultimate source for coverage levels.

[cw789]

• The coverage level data is indeed sourced from coverageLevels.json. I have a build pipeline that does quite a lot of work to build the content that is ultimately consumed by localize, but that's the ultimate source for coverage levels.

I need to clarify. As consumer I had the expextation to get around 400 locales for modern. The ones defined in effectiveCoverageLevels. Not just the parent around 100. But my expectation might be wrong.

[kipcole9]

:modern has 430 to be exact as of CLDR 48.2. And you are correct, CLDR clearly says that a locale inherits its coverage level from its parent locale. I have updated the code to do the expansion.

I will get a release out soon that correctly expands. Thanks for spotting that.

Anything else?

[cw789]

Anything else?

Not right now - no blockers to be found (now that even also the Decimal pad fractional digits is already solved).
It's all again very high quality, as I expected.

[kipcole9]

Allow me also to note the locale lookup process (documented in Localize.default_locale/0) in case you haven't seen it yet:

1. A value previously set via put_default_locale/1.

2. The LOCALIZE_DEFAULT_LOCALE environment variable.

3. The :default_locale key in the :localize application environment
   (e.g., config :localize, default_locale: :fr).

4. The LANG environment variable (e.g., "en_US.UTF-8"), with the charset
   suffix stripped.

5. :en as a final fallback.

And then the :supported_locales environment comes in to play. The default for that is Localize.all_locale_ids/0 with allow_runtime_locale_download: false. So if do no configuration, no matter what locale you select, you'll end up with :en because CLDR says you should always end up with a locale. And Localize ships with only :en and :und (:und only because some locales defer to it for some things so you'd end up needing it anyway). When log level is :debug (like in :dev mode) you'll see the locale loader falling back up the locale inheritance chain. And when thats exhausted, selecting :en as a last gasp because it's guaranteed to be there.

Hope that makes sense?

[cw789]

Yes, makes sense and is fine.

[kipcole9]

I've published localize version 0.4.0 with the following changelog entry:

Bug Fixes

• Localize.all_locale_ids/1 (:modern, :moderate, :basic) now returns the correct expanded list of locales. Thanks to @cw789 for the report.

[cw789]

Marvelous! Thank you very much.

[kipcole9]

You're clearly familiar with CLDR so I hope you'll share what your project is about when the time is right. And please keep the bug reports, issues and requirements coming.

[cw789]

Familiar with CLDR - I would not say so. It all started with:
https://elixirforum.com/t/is-there-a-way-to-localize-numbers-in-elixir-using-all-available-locales/67403

Yes of course, I will share once we are ready. Currently we are already migrating everything to Localize - yes it is better in all ways. We also explored Icu (icu4x NIF) as alternative, but Localize does better server all our needs.

I'll keep you updated. Once Money v6 version is out, we soon will have migrated everything.

[kipcole9]

ex_money version 6.0 is now out (along with updates to digital_token and money_sql) so hopefully you are good to go.