-
Notifications
You must be signed in to change notification settings - Fork 401
CLDR-18722 Explicit numberSystem attribute #4974
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
09366c0
8dbbcf6
112a943
cb070b2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -259,12 +259,8 @@ public CheckCLDR handleCheck( | |
} | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I take it that NumericType still gets these items, so they aren't skipped by line 258. |
||
XPathParts parts = XPathParts.getFrozenInstance(path); | ||
|
||
// TODO: re-enable this commented-out check | ||
// Reference: https://unicode-org.atlassian.net/browse/CLDR-18722 | ||
/* | ||
// Check that number formats are for an explicit number system. | ||
String numberSystem = parts.getAttributeValue(2, "numberSystem"); | ||
if (numberSystem == null) { | ||
if (!parts.containsAttribute("numberSystem")) { | ||
result.add( | ||
new CheckStatus() | ||
.setCause(this) | ||
|
@@ -273,7 +269,6 @@ public CheckCLDR handleCheck( | |
.setMessage( | ||
"Number formats must have an explicit numberSystem attribute.")); | ||
} | ||
*/ | ||
|
||
// Do tests that need to split the values | ||
|
||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2051,7 +2051,7 @@ CLDR data files are interpreted according to the LDML specification (http://unic | |
<!ATTLIST decimal references CDATA #IMPLIED > | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm wondering why this file exists; I've noticed that it causes errors when it drifts way from the regular ldml.dtd. If we keep it, we should have a test that it is identical (and maybe we do, and that's what alerted you to it?) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. In eclipse I see the following error with that file: Description Resource Path Location Type There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm confused by that too. There are 3 ldml.dtd files:
I was accidentally editing the wrong one before I noticed that... There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. In fact I did that again even after realizing there are 3 files; this PR still fails maybe for that reason. I'll make another (4th) commit shortly. @srl295 do you have insight about how the ldml.dtd files relate to each other? |
||
<!--@METADATA--> | ||
<!ATTLIST decimal numberSystem CDATA #IMPLIED > | ||
<!--@DEPRECATED--> | ||
<!--@MATCH:bcp47/nu--> | ||
|
||
<!ELEMENT group ( #PCDATA ) > | ||
<!ATTLIST group alt NMTOKENS #IMPLIED > | ||
|
@@ -2062,7 +2062,7 @@ CLDR data files are interpreted according to the LDML specification (http://unic | |
<!ATTLIST group references CDATA #IMPLIED > | ||
<!--@METADATA--> | ||
<!ATTLIST group numberSystem CDATA #IMPLIED > | ||
<!--@DEPRECATED--> | ||
<!--@MATCH:bcp47/nu--> | ||
|
||
<!ELEMENT list ( #PCDATA ) > | ||
<!ATTLIST list alt NMTOKENS #IMPLIED > | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is something wrong here; unrelated to this ticket. The [❰❱] characters should never occur in values for our data files. It looks like vetters might be pasting them into values. I'll file a separate ticket about this.