Closed
Bug 47836
Opened 25 years ago
Closed 25 years ago
In LANG=ko, font is too big.
Categories
(Core :: Internationalization, defect, P3)
Tracking
()
VERIFIED
FIXED
People
(Reporter: eungkyu, Assigned: bstell)
Details
(Keywords: intl, relnote, Whiteboard: relnote-user)
Attachments
(3 files)
|
143.33 KB,
image/jpeg
|
Details | |
|
163.22 KB,
image/jpeg
|
Details | |
|
625 bytes,
patch
|
Details | Diff | Splinter Review |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.0-test5 i686; en-US; m17) Gecko/20000804
BuildID: 2000080404
My environment LANG is ko or ko_KR.eucKR.
In this environment, Browser's all font is big,
such as menu, url, bookmark and so on.
and all korean in contents is big.
Not in LANG=C (except contents)
Reproducible: Always
Steps to Reproduce:
1.execute LANG=ko_KR.eucKR ./mozilla
2.execute LANG=C ./mozilla
3.compare this two.
Actual Results: ...font is big
Expected Results: good size of font
Comment 1•25 years ago
|
||
Bom-Shik, is there a bug already file for this problem?
Comment 3•25 years ago
|
||
Bom-Shik, can you reproduce? If so, please confirm the bug.
I can't really confirm this now - no KO locale in my test environment.
URL: (not about URL)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 5•25 years ago
|
||
I checked my Redhat linux 6.2 JA. Korean locale is not installed.
We need to get Korean Locale package to reproduce this.
I do not know how we can get it.
cc'd tajima@eng.sun.com,katakai@japan.sun.com. They may have some ideas.
Comment 6•25 years ago
|
||
Eungkyu, could you tell us where to get Korean locale?
Comment 7•25 years ago
|
||
This seems a known issue that erik work around some other problem.
reassign to erik. Don't try to fix this untill erik back.
The main reason erik hack this way for CJK locale is sometime we cannot find a
CJK font in the normal default UI size (which is too small for CJK fonts). I
remember he work around that problem by checking the LANG and do a minimun size
setting for CJK locales.
Assignee: nhotta → erik
| Reporter | ||
Comment 8•25 years ago
|
||
You can find korean locale in
Debian main stream (of course, deb package locale-ko) or
ftp://ftp.linuxkorea.co.kr/pub/ALZZA/version-6.2/i386/ALZZA/RPMS/locale-ko-
2.1.3-1az.noarch.rpm.
There are good 12 point korean font, and
we can see 10 point font.....|-)
ps. which i select below radio buttons?
Leave as NEW
Accept bug(changing ...)
Resolve buf, changing resu....
.
.
.
Comment 9•25 years ago
|
||
Q: which i select below radio buttons?
A:Eungkyu Song = You should not touch it. Erik will do that after he come back
from sabbitical.(8/29)
Add jshin@pantheon.yale.edu to the cc list
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Comment 10•25 years ago
|
||
Comment 11•25 years ago
|
||
Comment 12•25 years ago
|
||
I've just attached two screenshots with LANG=C and LANG=ko_KR.eucKR.
I don't see any difference btween two cases
and accordingly at a loss as to what this bug is about. Perhaps,
due to differences in repertoires of Korean fonts between me and
Enugkyu, I cannot reproduce what he found. Anyway, it'd be nice
if Eungkyu can attach two screenshots clearly showing what's wrong.
| Reporter | ||
Comment 13•25 years ago
|
||
I found that bug is not serious bug. This is just hack for CJK font.
I think Eric could not find small CJK font.
Park Won-kyu tell me that package/defaults/pref/unix.js file has this line.
pref("font.min-size.variable.ko", 16);
pref("font.min-size.fixed.ko", 16);
This is the problem. I prefer 10. There are good 10 point korean font.
This is "baekmuk gulim" font. (of course free, I think this font must be
default korean font in Xfree86 instead of "daewoo mincho").
Comment 14•25 years ago
|
||
You don't have the problem you reported any more if you set
font.min-size.{variable,fixed}.ko to 10, do you? Hmm, then why don't
have that problem even with those variables left as shipped (i.e. set to
16)? Could it be because I select a profile for M15 which doesn't
have those two variables? Or is it because I explicitly changed my font setting to some other Korean fonts? As for Baekmuk, I'm not sure it's good enough. In my eyes, it's far from good and has to go a long way. Anyway, that's to be dealt with in other forum as it's an XF86 issue.
Comment 15•25 years ago
|
||
M15 is quite old, and font.min-size is quite new.
Comment 16•25 years ago
|
||
The reason I wasn't able to reproduce the bug was I didn't know what
the bug is about until I got Eungkyu's message in Korean. It would have
been much easier for me to get it had he posted two screenshots
with two variables in question in unix.js set to 16(as shipped) and
10(as he wishes them to get changed to). Anyway, what he's suggesting is there's no need
for set the min. font size to 16 at least for Korean because most, if not all,
Korean Linux users have access to Korean fonts as small as 10pixel, which has been true even without
Baekmuk. I agree with him and unless there'e any significant problem in setthing those
two variables to 10, I guess it's better to set them to 10(or 12) instead of 16.
Comment 17•25 years ago
|
||
> M15 is quite old, and font.min-size is quite new.
I did use the latest nightly build (see my screenshots), but I used
the profile for M15 when making them. However, that didn't seem
to affect anything as the nightly build I used(2000-09-06-xx)
has two variables in question in unix.js. Also, when I tried again with
a newly generated profile for the build I was trying, nothing changed (because
I didn't look for what Eungkyu was talking about). Anyway, this
is just for letting you know what I did and the previous comment
has something of importance regarding this bug.
| Reporter | ||
Comment 18•25 years ago
|
||
Why don't you change
pref("font.min-size.variable.ko", 16);
pref("font.min-size.fixed.ko", 16);
to
pref("font.min-size.variable.ko", 12);
pref("font.min-size.fixed.ko", 12);
.
size 16 is too big.
Comment 19•25 years ago
|
||
I agree. Even 10 should be considered. Virtually every Korean
Linux users have Hangul fonts with 10pixel size (or truetype fonts) and it couldn't
be a valid reason for setting it to 16 that the standard X11
distibution only comes with 16pixel fonts for Korean.
Falling short of that, at least Release Note should mention that
those with smaller/scalable fonts may wish to change the
setting.
Updated•25 years ago
|
Whiteboard: relnote-user
Comment 20•25 years ago
|
||
reassign to bstell and clear Future
Assignee: erik → bstell
Status: ASSIGNED → NEW
Target Milestone: Future → ---
| Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Comment 21•25 years ago
|
||
Changed QA contact to andreasb@netscape.com for now.
QA Contact: teruko → andreasb
Comment 22•25 years ago
|
||
I don't know how Korean is supposed to look, but is this a dup of bug 76897?
Comment 23•25 years ago
|
||
I don't think this is dupl of the bug you mentioned. This bug can be
'fixed' very easily and I really hope this is fixed as suggested a long
time ago. Simply put, 16pixel font is *a way too big for Korean (it
may not be big for Japanese and Chinese). 99% of Korean Linux/FreeBSD
users have at least a few different Korean X11 fonts in various sizes
- 10,12,14,16,18,20 pixels - and truetype and CID fonts which XFree86
4.x can present to X clients at any size. Consequently, I don't think
the fact that X11 distribution comes only with 16pixel and 24pixel
fonts for Korean is a good reason for fixing the default font size for
Korean to 16pixel. Of course, non-Korean users who want to view Korean
pages on non-regular basis with ONLY 16/24 pixel font may like it as
it is now. However, that can be noted in 'Release notes' (not the other
way around)
Comment 24•25 years ago
|
||
Brian, it would probably be OK to change the minimum font size for Korean from
16 to 12 or even 10. This would solve a real problem for Korean users. We would
need to find out what fonts they are using, and obtain some of those for our QA
people here to use (since X Windows comes with 16 and 24 pixel Korean fonts by
default).
Updated•25 years ago
|
QA Contact: andreasb → teruko
Comment 25•25 years ago
|
||
Adding nsbeta1 keyword, and requesting a target milestone of M0.9.1 per iQA triage
Keywords: nsbeta1
Comment 26•25 years ago
|
||
Brian - Erik thought this was an easy one to fix. Do you have time to fix it?
Status pls . . .
| Assignee | ||
Comment 27•25 years ago
|
||
Comment 28•25 years ago
|
||
r=ftang rs
| Assignee | ||
Comment 29•25 years ago
|
||
fix checked in
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 30•25 years ago
|
||
Thanks for fixing this.
QA people at Netscape may wish
to install the baekmuk fonts (either bitmap or ttf). They're
available at ftp://ftp.mizi.com/pub/baekmuk.
baekmuk-2.0.tar.gz contains three different bitmap fonts
(gulim, batang, dotum) at 10,12,14,16,18,20,24 pixels
(in ksc5601_1987-0) and
each of them comes in both normal and bold.
If X-TT is installed for XF86 3.x or XF86 4.0x is installed
(RedHat 7.x), it's better to use baekmuk.spec (RPM spec file)
to install truetype version along with bitmap fonts at 10 and
12 pixels.
You need to log in
before you can comment on or make changes to this bug.
Description
•