Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 13 Nov 2012 22:32:12 -0800
From:      Yuri <yuri@rawbw.com>
To:        Yuri <yuri@rawbw.com>
Cc:        chromium@freebsd.org, Jonathan Chen <jonc@chen.org.nz>
Subject:   Re: Font display on Non-English sites
Message-ID:  <50A33AEC.4010305@rawbw.com>
In-Reply-To: <50A33219.2070000@rawbw.com>
References:  <CAJuc1zMPYcrY51=hkvs1CE%2B70BU6i8THD2RnueXDtPv2BosTQg@mail.gmail.com> <50A33219.2070000@rawbw.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Special unicode characters are also not displayed properly.
Even in the google results character U+200D (&#8205; &zwj; ZERO WIDTH 
JOINER) shows as a box.
This is some serious regression. Something similar happened before, over 
a year ago, but was fixed back then.
Developer Tools/Elements also shows this problem.

Maintainers should take a look. I think you should roll the version back 
to previous until regression is fixed.

Yuri


On 11/13/2012 21:54, Yuri wrote:
> I also see this. On its face this looks like a regression from 
> 22.x.x.x version which showed Japanese in the same environment.
> chrome shows the font-family in computed style as:
> メイリオ, Meiryo, Tahoma, Verdana, 'ヒラギノ角ゴ Pro W3', 'Hiragino 
> Kaku Gothic Pro', Osaka, 'MS Pゴシック', 'MS PGothic', sans-serif;
> chrome goes through the list of fonts in the style attempting to match 
> the font, and it may be that none of them matches.
> It's hard to tell whether it really should or should not show Japanese 
> with the fonts installed on the system.
>
> As a possible workaround you may try installing fonts from 
> japanese/font-* ports. This will work if the problem is a genuine lack 
> of Japanese font, not some other random bug.
> Maybe Japanese users will have a better perspective for this problem. 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50A33AEC.4010305>