搜索 | 用户支持

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

详细了解

Two characters now display incorrectly (only at one site)

  • 2 个回答
  • 1 人有此问题
  • 8 次查看
  • 最后回复者为 Bob Jersey

more options

At homeoint.org, which I am not sure is that well-updated, as of last week, and not on all its pages, the characters 'Æ/æ' and 'Œ/œ' now display as 'Ć/ć' and 'Ś/ś', respectively. Other browsers also exhibit this problem. Checking the encoding it sometimes is set to Central European (Windows); if it is reset to Western they display correctly. Wasn't there a way to make FF remember a given encoding for a particular site?

At homeoint.org, which I am not sure is that well-updated, as of last week, and not on all its pages, the characters 'Æ/æ' and 'Œ/œ' now display as 'Ć/ć' and 'Ś/ś', respectively. Other browsers also exhibit this problem. Checking the encoding it sometimes is set to Central European (Windows); if it is reset to Western they display correctly. Wasn't there a way to make FF remember a given encoding for a particular site?

被采纳的解决方案

All the pages linked from http://www.homeoint.org/books/boericmm/index.htm have the capital Œ on them, others tend to vary with the terminology in them. I also set encoding to Western and haven't seen the problem; hopefully that's all that was needed.

定位到答案原位置 👍 0

所有回复 (2)

more options

I'm not seeing the characters you mention on the main page, so can't check for issues.

Do you see these characters on a specific page?

This website is created using Microsoft FrontPage and is send by the server as windows-1252. These days websites should be using Unicode and not an 8-bit Western or Windows encoding to prevent issues.

I have Western selected for the encoding (View -> Text Encoding) if I open the main page. It is possible that some pages are send by a different encoding or with no encoding send by the server.

more options

选择的解决方案

All the pages linked from http://www.homeoint.org/books/boericmm/index.htm have the capital Œ on them, others tend to vary with the terminology in them. I also set encoding to Western and haven't seen the problem; hopefully that's all that was needed.