Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

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

  • 3 antwurd
  • 2 hawwe dit probleem
  • 1 werjefte
  • Lêste antwurd fan 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.

Alle antwurden (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.

Bewurke troch jmclvn op