Closed
Bug 647566
Opened 14 years ago
Closed 10 years ago
Remove "Unicode" submenu from encoding menu
Categories
(Core :: Internationalization, defect)
Core
Internationalization
Tracking
()
RESOLVED
FIXED
People
(Reporter: emk, Assigned: smontagu)
Details
(Whiteboard: [fixed by bug 805374])
Our UTF-16 decoder can detect byte order reliably, so UTF-16BE and UTF-16LE will just confuse users. No other browsers have three choices for UTF-16 family. Safari and IE cannot even select UTF-16 manually. If UTF-16BE or UTF-16LE is absolutely required, users can add them from "Customize List...".
Also UTF-8 is redundant because it's already appear in the highest-level submenu.
Thus we can remove "Unicode" submenu completely, IMO.
Simon, what do you think about this?
Comment 1•14 years ago
|
||
(In reply to comment #0)
> Our UTF-16 decoder can detect byte order reliably,
This should be true for HTML, but it is not necessarily as reliable for plain-text content....
> so UTF-16BE and UTF-16LE
> will just confuse users. No other browsers have three choices for UTF-16
> family. Safari and IE cannot even select UTF-16 manually. If UTF-16BE or
> UTF-16LE is absolutely required, users can add them from "Customize List...".
....but I'd agree that the use-case for these is sufficiently obscure that they don't need to be in the primary UI, and could be relegated to "Customize...".
Comment 2•10 years ago
|
||
Fixed by bug 805374.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Whiteboard: [fixed by bug 805374]
You need to log in
before you can comment on or make changes to this bug.
Description
•