The parser is complete and messaging formatting is also complete - both function and macro form.
Definitely interested in seeing if Mezzofanti and cldr_messages could work together. I’ll ping you a DM.
kip
ex_cldr Core Team
0
kip
ex_cldr Core Team
An update to ex_cldr_calendars 1.2.0 today to kickoff the weekend. It adds durations. A Duration is the difference between two dates, times and datetimes expressed in calendar time units. Of course Calendar.ISO is supported, but so are any calendars defined by or defined with Cldr.Calendar.new/3.
Then these durations can be localised to humanise the duration of time. Some examples:
# How long until the Tokyo Olympic Games start?
iex> {:ok, d} = Cldr.Calendar.Duration.new(~D[2019-08-31], ~D[2020-07-24])
{:ok,
%Cldr.Calendar.Duration{
day: 24,
hour: 0,
microsecond: 0,
minute: 0,
month: 10,
second: 0,
year: 0
}}
iex> Cldr.Calendar.Duration.to_string d
{:ok, "10 months and 24 days"}
iex> Cldr.Calendar.Duration.to_string d, locale: "ar"
{:ok, "10 أشهر و24 يومًا"}
iex> Cldr.Calendar.Duration.to_string d, locale: "he"
{:ok, "10 חודשים ו24 ימים"}
iex> Cldr.Calendar.Duration.to_string d, style: :narrow
{:ok, "10m and 24d"}
iex> Cldr.Calendar.Duration.to_string d, style: :narrow, list_options: [style: :unit_narrow]
{:ok, "10m 24d"}
All the localisation is driven, of course, by CLDR data encapsulated in ex_cldr.
3
kip
ex_cldr Core Team
ex_cldr 2.11 release supporting CLDR 36.0.0
This week the Unicode Consortium released CLDR version 36 upon which the hex package ex_cldr is based.
The CLDR release notes explain in detail the changes underlying the most comprehensive source of internationalisation and localisation data in the world, used by every major vendor.
Data changes that may affect ex_cldr formatting
- zh: The currency symbol for CNY changed from fullwidth ￥(FFE5) to halfwidth ¥ (00A5)
- fr_CA : Switched to full year (not 2-digit year) in short date formats. [CLDR-11666]
- bg: Removed “ч.” from time formats. [CLDR-11545]
- The translations for the new name ‘North Macedonia’ has been refined for many languages by contributors, and those languages with no contributors have been reverted to code ‘MK’. All Alt values also have been removed [CLDR-13099].
Release note highlights
- Approximately 32K items added
- Significant increase (approx 50% or more) in moderate and/or modern coverage for: ceb (Cebuano), ha (Hausa / Latin script), ig (Igbo), kok (Konkani), qu (Quechua), to (Tongan), yo (Yoruba). Additionally, the following locales had at least a 15% increase in basic coverage: az (Azerbaijani / Latin script), so (Somali / Latin script).
- Seed data for new locales, including three native languages of N. America: cic (Chickasaw), mus (Muscogee), osa (Osage, Osage script); an (Aragonese), su (Sundanese, Latin script), szl (Silesian).
- Additional data for new items listed below.
- Emoji
- Added names and keywords for Emoji 13.0 draft candidates; these are to be fleshed out further in v36.1.
- Refined names and keywords for Emoji 12.0, including for English.
- Measurement units:
- Additional compoundUnitPattern ({0}⋅{1} in root) for expressing units like newton-meter (N⋅m)
- Additional units: dot-per-centimeter, dot-per-inch, em, megapixel, pixel, pixel-per-centimeter, pixel-per-inch; decade; therm-us; bar, pascal
- Locale identifiers and names
- Extended Language Matching to have fallbacks for many encompassed languages. [CLDR-13244]
- Added more languageAliases from the BCP47 language subtag registry, for deprecated languages.
- New alt=“menu” names for certain languages, intended to provide better sorting in menus. [CLDR-11834]
- Updated validity and collection information for geographic subregions; updated names especially for subregions of UK and Sweden.
- Names have been added for “pseudo-regions” XA (Pseudo-Accents) and XB (Pseudo-Bidi). These are only intended for testing purposes, you may need to add special handling to remove them for production purposes. [CLDR-13100]
- Other
- Time zone data support for 2019c. [CLDR-13281]
There are no changes to the public API of any of the ex_cldr_* packages. Updates are only to encapsulate the new data.
Upgrading
Executing mix deps.update ex_cldr should be enough to get you on the latest version which is 2.11.0.
3
kip
ex_cldr Core Team
Since the new astro library is now out I was able to finish up the Persian (Solar Hijri) calendar which is now available on hex.
This is a calendar that starts the year on the March equinox (or a day later if the equinox is equal to or later than true solar noon on the day of equinox in Iran). The fact that it is observation based required the development first of a library to do the astro calculations - which turned out to be good fun (albeit there is much more to do to support more complex lunisolar calendars like the Islamic and Hebrew calendars).
Localisation is supported via ex_cldr_calendars which is a dependency. And full date/time formatting is available via ex_cldr_dates_times which is not a dependency.
Since I’m back temporarily on calendars I’ll finish up the Coptic Calendar and the Ethiopic Calendar since they are quite straight forward.
1
kwando
kip
ex_cldr Core Team
With the impending release of Elixir 1.10, several of the CLDR libs have been updated to be compatible without compiler warnings or to leverage new capabilities. Feedback on any issues would be most welcome. A simple mix deps.update <lib> will be enough to move to the latest version which is also backwards compatible for earlier Elixir versions (typically to Elixir 1.8).
The new releases are:
- ex_cldr_calendars 1.7.0 which uses the new implementation of the
Inspectprotocol for calendar types to allow the inspecting and parsing ofSigil_D,Sigil_NandSigil_Ufor any valid calendar. For example:
iex> ~D[2020-W01-1 Cldr.Calendar.ISOWeek]
~D[2020-W01-1 Cldr.Calendar.ISOWeek]
iex> ~D[2020-01-02 Cldr.Calendar.Gregorian]
~D[2020-01-02 Cldr.Calendar.Gregorian]
-
ex_cldr 2.12.0 which removes calls to the deprecated
Code.ensure_compiled?/1 -
ex_money 4.4.2 which also removes calls to
Code.ensure_compiled?/1. It now has a dependency onex_cldrof a minimum of2.12.0.
The other CLDR packages do not require any updating to support Elixir 1.10,
1
kip
ex_cldr Core Team
With Elixir 1.10 now out its time to release ex_cldr_units 2.8.0 that supports the new Elixir Enum/sort/2 by introducing Cldr.Unit.compare/2. Any two units that can be converted to each other can be compared.
Examples
iex> alias Cldr.Unit
Cldr.Unit
iex> unit_list = [Unit.new(:millimeter, 100), Unit.new(:centimeter, 100), Unit.new(:meter, 100), Unit.new(:kilometer, 100)]
[#Unit<:millimeter, 100>, #Unit<:centimeter, 100>, #Unit<:meter, 100>,
#Unit<:kilometer, 100>]
iex> Enum.sort unit_list, Cldr.Unit
[#Unit<:millimeter, 100>, #Unit<:centimeter, 100>, #Unit<:meter, 100>,
#Unit<:kilometer, 100>]
iex> Enum.sort unit_list, {:desc, Cldr.Unit}
[#Unit<:kilometer, 100>, #Unit<:meter, 100>, #Unit<:centimeter, 100>,
#Unit<:millimeter, 100>]
iex> Enum.sort unit_list, {:asc, Cldr.Unit}
[#Unit<:millimeter, 100>, #Unit<:centimeter, 100>, #Unit<:meter, 100>,
#Unit<:kilometer, 100>]
1
kip
ex_cldr Core Team
Updates released to hex for most of elixir-cldr libraries based on CLDR.
Summary of updates
-
Ensure certificate verification when downloading locales. This should automatically detect the certificate trust store on most platforms (except Windows). Therefore in most cases no configuration is required. If you think it should detect the trust store on your platform but it doesn’t, please raise an issue. It will also detect that either castore or certifi is installed and use the package’s trust store in preference to the platform trust store.
-
Updates the data to CLDR version 37. Adds about 20 new locales for a total of 566. Can you say
ff-Adlam-CM? It’s the Fula language with the Adlam script as spoken in Cameroon. -
Significant updates to the Unit of Measure data which is supported by ex_cldr_units version 3.0.0. The units engine now supports compound units and algebraic units.
square ampere per yoktolumenanyone? The units do not have to be obviously meaningful - just algebraically resolvable. Built in support for SI prefixes and square- and cubic- prefixes. The output formatting viaCldr.Unit.to_string/3needs some more work for complex units but is otherwise sound.
-
Adds the
Cldr.Charsprotocol which is implemented for numbers, dates, times, units, money to continue the journey towards low-friction localisation of applications -
Adds much better support for the BCP47 U extension which continues the work towards having the language tag become a preferred way to express user intent in localised applications. For example, this allows a user to specify default currency, default number system, default calendar and so on.
Release versions and links
- ex_cldr version 2.14.0. Changelog. Github.
- ex_cldr_numbers version 2.13.0. Changelog. Github.
- ex_cldr_dates_times version 2.4.0. Changelog. Github.
- ex_cldr_lists version 2.5.0. Changelog. Github.
- ex_cldr_units version 3.0.0. Changelog. Github.
- ex_cldr_calendars version 1.8.0. Changelog. Github.
- ex_cldr_calendars_format version 0.4.0. Changelog. Github.
- ex_cldr_currencies version 2.5.0. Changelog. Github.
4
kip
ex_cldr Core Team
ex_cldr_numbers version 2.14.0 is released today. This release makes it easy to parse numbers and currencies in a localised manner. Some examples:
Parsing
# Interpret grouping and decimal marker in
# a localised way
iex> Cldr.Number.Parser.parse("＋1.000,34", locale: "de")
{:ok, 1000.34}
# Using underscore as a separator is supported
iex> Cldr.Number.Parser.parse("-1_000_000.34")
{:ok, -1000000.34}
# The type of number can be specified: integer, float, Decimal
iex> Cldr.Number.Parser.parse("1.000", locale: "de", number: :integer)
{:ok, 1000}
# If the string doesn't fit the type an error is returned
iex> Cldr.Number.Parser.parse("＋1.000,34", locale: "de", number: :integer)
{:error, "+1000.34"}
Scanning
Scan the string and separate numbers and string
iex> Cldr.Number.Parser.scan("£1_000_000.34")
["£", 1000000.34]
# In any arbitrary string
iex> Cldr.Number.Parser.scan("I want £1_000_000 dollars")
["I want £", 1000000, " dollars"]
iex> Cldr.Number.Parser.scan("The prize is 23")
["The prize is ", 23]
iex> Cldr.Number.Parser.scan("The lottery number is 23 for the next draw")
["The lottery number is ", 23, " for the next draw"]
iex> Cldr.Number.Parser.scan("The loss is -1.000 euros", locale: "de", number: :integer)
["The loss is ", -1000, " euros"]
Resolving currencies from strings
# Try to find the currency that reflects
# string description
iex> Cldr.Number.Parser.scan("100 US dollars")
...> |> Cldr.Number.Parser.resolve_currencies
[100, :USD]
# Even with a fuzzy match
iex> Cldr.Number.Parser.scan("100 eurosports")
...> |> Cldr.Number.Parser.resolve_currencies(fuzzy: 0.8)
[100, :EUR]
# and in a locale-aware way
iex> Cldr.Number.Parser.scan("100 dollars des États-Unis")
...> |> Cldr.Number.Parser.resolve_currencies(locale: "fr")
[100, :USD]
1