richardschneider / net-cldr Goto Github PK

View Code? Open in Web Editor NEW

11.0 3.0 4.0 1.05 MB

Processing locale data for internationalisation software using Unicode CLDR

License: MIT License

C# 99.97% Batchfile 0.03%

cldr internationalisation i18n unicode

net-cldr's Introduction

Sepia.Globalization

Provides locale content for internationalisation software using the Unicode Common Local Data Repository (CLDR).

Features

Uses the official Unicode CLDR XML without any "build steps"
Can download the latest CLDR anytime
Uses XPath expressions to query the CLDR
Parsing of a locale identifier
Validation of common codes (language, currency, ...)
Supports complex CLDR inheritance via
Formatting of numbers and currency
Spelling out cardinal and ordinal numbers

Getting started

Published releases of the package are available on NuGet. To install, run the following command in the Package Manager Console.

PM> Install-Package Sepia.Globalization

Usage

using Sepia.Globalization;

The CLDR uses the singleton pattern. To access the repository, use Cldr.Instance.

Ensure that the latest version of the CLDR is installed. This will download the latest published release from unicode.org, if required.

var version = Cldr.Instance.DownloadLatestAsync().Result;
Console.WriteLine($"Using CLDR {version}");

Query

Query the CLDR for the fractional digits of the Japanese Yen (JPY)

var jpy = Cldr.Instance
    .GetDocuments("common/supplemental/supplementalData.xml")
    .FirstElement("supplementalData/currencyData/fractions/info[@iso4217='JPY']");
Assert.AreEqual("0", jpy.Attribute("digits").Value);

Format

var locale = Locale.Create("fr");
var formatter = NumberFormatter.Create(locale);

Assert.AreEqual("1234,568", formatter.Format(1234.56789));

License

The library is licensed under the MIT license. Refere to the LICENSE file for more information.

net-cldr's People

Contributors

Stargazers

Watchers

Forkers

mikamikem kreativjos markusdresch spocweb

net-cldr's Issues

AppVeyor fails to find latest CLDR

It appears that unicode.org is blocking requests from AppVeyor, see the details here.

This prevents the tests from running because no CLDR data is present on the test server.

Currency symbol spacing

The Numeric Formatting does not obey <currencySpacing> rules.

Validating codes fail

The common\validity XML files contain string ranges which are not supported by the IsXXXDefined methods.

Compact numbers

The Numeric Formatter does not allow the long/short compact representation; such as 1000 being "1K".

@richardschneider that is not bug, sorry for this. But I am so new using CLDR and slogging to understand. I have a project which was writing .NET. I found your .NET wrapper. So my question is about this http://cldr.unicode.org/translation/transforms page. I would like to transform Chinese or Japanese or Russian or Greek person name to roman writing. For example;

キャンパス -> kyanpasu
Αλφαβητικός Κατάλογος -> Alphabētikós Katálogos
биологический -> biologicheskij

Thank you in advance

Missing number grouping for small numbers

Hello,
it looks like a number grouping functionality works incorrectly in the edge case:

var version = await Cldr.Instance.DownloadLatestAsync(); // version: 38.0

var locale = Locale.Create("en"); // locale: en-Latn-US
var formatter = NumberFormatter.Create(locale); // formatter.Options.UseGrouping: true, formatter.Symbols.Group: ","

Console.WriteLine($"{formatter.Format(1000)}");

For en-Latn-US locale minimumGroupingDigits is 1 and decimalFormat pattern is #,##0.###.
So according to Numbering Systems and Number and currency patterns docs, 1,000 must be printed out, but 1000 is printed instead.

I guess the problem is here:

useGrouping = nDigits > minDigits;

should be

useGrouping = nDigits >= minDigits;

Please check, maybe I misunderstood the docs.