CLDR-15923 load UN Literacy data from new location

[srl295]

CLDR-15923

• update docs (new location)
• includes updated data
• includes unit tests that will fail if parsing fails
• This PR completes the ticket.

ALLOW_MANY_COMMITS=true

[pedberg-icu]

Nicely organized!

[btangmu]

This is a little surprising, that its absence was never a problem before... oh, I think I see, the new SimpleHandler.handleElement doesn't currently do anything, and this is in case it eventually does

[srl295]

It's a new (internal) API. There wasn't a way (in this API) to register for notification on a new element. The issue comes because the data is of this form:

<a>
   <b c="3"/>
   <b d="4"/>
</a>
<a>
   <b c="5"/>
   <b d="6"/>
</a>

the XPATH=based api would only produce:

//a/b[@c="3"]
//a/b[@d="4"]
 (need notification that we're on a new 'a' here)
//a/b[@c="5"]
//a/b[@c="6"]

since there's no identity on <a> this new API lets me reset the parser. Anyway, that's what it's for.

This isn't needed for CLDR's own data, because the <a> above always has a clear identity <a id="something"/> vs <a id="somethingElse"/> so produces a unique xpath. This minor API update lets me reuse our existing convenience functions without writing something entirely new for this single file.

[macchiati]

For normal CLDR there must be a distinguishing attribute for the first a and the second a to be different.

In CLDR, the mechanism for such distinctions is to add an _q distinguishing element. That also preserves order where needed. That could be done here as well, for consistency.

[srl295]

@macchiati this is the internal low-level XMLFileReader interface. _q is handled at the next layer up.

[srl295]

normal CLDR data doesn't go through this interface, see other comment.

[macchiati]

I'd like the _q discussion settled first. I'm ok with a special case, but I just don't want it to interfere with other tooling.

[srl295]

I'd like the _q discussion settled first. I'm ok with a special case, but I just don't want it to interfere with other tooling.

take a look at the code change in context. This is just a new function on SimpleHandler. Normal CLDR data is loaded with XMLNormalizingLoader.loadXMLFile() which calls XMLFileReader.read(fullFileName, fis, -1, true, XML_HANDLER); - not SimpleHandler.

[macchiati]

Makes sense, thanks for the background