From: Alan Humpherys <alangh@xm...> - 2002-12-23 05:54:12
Thank you for reporting this issue. I have added this as a feature request
(#657733) to fix in some future release as we provide improved font handling
for various character sets.
[mailto:fire-talk-admin@...]On Behalf Of Jared
Sent: Sunday, December 15, 2002 3:14 AM
Subject: Re: [Fire-talk] Hey everyone
I've discovered what is happening. It isn't actually bolding the fonts
or displaying them incorrectly, it is just choosing to display a
different version of the normal font. Normally, if the chosen font
doesn't support the Japanese characters, it defaults to "Hiragino Kaku
Gothic Pro" with a typeface of W3. For some reason, Fire is defaulting
to the correct font but with a typeface of W6. This makes it much
thicker than normal. iChat and Proteus both seem to use the W3 font.
I'm not sure how they decided that.
Now, if my chosen font is a Japanese font, then it displays normally
because it supports the characters. It's only when it has to default to
a Japanese font that it messes up.
I'm not sure how to go about fixing this, but I hope this information
helps you track down the problem.
On Thursday, December 12, 2002, at 11:05 PM, Graham Booker wrote:
> 2) We will look into this.
>> 2) Before using OSCAR, Japanese did not work over AIM. I'm happy that
>> it now does which brings it a lot closer to "iChat status" in my
>> book. However, the font looks bolded. I don't know why this is
>> happening, but it might fall under the "bug" category. Either that,
>> or as a feature it would be nice to choose a font for non-roman
>> characters to be displayed in. This is not a feature I've seen
>> anywhere else and would be very nice.
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
Fire-talk mailing list
Get latest updates about Open Source Projects, Conferences and News.