Am 23.02.2012 22:14, schrieb Orchid Win7 v1:
> On 23/02/2012 17:35, Warp wrote:
>> Support for UTF-16 is still relatively poor (although getting better).
>> Most modern browsers should handle it ok, though, but it requires for the
>> server to send the proper http header to tell the browser the encoding,
>> and configuring the server to do this might not be trivial. (A html file
>> encoded in UTF-16 will look like garbage.)
>
> Isn't that what the HTML encoding tag is for? Or the XML encoding
> declaration?

You can't read those until you know at least some basics about the 
encoding :-P

That's /one/ reason why XML requires UTF-16 files to start with a byte 
order mark: If the file starts with "FE FF" or "FF FE", it's either 
UTF-16, malformed XML (not starting with optional whitespace followed by 
"<?"), or indeed garbish, so UTF-16 is a safe bet in that case. 
Otherwise rely on the file format being backward compatible with ASCII, 
and treat it as UTF-8 (which is ASCII-compatible as well) until an 
encoding declaration tells you otherwise.

Post a reply to this message