richardschneider / net-cldr Goto Github PK

@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

The Algorithmic Formatter is not implemented.

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

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.

The Numeric Formatting does not obey <currencySpacing> rules.

The Numeric Formatter does not obey the <minimumGroupingDigits>.

Parsing a LocalIdentifier should fail when a subtag is not defined.

Commented out code is in TransformFromBcp47 but cannot be enabled until #2 is resolved.

String Ranges needs to be fully implemented. It currently only supports a special test.

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

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.