[Unicode]   Common Locale Data Repository : Bug Tracking Home | Site Map | Search

CLDR Ticket #11289(new survey)

Opened 4 weeks ago

Adding code point scalar values in LDML

Reported by: Marcel Schneider <charupdate@…> Owned by: anybody
Component: annotations Data Locale:
Phase: dsub Review:
Weeks: Data Xpath:


Preparing votes off-line in a text editor is hard because the hexadecimal code points are missing in the LDML files, while the "cp" attribute’s value is a literal. Example:


Now like what I requested in ticket:10206, I’d suggest adding the hex code points. Default sorting is more straightforward using literals, so that these would stay first, but as value of a char attribute, that seems not yet to occur in the DTD. Next comes then the cp attribute, still with a CDATA value but the hexadecimal code point without the "U+" prefix. This is however present in:
but not in:

Anyway in the sources, "U+" is generally not present.

If cp must keep its literal value for backwards compatibility, the code point could be the value of a sv attribute, for "scalar value", or hcp for "hex code point".

Another good thing to add is the emoji number. As this is always unique, while a given emoji may have multiple code points that it is made up from, the latter may be omitted to avoid clutter.

The suggested DTD snippet is then (new in bold):

<!ELEMENT annotation ( #PCDATA ) >
<!ATTLIST annotation cp CDATA #REQUIRED >
<!ATTLIST annotation no CDATA #REQUIRED >
<!ATTLIST annotation hcp CDATA #IMPLIED >
<!ATTLIST annotation tts CDATA #IMPLIED >


<!ATTLIST annotation type (tts) #IMPLIED >
<!ATTLIST annotation alt NMTOKENS #IMPLIED >
<!ATTLIST annotation draft (approved | contributed | provisional | unconfirmed) #IMPLIED >




Add a comment

Modify Ticket

as new

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.