Programming language identifier normalization/casing

• Next message: Peter_Constable@sil.org: "RE: Term Asian is not used properly on Computers and NET"
• Previous message: Marco Cimarosti: "UTF-64 [warning: contains bits & bytes humor] (was RE: [OT] bits and bytes)"
• Next in thread: Peter_Constable@sil.org: "Re: Programming language identifier normalization/casing"
• Maybe reply: Peter_Constable@sil.org: "Re: Programming language identifier normalization/casing"
• Maybe reply: Kenneth Whistler: "Re: Programming language identifier normalization/casing"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
• Mail actions: [ respond to this message ] [ mail a new topic ]

Unicode 3.1 Technical report #15, Annex 7
(http://www.unicode.org/unicode/reports/tr15/#Programming_Language_Ident
ifiers) contains the following remark:
"Generally if the programming language has case-sensitive identifiers
then Normalization Form C may be used, while if the programming language
has case-insensitive identifiers then Normalization Form KC may be more
appropriate."

If I'm not mistaken normalization and casing are two independent things.
So what would be the reason to make this connection?

Thanks in advance
Achim Ruopp
International Program Manager

• Next message: Peter_Constable@sil.org: "RE: Term Asian is not used properly on Computers and NET"
• Previous message: Marco Cimarosti: "UTF-64 [warning: contains bits & bytes humor] (was RE: [OT] bits and bytes)"
• Next in thread: Peter_Constable@sil.org: "Re: Programming language identifier normalization/casing"
• Maybe reply: Peter_Constable@sil.org: "Re: Programming language identifier normalization/casing"
• Maybe reply: Kenneth Whistler: "Re: Programming language identifier normalization/casing"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
• Mail actions: [ respond to this message ] [ mail a new topic ]

This archive was generated by hypermail 2.1.2 : Fri Jul 06 2001 - 00:18:17 EDT