On Mar 20, 2008, at 14:16, Henri Sivonen wrote: >> 1. If the new encoding is UTF-16, change it to UTF-8. > > Please be specific about UTF-16BE, UTF-16LE, UTF-32, UTF-32BE and > UTF-32LE. The spec should say whether the substitution happens on the declaration string level or on a resolved encoding object level (after processing all the plentiful legacy aliases). The encoding object wouldn't be available when the UA doesn't support UTF-16 (permitted but unlikely) or UTF-32 (likely). I'd expect the substitution to happen on the string in this case but on the encoding object in the Latin 1, Thai and GBK cases elsewhere. -- Henri Sivonen hsivonen@iki.fi http://hsivonen.iki.fi/Received on Thursday, 20 March 2008 12:57:06 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 13 October 2008 01:39:15 GMT