Talk:International characters in XUL JavaScript

From MDC

1) From what I read about BOM on wikipedia, it cannot be used to "determine the character set" of a file. There are a few options that allow to differentiate between different unicode formats, but not between other simpler charsets. --Nickolay 07:41, 13 September 2005 (PDT)

It can be used just fine to decide between UTF-8, -16 and -32, and the little/big-endian versions of those --biesi

Right, but saying it determines the character encoding is a bit misleading.--Nickolay 09:57, 13 September 2005 (PDT)

OK, maybe... I can't currently think of a better wording for it; if you can, feel free to change. BTW, thanks for the fixups to this article. --Biesi 11:39, 13 September 2005 (PDT)

2) We should use consistent terminology when referring to the character encoding. In this article the terms "character encoding", "character set", and "charset" are used interchangably. I don't know which is the preferred term. --Nickolay 07:41, 13 September 2005 (PDT)

Oops. I tried to use character encoding consistently. --biesi

3) It's not clear from the article, whether passing charset in Content-Type header worked in pre-1.8 versions. The name of the article (intl characters in *XUL* JS) contributes to the confusion. --Nickolay 07:41, 13 September 2005 (PDT)

it didn't. The title is XUL JS because HTML JS behaves differently... Is the notice that previous versions always used ISO-8859-1 not clear? --biesi

Oh, okay. Yes, in fact it's quite clear, and I was just a bit confused. I tried to edit the page to make it even more clear. --Nickolay