Re: Names for control characters (Was: "(in 6429)" in allkeys.txt)

> From: "Whistler, Ken" > Date: Wed, 12 Mar 2014 16:48:25 + > Cc: "Whistler, Ken" , > "unicode@unicode.org" > > Please be very careful here. Having a non-empty value in field 1 of > UnicodeData.txt is *not* the same has "having a Unicode name". You will see that I didn't refer to th

RE: Names for control characters (Was: "(in 6429)" in allkeys.txt)

Please be very careful here. Having a non-empty value in field 1 of UnicodeData.txt is *not* the same has "having a Unicode name". See: http://www.unicode.org/versions/Unicode6.2.0/ch04.pdf#G135207 for the gory details. The "Unicode name" is formally defined in terms of the Name property, which

Re: Names for control characters (Was: "(in 6429)" in allkeys.txt)

> From: starb...@stp.lingfil.uu.se (Per Starbäck) > Date: Wed, 12 Mar 2014 13:32:15 +0100 > Cc: "unicode@unicode.org" > > Regarding these names in ISO 6429 again, how come these control > characters don't have Unicode names? They have a non-empty "old name" field: ;;Cc;0;BN;N;NULL

Re: Names for control characters (Was: "(in 6429)" in allkeys.txt)

They do have aliases in NameAliases.txt ;NULL;control ;NUL;abbreviation 0001;START OF HEADING;control 0001;SOH;abbreviation 0002;START OF TEXT;control 0002;STX;abbreviation ... Mark *— Il meglio è l’inimico del bene —* On Wed, Mar 12, 2014 at 1:3

Names for control characters (Was: "(in 6429)" in allkeys.txt)

Ken Whistler wrote: > Ah, I see what the interpretation problem was. Yes, that is > a straightforward kind of improvement -- easily enough done. > Look for a change the next time the file is updated. (It will not > be immediately changed, pending other review comments.) Thanks! Then I'll skip maki