33930 - recognize iso-8859-8-i, iso-8859-8-e, iso-8859-6-i, iso-8859-6-e

Status: RESOLVED FIXED

(Core :: Internationalization, defect, P3)

Description

[bobj]

We need to recognize iso-8859-8-i and iso-8859-8-e charsets, so that
AT LEAST we pick up the correct fonts.

If we add visual Hebrew support we will need the character coding menu to
set iso-8859-8-e.

Comment 1

[bobj]

Correction to my last comment.  According to
 http://www.w3.org/TR/html401/struct/dirlang.html#h-8.2.5

    The parameter value "ISO-8859-8" (for Hebrew) denotes visual encoding,
    "ISO-8859-8-i" denotes implicit bidirectionality, and "ISO-8859-8-e"
    denotes explicit directionality.

So visual Hebrew should use iso-8859-8.

Comment 2

[bobj]

For the Unicode converters, we should convert 8859-8-* using the 8859-8
converter and the font subsystem should map 8859-* to the same "language group"
as it does 8859-8.

Comment 3

[bobj]

We should do the same for Arabic: iso-8859-6-i and iso-8859-6-e

Comment 4

[bobj]

From
   ftp://ftp.isi.edu/in-notes/iana/assignments/character-sets

here's the specific (case insensitiv) name and aliases to be supported:

  Name: ISO_8859-6-E
  Alias: csISO88596E

  Name: ISO_8859-6-I 
  Alias: csISO88596I

  Name: ISO_8859-8-E
  Alias: csISO88598E

  Name: ISO_8859-8-I
  Alias: csISO88598I

Comment 5

[bobj]

ftang already has bug 32290 "treat gb2312 label as though it were GBK"

Comment 6

[Frank Tang]

OK I will add them with different charset alias resolution but use the same 
converter.

Comment 7

[Frank Tang]

fixed and check in

Comment 8

[Frank Tang]

mark it M15 so QA will verify it.

Comment 9

[moshev]

I checked it with http://www.qsm.co.il/Hebrew/qasheia.htm using
build 2000040512. Looks fine (at least for iso-8859-8-i)

Comment 10

[Teruko Kobayashi]

Laura, please verify this.