Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Firefox having problems with UTF-16le (Windows default unicode set)

  • 1 个回答
  • 5 人有此问题
  • 2 次查看
  • 最后回复者为 cor-el

more options

I have a website where I have many different languages (English, German, Russian, Old Russian, Polish, French, Italian, Spanish, etc.) and so it is pretty necessary to use a unicode set to accommodate this. For quite awhile, Windows default Unicode set is UTF-16le, so that is what I use, and every page within this site has that coded in the header for browsers to recognise. This site had been tested with Firefox, IE, Opera, Safari, Kylo, and even Netscape, and there was no problem. Within the last couple months, however, Firefox has released updates which have garbled my site, and even when I manually set the encoding to UTF-16le, my links to amazon are rendered completely unusable, and if I navigate away from the page and then click back to a page using the back button, Firefox once again renders it as garbage.

I have a website where I have many different languages (English, German, Russian, Old Russian, Polish, French, Italian, Spanish, etc.) and so it is pretty necessary to use a unicode set to accommodate this. For quite awhile, Windows default Unicode set is UTF-16le, so that is what I use, and every page within this site has that coded in the header for browsers to recognise. This site had been tested with Firefox, IE, Opera, Safari, Kylo, and even Netscape, and there was no problem. Within the last couple months, however, Firefox has released updates which have garbled my site, and even when I manually set the encoding to UTF-16le, my links to amazon are rendered completely unusable, and if I navigate away from the page and then click back to a page using the back button, Firefox once again renders it as garbage.

所有回复 (1)

more options

The server sends the page as UTF-8. You will have to change that to UTF-16 to avoid such problems. Firefox will ignore a BOM in the file if the server specifies an encoding in the HTTP response headers.