20790 - add keyboard short cut to a user preferred encoding

Status: VERIFIED WONTFIX

(Core :: Internationalization, enhancement, P3)

Description

[Eugene Savitsky]

I wish to customize preferred codepage to keyboard shourtcut or to right click
menu. Example:

CTRL-K - KOI8-R
CTRL-W - Win1251
etc.

or by right click in submenu.

-------------
xxxxxxxx     |
xxxxxxxxx    |
xxxxxxxxxxx  |
xxxxxxxxxx   |
Codepage ->  |-----------
-------------| KOI8-R   |
             | WIN1251  |
             ------------

Comment 1

[cata]

Hmm, can I mark this one "food for thought"? :))) Marking just M13 for now.

Comment 2

[bobj]

This won't make it for Beta.  Put it on the M20 list for later consideration.

Comment 3

[Eugene Savitsky]

It can be smth like CTRL-right click menu (different from "just right click")

Comment 4

[Frank Tang]

we should talk to UI person to allocate 3-5 control key for encoding menu and 
allow user to customize it. bobj- can you talk to ui folks to allocate it ?

Comment 5

[Frank Tang]

mark it as M23

Comment 6

[Frank Tang]

Change the summary to 
add keyboard short cut to a user preferred encoding

Comment 7

[bobj]

[e-mail],
For labeled pages, invoking the Character Coding menu is unnecessary.
Have you tried using the
     View|Character Coding|Auto-Detect|Auto-Detect (Russian)
The Netscape Commercial build also includes
    View|Character Coding|Auto-Detect|Auto-Detect (All)

This should make it so that no user intervention is needed.

Reassigning the UI request to German.

Comment 8

[Eugene Savitsky]

So? Are we gonna close the bug?

Comment 9

[bobj]

Did my alternative work for what you need?
IMHO, we should add short-cut keys to only things that be used frequently by
many users.  The hope, with the auto-detection feature, was to actually
minimize the user interaction with the Character Coding menu.  The expectation
is that the menu is there when pages are not labeled, not auto-detectable, or
mislabeled.

Do you think the short-cut key would be used a lot?  If not, please close
the bug.  Otherwise, let's discuss the usability issues.  Maybe there are
other alternatives.  Thanks.

Comment 10

[Eugene Savitsky]

I believe that when the bug was filled there wasn't autodetect yet, or it 
doesn't worked.

I belive this bug autodetect is covered by autodetecting.

Tnx.

Comment 11

[bobj]

Closing as WONTFIX.  Please file another bug if the autodetection does not
work as "advertised"! :-)

Comment 12

[Teruko Kobayashi]

Verified as wonfix.