2010/12/9 Worley, Dale R (Dale) <[email protected]>: > There is a corruption that allows situations like this to work fairly well: > Treat all "upper half" bytes (x80 to xFF) as "letters": > > UTF8-NONASCII = %x80-FF > > This causes UTF-8 encoded characters x80 and upward to appear as a sequence > of UTF8-NONASCII, but in most applications, that is acceptable. If the text > is encoded using ISO-8859-x, or any one-byte encoding that reserves x00-x7F > to match ASCII, then the characters x80-xFF are parsed as a single > UTF8-NONASCII.
Fantastic! It works! (and doesn't break valid cases as I've described in my previous sent mail). :) > Of course the best solution is to replace any device that does not encode > characters correctly. Yes, but it depends on vendors and it's not easy to "change the world" :) > But also verify that you are configuring the device correctly -- if the > configuration information is presented in an unexpected encoding, the phone > might be copying the bytes without examining them. I just configure my display name "Iñaki" in the web interface of the Linksys phone, so there is nothing special I can do. The web interface or the phone should be intelligent enough to correctly write such value, but it's not the case. -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
