Closed
Bug 255319
Opened 20 years ago
Closed 20 years ago
Korean Unix fonts problem
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 254585
People
(Reporter: jongampark, Assigned: bugzilla)
References
()
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a3) Gecko/20040811 Firefox/0.9.1+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a3) Gecko/20040811 Firefox/0.9.1+
With the previous version, Unix Korean fonts, like Un Batang, Un Bom, Un Philgi,
and so on, can be used on MacOS X / Firefox. However with current version,
Korean characters when the Unix fonts are chosen to be used are displayed as
rectangles.
Reproducible: Always
Steps to Reproduce:
1. Set Korean pages to use your own Unix Korean fonts like Un-something with
appropriate preference setting.
2.
3.
Actual Results:
All Korean characters are drawn as rectangles
Expected Results:
Nice Korean characters
What is the version of OS?
Which font is Unix Korean fonts concretely?
What kind of font is it?(TrueType, OpenType, etc.)
Does a problem come out with OS standard font?
Reporter | ||
Comment 2•20 years ago
|
||
(In reply to comment #1)
> What is the version of OS?
> Which font is Unix Korean fonts concretely?
> What kind of font is it?(TrueType, OpenType, etc.)
> Does a problem come out with OS standard font?
>
OS : MacOS X version 10.3.5
Fonts :
Un Batang
Un Bom
Un Dotum
Un Gungseo
Un Pilgi
Un Shinmun
Un Yetgul
Un Pen
Un penheulim
What kind of font is it? : TrueType Unicode
Does a problem come out with OS standard font? NO
P.S. It worked with previous version of the Firefox.
It can also means that the Firefox on Linux can have this problem. Because those are Unix fonts.
Comment 3•20 years ago
|
||
This is a result of the fix to bug 120401 (read comments from jshin about these
fonts).
It is being dissuced in bug 254585
*** This bug has been marked as a duplicate of 254585 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•