Re: Unicode strings?

Crypto Compress wrote:

Good point, but users should use NFC UTF-8 without BOM for variable/function names. It would be documentation issue.

in the languages i know combining diacritics are not common so can't evaluate how practical it is to type those. Would it be impossible to change code with a dumb editor? $café !== $café 0x63 0x61 0x66 0xC3 0xA9 0x63 0x61 0x66 0x65 0xCC 0x81

'cryptocompress' (is that really on your passport :( ) This is exactly the area we need to agree on a plan moving forward. There are a number of options on the table 1 - Limit variable and other names to 'ASCII' only characters so that case folding can be maintained. 2 - Remove 'case insensitivity' but not just for point 1 reasons. ( I see this as your example being two different strings ;) ) 3 - Allow unicode names to be used in places where they currently cause problems. Not actually using unicode variable names myself, I still don't understand where the problems are with '3' except for the simple comparison case where normalizing and case conversion creates a minefield? People are currently using unicode in these areas and understand many of the restrictions? -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk