We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

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

  • 1 Antwort
  • 1 hat dieses Problem
  • 6 Aufrufe
  • Letzte Antwort von Shadow110

more options

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 Antworten (1)

more options

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++