Closed Bug 21209 Opened 25 years ago Closed 25 years ago

Japanese Hiragana does not display when certain Big5 fonts are installed

Categories

(Core :: Internationalization, defect, P3)

Other
Linux
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: momoi, Assigned: ftang)

Details

(Whiteboard: have fix. waiting for open tree.)

** Observed with 12/8/99 Linux build **

I have some Big5 fonts installed on my Linux box (mugen).
Recently Erik has made it possible to use Big5 fonts with
"..et-0" suffix.

For example the following font is on my Linux box.

-eten-taipei-medium-r-normal--16-150-75-75-c-160-big5.et-0

The problem is that I can't see Japanese Hiragana any more
in Browser, Composer, and Messenger. Apparently, we use this
font ahead of a Japanese font.

When the font pref is enabled for Unix, this problem can be
avoided. But in any case, we need to find a solution for M12.
Status: NEW → ASSIGNED
Target Milestone: M13
We should use the CP950 conversion instead of the current one. The current one
have HIRAGANA defined but it is not common in any BIG5 font.
I have use the microsoft CP950.TXT to build our Big5 conversion table in my
local tree to fix this problem. Need to wait till tree open to check in.
Whiteboard: have fix. waiting for open tree.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
change the big5.uf and big5.ut to use the microsoft CP950.TXT conversion table
instead of the unpopluar Taligent table.
teruko, if you want me to verify this, I'll be appy to do it.
Just re-assign the task to me.
QA Contact: teruko → momoi
I changed QA contact to momoi@netscape.com.
Status: RESOLVED → VERIFIED
** Checked with 1/3/99 Linux build **

I re-installed my Taipei fonts (16 & 24 pts).
Then I compared the above build with the M12 release build.
The new build can display all Kana characters even with these
Big 5 fonts. On the other hand, the M12 build cannot.
This proves that the problem has been resolved in M13 builds
later than 12/21/99.

Marking the fix verified.
You need to log in before you can comment on or make changes to this bug.