205767 - Turkish, Georgian, Armenian at wrong place - Character Coding/SE & SW Asian

Status: RESOLVED FIXED

(Core :: Internationalization, defect)

Description

[Biju]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030504 Mozilla Firebird/0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030504 Mozilla Firebird/0.6

At present "View/Character Coding/More/SE & SW Asian" contains Turkish,
Georgian, Armenian.
But "Turkish" should be in "Middle Eastern"
"Georgian", "Armenian" should be in "Russian" or something


Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Biju]

s

Comment 2

[Simon Montagu :smontagu]

This is internationalization. The Bidi component is for bugs with right-to-left
languages.

Comment 3

[Simon Montagu :smontagu]

This has come up before, see bug 93237 comment 2.

Comment 4

[Vahe Khachikyan]

(In reply to comment #0)
> "Georgian", "Armenian" should be in "Russian" or something
Sorry but the suggestion above is a nonsence!
Georgian and Armenian languages might not be put under Russian group
because at least Armenian is linguastically nearer to Latine (yep I mean that
old dead predecessor of all current Westeuropean languages) then to Russian. 

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Jungshik Shin]

Turkish in SW Asia (well, a part of it is in Europe :-)) is more or less right
although I don't like the idea of bundling South East Asia (Vietnamese, Thai),
South Asia (Hindi and other Indic), South West Asia (Turkish), Armenian and
Georgian into a gigantic 'SE & SW Asia' . Because we already have Middle East
(which is not a neutral but Euro-centric term), perhaps Turkish should be moved
there (although it sometimes regarded as belonging to 'Near East' : again
Euro-centric). We can change the label 'SE & SW Asia'  to 'South and SE Asia'
for Thai, Vietnamese, Hindi and others. 

What to do with Georgian and Armenian? That's tough... 

Comment 7

[Biju]

Rename "SE & SW Asian" to "Other"

(In reply to comment #4)
> (In reply to comment #0)
> > "Georgian", "Armenian" should be in "Russian" or something
> Sorry but the suggestion above is a nonsence!

absolutely not a nonsense, 
please read my comments carefully it ends with "or something" 
so point I raised is "Georgian" and "Armenian" is not in "SE & SW Asian"  

Comment 8

[Ahmet Serkan Tıratacı]

Any improvement here? Will any authority ever spend some time to comment on this bug?

Comment 9

[Biju]

Attachment: encoding.png

Comment 10

[Amir Aharoni]

This bug is still relevant in Fx 2.0.0.6. This IS a bug: When i tried to find the right encoding for the Armenian site http://www.iravunk.com/ , it took me quite a few seconds; "SE & SW Asian" is very unintuitive.

BTW, this is the first bug that comes up when one searches Bugzilla for the word "Armenian".

None of these languages shouldn't be in "Russian", of course.

Middle Eastern is probably OK geographically, but wrong linguistically and politically - Turkey, Armenia and Georgia are doing great efforts to present themselves as European countries.

Armenian and Georgian are probably most similar to Greek linguistically - their writing systems are left-to-right and alphabetic, but non-Latin. Greek is Western European.

Maybe you can make a new group called South European.

Maybe it would be best to simply put all non-Cyrillic European alphabets, including Arm. and Geo. into "European" and put Cyrillic separately.

I don't know...

Comment 11

[Henri Sivonen (:hsivonen) (not reading bugmail until 2025-02-06)]

This was fixed by bug 805374. (The part about Georgian was fixed earlier.)

Specifically:

 * Firefox no longer supports ARMSCII-8 or GEOSTD8. They aren't needed for Web compatibility, aren't supported by other browsers and are not part of the Encoding Standard. (Firefox does take steps to make pages that are ARMSCII-8-encoded but declared as x-user-defined in <meta> plus a font to render in a readable way.)

 * The Character Encoding menu is now flat so Turkish is on the top level like all other items.