Releases: elixir-cldr/cldr
Cldr version 2.33.2
Bug Fixes
- Fixes a bug in
Cldr.LanguageTag.Sigil.sigil_l/2
. With the changes in metadata structure for Elixir 14 a pattern match was failing. The pattern is now fixed and is backwards compatible with earlier Elixir versions.
Cldr version 2.33.1
Enhancements
- Now delegates locale installation to
Cldr.Http.get/2
in the cldr_utils library so that we can centralise request handling and provide an "unsafe TLS" option for downloading to support resolution of #184.
Cldr version 2.33.1-rc.0
Enhancements
- Now delegates locale installation to
Cldr.Http.get/2
in the cldr_utils library so that we can centralise request handling and provide an "unsafe TLS" option for downloading to support resolution of #184.
Testing in CI
This version of ex_cldr
does nothing more than delegate HTTP requests to Cldr.Http.get/2
that is in the cldr_utils
library. This is a more up-to-date request handler (still using httpc
) that configures cyphers according to the ERLF guidelines.
If you have a chance to test in CI with this candidate release and it works I'd appreciate you letting me know. And if it doesn't fix the issue too of course!
Cldr version 2.33.0
Bug Fixes
Fixed a bug whereby Cldr would not compile due to a change to module alias resolution in generated code. The root cause of the change has not been established but the fix, by specifically importing Cldr.Math, works on Elixir 1.14 and earlier releases back to Elixir 1.11.
Enhancements
Removes warnings for Elixir 1.14. As a result ex_cldr
is now supported with Elixir 1.11 and later only (support for Elixir 1.10 has been discontinued).
Allow either of ratio 2.x
or ratio 3.x
dependencies to be configured. This library is only used during the development of ex_cldr
and is not normally used by library consumers. However ex_cldr_units does use ratio
so this flexibility helps downstream maintenance, especially when ratio is updated to avoid Elixir 1.14 deprecation warnings.
Cldr version 2.32.1
Bug Fixes
- Don't use
IO.warn/2
when compiling a backend and a known Gettext locale can't be matched to a Cldr locale.IO.warn/2
will cause errors if the compilation settingwarnings_as_errors: true
is set. Instead, these messages will be output as a "note" that does not trigger warnings. In addition the error message has been improved to make clear that although the Gettext locale has no Cldr equivalent, it will still be matched at runtime. See the conversation at https://elixirforum.com/t/bridging-locale-name-differences-between-ex-cldr-gettext. Thanks to @lenards for the report.
Cldr version 2.32.0
Bug Fixes
- Fix
Cldr.with_locale/{2, 3}
to source the current locale from the backend of the supplied new locale. This reduces the chances of an exception resulting from a non-existent default backend and a default locale that is not set.
Enhancements
- Add
with_locale/2
to Cldr backend modules. This ultimately delegates toCldr.with_locale/{2, 3}
Cldr version 2.31.0
Enhancements
- Adds
Cldr.Locale.script_from_locale/{1, 2}
andCldr.default_script/0
.
Cldr version 2.30.0
Enhancements
- Adds a backend module for
AcceptLanguage
which definesMyApp.Cldr.AcceptLanguage.parse/1
andMyApp.Cldr.AcceptLanguage.best_match/1
Cldr version 2.29.0
Migration
- The plugs
Cldr.Plug.SetLocale
,Cldr.Plug.AcceptLanguage
andCldr.Plug.PutSession
have been extracted to their own library, ex_cldr_plugs. Therefore adding{:ex_cldr_plugs, "~> 1.0"}
to thedeps
of any application using these plugs is required.
Bug Fixes
Cldr version 2.28.0
Enhancements
- Update CLDR to release 41. This is minor CLDR release adding
en-MV
,hi-Latn
andks-Deva
locales and continuing data improvements on unit grammar. Changes to locales in this release can be found on the locale change page.