搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

Why does FF not properly display .htm web pages created in Word, and how can I fix this?

  • 5 回覆
  • 14 有這個問題
  • 7 次檢視
  • 最近回覆由 cor-el

more options

I create my web page using Word, and recently upgraded to 14.0.1. The updated web page displays fine in Mac Safari, or Chrome, but not in FF; rather is displays as junk characters. I realize this is likely due to lines added to the .html code by MS Office, but I think FF should be able to parse it if Safari and Chrome can. Thank you for any help.

I create my web page using Word, and recently upgraded to 14.0.1. The updated web page displays fine in Mac Safari, or Chrome, but not in FF; rather is displays as junk characters. I realize this is likely due to lines added to the .html code by MS Office, but I think FF should be able to parse it if Safari and Chrome can. Thank you for any help.

被選擇的解決方法

That is a page saved as Unicode UTF-16LE, but send by the server as UTF-8.

View > Character Encoding > More Encodings > Unicode > UTF-16LE

You either need to save the page as Unicode UTF-8 or configure the server to send the page(s) as UTF-16. The first is probably easier to do.

從原來的回覆中察看解決方案 👍 2

所有回覆 (5)

more options

I am just guessing but maybe the web page has been designed specifically to use MS office or IE none standard features. Run your code through the W3C validator http://validator.w3.org/


P.S I must remember to read the System Details provided before posting comments ;-)

由 John99 於 修改

more options

The W3C validator won't help him, the code is so bad the validator won't checl it.

Opera doesn't display that page either.

http://kompozer.net/

more options

選擇的解決方法

That is a page saved as Unicode UTF-16LE, but send by the server as UTF-8.

View > Character Encoding > More Encodings > Unicode > UTF-16LE

You either need to save the page as Unicode UTF-8 or configure the server to send the page(s) as UTF-16. The first is probably easier to do.

由 cor-el 於 修改

more options

I saved with UTF-8 encoding and that fixed it. Thank you.