214769 - a couple of more registry-encoding pairs for ISO10646 identity mapping fonts

Status: RESOLVED FIXED

(Core :: Internationalization, defect)

Description

[Jungshik Shin]

Currently, Mozilla (GFX:Gtk, GFX:Xlib) recognizes the
following registry-encoding pair (the last 2 fields of XLFD) as ISO 10646 font
(the identity mapping between the font glyph indices and ISO 10646 BMP code
points. of course, the mapping is sparse)

   iso10646-1
   ucs2.cjk-0
   ucs2.cjk_japan-0
   ucs2.cjk_korea-0
   ucs2.cjk_taiwan-0
   ucs2.cjk_china-0

Apparently, HP/UX uses a few other registry-encoding pairs and I was asked to
support them as well. As soon as I get registry-encoding pairs, I'll make a patch.

Comment 1

[Mi-Young Lee]

HP-UX uses "iso10646.2000-cn" for Simplified Chinese and "korean.ucs2-0" for 
Korean. These should be supported.

Comment 2

[Jungshik Shin]

Thanks. How about Japanese and TC? What does HP/UX use? jisx0213 (not 0212 or
0208) and cns11643* ? 

Comment 3

[Mi-Young Lee]

We are not providing ISO 10646 fonts for Japanese and T-Chinese.

Comment 4

[Jungshik Shin]

Attachment: a patch (4-liner :-)

OK. Then, I'll just take care of two registry-encoding pairs here.

Comment 5

[Jungshik Shin]

Comment on attachment 129295 [details] [diff] [review]
a patch (4-liner :-)

asking the usual suspects :-) for r/sr
this is a simple fix for HP/UX (Gfx:Gtk, Gfx:Xlib)

Comment 6

[Simon Montagu :smontagu]

Comment on attachment 129295 [details] [diff] [review]
a patch (4-liner :-)

r=smontagu

Comment 7

[Jungshik Shin]

Comment on attachment 129295 [details] [diff] [review]
a patch (4-liner :-)

Thanks for r/sr.

Asking for a1.5b. This is a very low risk patch, but important for HP/UX build.
Without this patch, on HP/UX, some Korean characters won't be rendered. I
removed the fallback rendering code in bug 214743 expecting this to be	fixed
in tandem.

Comment 8

[chris hofmann]

Comment on attachment 129295 [details] [diff] [review]
a patch (4-liner :-)

approved for 1.5b landing

Comment 9

[Jungshik Shin]

Fix was checked into the trunk 
 

Comment 10

[Mi-Young Lee]

When I test with the build that includes fixs for 152264(not the latest 
patch),214743,214769,206060 and 213880 on HP-UX, I have the following questions.

- For Korean, ksc5601.1987-0 and ksc5601.1987-1 fonts are listed.
- For S-Chinese, iso10646.2000-cn and korean.ucs2-0 are listed besides 
gb2312.1980-1. Why are korean.ucs2-0 fonts listed?
- For T-Chinese(Taiwan), iso10646.2000-cn and korean.ucs2-0 are listed besides 
some fonts. Why are they listed? and "hpbig5-" is not listed.
- For T-Chinese(Hong Kong), iso10646.2000-cn and korean.ucs2-0 are listed 
besides "hphkbig5-". Why are they listed?
- For Japanese, iso10646.2000-cn and korean.ucs2-0 are also listed besides some 
fonts. Why are they listed?

Comment 11

[Jungshik Shin]

That's by design in a sense. I forgot the bug number, but the patch for that bug
made Mozilla list fonts matching langGroup/styles first and then the horizontal
rule (as a delimeter)  followed by the rest of fonts  regardless of
langGroup/styles. 

For instance, for SC, the following is normal

  gb2312.1980-1 font1
  gb2312.1980-1 font2
  iso10646.2000-cn font
  ......
  --------------------        <=== the delimeter
  korean.ucs2-0 font
  iso10646 fonts (other than iso10646.2000-cn)

BTW, is korean.ucs2-0 listed above the delimeter for Korean? It should be. 

As for hpbig5- not being listed, it might be due to 'hpbig5-*' taking place of
'hpbig5-'. Let's discuss it in bug 206060.