All Versions
62
Latest Version
Avg Release Cycle
25 days
Latest Release
-

Changelog History
Page 5

  • v2.10.0 Changes

    January 14, 2020

    🚀 This is the changelog for Cldr v2.10.0 released on January 15th, 2020. For older changelogs please consult the release tag on GitHub

    🐛 Bug Fixes

    • 🛠 Fixes formatting of negative percentages. Actually fixes an issue where the default negative format would be incorrect in many cases. Thanks to @maennchen. Closes #11.

    ✨ Enhancements

    • ⚠ Optionally logs a warning if compiling a number format at runtime. The warning is emitted only once for each format to reduce log clutter. The log warning is emitted if the backend configuration key :supress_warnings is set to false (this is the default value). The warn_once mechanism depends on the availability of the :persistent_term module which is only available from OTP 21.2 onwards. On earlier releases of OTP no warning will be emitted.

  • v2.9.0 Changes

    October 20, 2019

    🚀 This is the changelog for Cldr v2.9.0 released on October 20th, 2019. For older changelogs please consult the release tag on GitHub

    ✨ Enhancements

    • Adds option :currency_symbol to Cldr.Number.to_string/2. This option, when set to :iso changes a currency format to force using the ISO currency code instead of the native currency symbol.

  • v2.8.0 Changes

    October 09, 2019

    🚀 This is the changelog for Cldr v2.8.0 released on October 10th, 2019. For older changelogs please consult the release tag on GitHub

    ✨ Enhancements

    • ⚡️ Update ex_cldr to version 2.11.0 which encapsulates CLDR version 36.0.0 data.

  • v2.7.2 Changes

    September 06, 2019

    🚀 This is the changelog for Cldr v2.7.2 released on September 7th, 2019. For older changelogs please consult the release tag on GitHub

    🐛 Bug Fixes

    • 0️⃣ Call Keyword.get_lazy/3 when accessing Cldr.default_locale/0 to avoid exceptions when no default backend is configured but an optional :backend has been passed.

  • v2.7.1 Changes

    August 23, 2019

    🚀 This is the changelog for Cldr v2.7.1 released on August 23rd, 2019. For older changelogs please consult the release tag on GitHub

    🐛 Bug Fixes

    • Fix @spec for Cldr.Number.to_string/3 and Cldr.Number.to_string!/3

  • v2.7.0 Changes

    August 20, 2019

    🚀 This is the changelog for Cldr v2.7.0 released on August 21st, 2019. For older changelogs please consult the release tag on GitHub

    ✨ Enhancements

    • An option :backend can be passed to Cldr.Number.to_string/3 and it will be used if being called as Cldr.Number.to_string/2. This means that for a call like Cldr.Number.to_string(number, backend, options) which has an option :backend, the call can be replaced with Cldr.Number.to_string(number, options).

  • v2.6.4 Changes

    June 16, 2019

    🚀 This is the changelog for Cldr v2.6.4 released on June 16th, 2019. For older changelogs please consult the release tag on GitHub

    🐛 Bug Fixes

    • 🛠 Fix the default value for the backend parameter for Cldr.Number.to_string/3

    • Allow Cldr.Number.to_string/3 to be called as Cldr.Number.to_string <number>, <options> as long as there is a default backend configured in config.exs.

  • v2.6.3 Changes

    🚀 This is the changelog for Cldr v2.6.3 released on June 15th, 2019. For older changelogs please consult the release tag on GitHub

    🐛 Bug Fixes

    • Correctly interpret the special short format 0 to mean "format as a normal decimal or currency number". Thanks to @epilgrim. Closes #10

  • v2.6.2 Changes

    🚀 This is the changelog for Cldr v2.6.2 released on June 12th, 2019. For older changelogs please consult the release tag on GitHub

    🐛 Bug Fixes

    • Don't transliterate in Cldr.Number.Transliterate.transliterate_digits/3 if from and to number systems are the same.

  • v2.6.1 Changes

    🚀 This is the changelog for Cldr v2.6.1 released on June 2nd, 2019. For older changelogs please consult the release tag on GitHub

    🐛 Bug Fixes

    • 🐎 Ensure Cldr.Number.to_string/3 doesn't transliterate is the number systems are compatible for a given locale. Basically, if the local and number system don't require transliteration from 0..9 to another script (like indian, arabic, ...) then we don't do it. This improves performance by about 10% for this common case.