Re: [Geopriv] Domain identifier in common policy
Andrew Newton <[email protected]>
| Newsgroups | gmane.ietf.simple,gmane.ietf.geopriv |
|---|---|
| Message-ID | <[email protected]> |
On Jan 6, 2006, at 11:03 AM, Henning Schulzrinne wrote: > I still fail to see the practical advantage of allowing UTF-16, > given that we control the input and that this is not general text, > but rather strings with a very specific purpose. 1) How does the application know that the source encoding was UTF-16? Or asked another way, how does the application know the source encoding was not UTF-8? Most can look at the XML declaration, but in the passing of the element content where this is actually relevant they may not be able to tell. This type of detection is extra logic and seems unnecessary if the application can handle both. Also, on platforms that would output UTF-16, it is extra logic to force them to transcode to UTF-8, which is also unnecessary since the receiver of that output must understand UTF-16. 2) What practical advantage is there to disallowing UTF-16? -andy _______________________________________________ Simple mailing list [email protected] https://www1.ietf.org/mailman/listinfo/simple