Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

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

  • 5 replies
  • 14 have this problem
  • 8 views
  • Last reply by 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.

Chosen solution

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.

Read this answer in context 👍 2

All Replies (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 ;-)

Modified by 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

Chosen Solution

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.

Modified by cor-el

more options

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

more options

You're welcome