On Wednesday 2009-07-15 04:24 +, Ian Hickson wrote:
Firefox checks to see if the first two bytes are null/not-null or
not-null/null and acts accordingly; if they're both not null it uses BE
and if they're both null it does something I don't recognise (and checks
both the UTF-8 and
On Wed, 24 Jun 2009, Kartikaya Gupta wrote:
There's a page
(http://www.microsoft.com/windowsmobile/mobile/en-us/totalaccess/software/software/eula-sw-netflix.mspx
specifically) that has a Content-Type header of text/html;
charset=utf-16 and has no BOM. The references I've seen (RFC2781,
There's a page
(http://www.microsoft.com/windowsmobile/mobile/en-us/totalaccess/software/software/eula-sw-netflix.mspx
specifically) that has a Content-Type header of text/html; charset=utf-16
and has no BOM. The references I've seen (RFC2781, as well as
Have you checked for a byte order marker in the source document? (see http://unicode.org/faq/utf_bom.html#BOM
)
--Oliver
On Jun 23, 2009, at 6:42 PM, Kartikaya Gupta wrote:
There's a page (http://www.microsoft.com/windowsmobile/mobile/en-us/totalaccess/software/software/eula-sw-netflix.mspx
On Tue, Jun 23, 2009 at 10:03 PM, Oliver Huntoli...@apple.com wrote:
Have you checked for a byte order marker in the source document? (see
http://unicode.org/faq/utf_bom.html#BOM )
He said it has no BOM.
