Re: Strange Browser Behavior

From: Tom Gewecke (
Date: Mon Jan 08 2007 - 11:17:35 CST

On Jan 8, 2007, at 10:01 AM, Simon Montagu wrote:

> The process for translating a UTF-32 codepoint into a UTF-16 surrogate
> pair, without first checking whether the UTF-32 codepoint is within
> the legal range:
> (0x230DBD - 0x10000) / 0x400 + 0xD800 = 0xE083
> (0x230DBD - 0x10000) % 0x400 + 0xDC00 = 0xDDBD
> On Windows Firefox 2 this is what I see on your test page. I'm not
> sure why the sequence is preceded by a BOM for you.
> For the record, the bug of not checking the original value was fixed
> some time ago, and on a nightly build of Firefox I see a single U+FFFD
> character.

Thanks much to everyone who responded! The BOM is an error generated
when I saved the text. Normally Mac apps don't add that for UTF-8, but
I happened to use one that does.

I guess the latest regular Mac Firefox release,, has not got
the fix yet.

This archive was generated by hypermail 2.1.5 : Thu Jan 18 2007 - 15:55:40 CST