71484 - 10646 X fonts country in 'additional-style' field

Status: RESOLVED INVALID

(Core :: Internationalization, defect)

Description

[kill this account]

it appears that some 10646 x fonts have a language indicator.

We need to take a look at this.

From bug 27378:
========================================================================
Yet another field might be necessary to differntiate between fonts like
the following:

-misc-fixed-medium-r-normal-ja-13-120-75-75-c-120-iso10646-1
-misc-fixed-medium-r-normal-ja-18-120-100-100-c-180-iso10646-1
-misc-fixed-medium-r-normal-ko-0-0-100-100-c-0-iso10646-1
-misc-fixed-medium-r-normal-ko-18-120-100-100-c-180-iso10646-1

These fonts are shipped by default in XF86 4.0.x and everything is identical
except for the 'additional-style' field which is empty for most X11 fonts.
Do I have to file a new bug for this? 

Jungshik Shin
=========================================================================

Comment 1

[Andreas Becker]

Changing QA Contact to [e-mail].

Comment 2

[Frank Tang]

bstell- this is good information. But what is THE BUG ? or THE FEATURE? What will 
make this "issue/feature/bug" CLOSED ?
Mark it as FUTURE for now.

Comment 3

[kill this account]

here is my current thinking regarding these fonts:

1) they should be sorted into the font pref list for the appropriate language

2) when selecting a fallback font we should consider the language attribute

Comment 4

[Jungshik Shin]

  There's a more urgent need for distinguishing fonts
with everything equal except for 'additional-style' field in XLFD.
I wrote about this about a year ago in mozilla I18n newsgroup(and Erik
may remember this).  As it stands, Mozilla font selection menu doesn't
offfer any means by which  users can  know which font is selected if
two fonts have the identical values in all the XLFD fields except for
'additional-style' field. I supsect Mozilla doesn't know, either and it
just puts itself at the disposal/whim of X server/font server.

  For instance, I want to specify explicitly the following font

   -misc-fixed-medium-r-normal-ko-18-120-100-100-c-180-iso10646-1

  instead of

   -misc-fixed-medium-r-normal-ja-18-120-100-100-c-180-iso10646-1

for both UTF-8 and Korean encodings because the former has all the
glyphs for 11172 Hangul syllables while the latter does not.


  BTW, I found I cannot choose fonts with 'iso10646-1' any more for
encodings other than UTF-8. I guess some thought has to be given to
whether it's better this way or not. It could be desirable to let users
pick iso10646-1 font for (some) encodings which are not Unicode-based.

Comment 5

[Jungshik Shin]

JS>  BTW, I found I cannot choose fonts with 'iso10646-1' any more for
JS> encodings other than UTF-8. I guess some thought has to be given to
JS>  whether it's better this way or not. It could be desirable to let users
JS> pick iso10646-1 font for (some) encodings which are not Unicode-based.

  Perhaps, this issue should be discussed in  bug 41721 and bug 58412.
There's a thread in mozilla I18N newsgroup/mailing list on the issue  as
well (started by James Su <[e-mail]>). See
<news://news.mozilla.org/[e-mail]> and its follow-ups.

Comment 6

[Frank Tang]

give this to shanjian

Comment 7

[Frank Tang]

shanjian is no longer working on mozilla for 2 years and these bugs are still
here. Mark them won't fix. If you want to reopen it, find a good owner first. 

Comment 8

[Travis Chase]

Mass Re-open of Frank Tangs Won't fix debacle. Spam is his responsibility not my own

Comment 9

[Travis Chase]

Mass Re-assinging Frank Tangs old bugs that he closed won't fix and had to be
re-open. Spam is his fault not my own