This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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

Quotation marks display as &quot in web pages, I'm using Unicode UTF-8 character encoding.

  • 3 replies
  • 2 have this problem
  • 1 view
  • Paskiausią atsakymą parašė jmclvn

more options

On many web pages, where a quotation mark character should appear, instead the page displays the text &quot. I believe this happens with other punctuation characters as well such as apostrophes although the text displayed in these other cases is different, of course. I'm guessing this is a problem with character encoding. I'm currently set to Unicode (UTF-8) encoding. Have tried several others without success.

On many web pages, where a quotation mark character should appear, instead the page displays the text &quot. I believe this happens with other punctuation characters as well such as apostrophes although the text displayed in these other cases is different, of course. I'm guessing this is a problem with character encoding. I'm currently set to Unicode (UTF-8) encoding. Have tried several others without success.

All Replies (3)

more options

Can you give a link as an example?

It is possible that the text was copied from an other source and that the & was HTML encoded a second time as & and appears as such in the page code.
If the HTML entity is used then the encoding shouldn't matter.

more options

Here's a link where the problem occurs. Note the second line of the main body of text.

http://www.sierratradingpost.com/lp2/snowshoes.html

BTW, I never use IE, but I checked this site in IE and it shows the same problem, so maybe it is the page encoding after all rather than what I thought.

In any case, my thanks for your help and would appreciate any solution you can suggest.

more options

Probably mis-posted my reply to your request. See post above.

Modified by jmclvn