Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Avatar for Username

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.

Why isn't Firefox displaying a character right, but Chrome is?

  • 1 antwurd
  • 1 hat dit probleem
  • 16 werjeftes
  • Lêste antwurd fan Shadow110

frebe01
frebe01
mear opsjes

When I used NotePad++ to write 1 character from the ascii insertion panel, value 131, hex 83 "ƒ" (I did this as a 1 character file n saved it as 1letter.txt n 1letter.htm, it displayed as 198, hex C6 "Æ" (sans the ""), but not just Æ

There's a comma where an apostrophe would normally be

It's too ƒricking weird

Why isn't it displaying value 131, hex 83 "ƒ"?

Chrome displays value 131, hex 83 "ƒ" perfectly

ƒrebe

When I used NotePad++ to write 1 character from the ascii insertion panel, value 131, hex 83 "ƒ" (I did this as a 1 character file n saved it as 1letter.txt n 1letter.htm, it displayed as 198, hex C6 "Æ" (sans the ""), but not just Æ There's a comma where an apostrophe would normally be It's too ƒricking weird Why isn't it displaying value 131, hex 83 "ƒ"? Chrome displays value 131, hex 83 "ƒ" perfectly ƒrebe

Alle antwurden (1)

Shadow110
Shadow110
mear opsjes

Hi, as Notepad++ sticks formatting code into things it is possible that is the reason. Firefox does not do UTF8 but not sure as to doing ascii just know that it does stick formatting in to the page.

There is an Encoding menu under the Format menu somewhere. Could you check in the lower right corner of Notepad++ what character encoding is being used for your documents. Some encodings, particularly UTF-16 encodings,

Best I can do at the moment as do not use notepad++