Closed Bug 372375 Opened 18 years ago Closed 9 years ago

please add a preference setting for strict ISO-8859-1 encoding

Categories

(Core :: Internationalization, enhancement)

Product:
Core
Component:
Internationalization
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: davygrvy, Assigned: smontagu)

References

(
URL
)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a3pre) Gecko/20070228 Minefield/3.0a3pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a3pre) Gecko/20070228 Minefield/3.0a3pre I would like to have a preference setting, possibly 'intl.charset.strict' that is a boolean, that allows me not to have the leakage of Windows-1252 characters within iso-8859-1. This shall include entities, too. I want them all as empty boxes as they should be, thank you. Reproducible: Always Steps to Reproduce: 1. Go to http://old.no/charmap/iso-8859-1.html 2. Observe what should be empty spots in the range 128-159 3. Actual Results: no way to override the inaccurate iso-8859-1 encoding. Expected Results: to find a way to set a preference value for standards mode.
Assignee: nobody → smontagu
Status: UNCONFIRMED → NEW
Component: Preferences → Internationalization
Ever confirmed: true
OS: Windows XP → All
Product: Firefox → Core
QA Contact: preferences → i18n
Hardware: PC → All
Version: unspecified → Trunk
some more references. bug 47583 bug 121174
ping.. is this dead?
where in the code are these hacks so I may fix it myself?
I think I found the point of the switch in mozilla/intl/uconv/src/nsISO88591ToUnicode.cpp It #includes cp1252.ut rather than 8859-1.ut
Interestingly, the source contains no comment about the change. I would have thought a well evolved project would full of wonderfully amusing and enlightening comments such as /* Due to the entire population of M$ FrontPage users not knowing to set their encoding value to 'Windows-1252', it has now become our responsibility as the rending agent to do it for them. Whether this is 'The right thing to do' or not is greatly debated. */
I think this option would be useful for authors who want to see their documents the way it is written. Without the deep war story, I was scratching my head quite a lot when I wrote an rss2html server module that accepted everything from RDF 0.9 to Atom. The misunderstanding of encodings in the wild is unbelievable. I had to add quite a lot of special case work to manage it. But to then see FireFox not displaying text accurately was also a shock and the reason for this request. How can I tell when I had dangerous characters slip through if FireFox is munging this for me? http://www.cs.tut.fi/~jkorpela/www/windows-chars.html
Simon points to two places that need config switches: Bug 288904#c34
Suggest wontfix. This is the way the web works, and you shouldn't be using those code points anyway.
Status: NEW → UNCONFIRMED
Ever confirmed: false
Actually you have that inverted. Yes, I don't want to use those code points, but FF gives me characters
We implement https://encoding.spec.whatwg.org/
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
http://old.no/charmap/iso-8859-1.html is still displayed wrong
No characters should be shown in the range 7F thru 9F. There is nothing there: http://ftp.unicode.org/Public/MAPPINGS/ISO8859/8859-1.TXT
You need to log in before you can comment on or make changes to this bug.