Enable the Character Encoding menu for Chinese and Korean by default (Cyrillic locales too?)

RESOLVED WONTFIX

Status

()

Firefox for Android
General
RESOLVED WONTFIX
6 years ago
5 years ago

People

(Reporter: xti, Unassigned)

Tracking

Trunk
ARM
Android
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
Firefox 16.0a1 (2012-06-28)
Device: Galaxy Nexus
OS: Android 4.0.2

Steps to reproduce:
1. Change OS language to Japanese
2. Open Fennec
3. Go to Menu > Setting > Character Encoding and verify if the 1st option (Show Menu) is selected
4. Repeat all steps by changing the OS language at step 1 to Chinese and Korean

Expected result:
For all languages with special characters, the Character Encoding menu is enabled by default.

Actual result:
The Character Encoding menu is enabled by default just for Japanese.

Note:
Cyrillic locales should have the same facility too.
Japanese is the only that has multiple for it's language; I think the bigger problem is that we should allow for more encoding.

Comment 2

6 years ago
I'm not sure this should be consistent per script or latin-ishness of that.

This is more about how bad sites in the affected regions are in sending the correct http headers.

Note, the source code is http://mxr.mozilla.org/l10n-mozilla-beta/search?string=showCharacterEncoding&find=mobile%2Fandroid&findi=&filter=^[^\0]*%24&hitlimit=&tree=l10n-mozilla-beta
Summary: Inconsistency for Character Encoding menu for Japanese, Chinese and Korean (Cyrillic locales too?) → Enable the Character Encoding menu for Chinese and Korean by default (Cyrillic locales too?)
What's the rationale for enabling this for Chinese and Korean? In practice, there's one Korean legacy encoding (EUC-KR), one zh-TW legacy encoding (Big5) and one zh-CN legacy encoding (GBK).

We should not enable the menu in more locales by default without a clear need.
I agree with your explanation Henri.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.