Closed
Bug 20701
Opened 25 years ago
Closed 25 years ago
Character Set menu items should not clutter View menu
Categories
(Core :: Internationalization, defect, P3)
Core
Internationalization
Tracking
()
People
(Reporter: german, Assigned: cata)
Details
With build in recent days I have noticed that the Character set optioins have
greatly expanded in the view menu. This is overly cluttering this important
menu. I do undertand that you need to represent the relation ship between main
character set (e.g ISO) and sub-character set (e.g. Western ISO-8859-1). But
while this terminology is useful for an esteemed subset of our user base, namely
those who understand what those cryptic abbreviations mean, for the rest it will
unacceptably clutter the view menu. I suspect even those users who are in need
for a international character set do not appreciate the way its being presented.
I am in favor of having one item Character Set... that gets you to a dialog with
two select list, in the first you have the main character set groups, and
dependent on its selection you show the subgroups in the second list. This will
map better to the usage fo this feature.
Updated•25 years ago
|
Assignee: ftang → cata
Comment 1•25 years ago
|
||
The current items list there is simply a work around because XP toolkit group
have not fix the long menu scrolling issue and our charset menu customization
work have not done yet.
Right. Also, the future Character Set menu is there too, and when it will be
fully functional the present Character Set menu options will be removed. Bug
#15482.
Comment 3•25 years ago
|
||
German, I sent you a link to the proposal on the Browser Character Coding
Menu this week. It's found here:
http://www.mozilla.org/projects/intl/uidocs/browsercharmenu.html
Would you look it over and send us your comments/suggestions?
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 6•25 years ago
|
||
Read 15482 and I'm verifing this as a dup of that bug.
You need to log in
before you can comment on or make changes to this bug.
Description
•