ttf-wqy-zenhei makes libqt4.4 to render all fonts unantialiased

[Lukas Hejtmanek]

Binary package hint: ttf-wqy-zenhei

If the ttf-wqy-zenhei font is enabled in the fontconfig, the Qt (libqt4 - 4.4.0-1ubuntu3, Ubuntu/intrepid) renders all the fonts non-antialiased.

I think this is a known problem but without any fix.

[Arne Goetje (arnegoetje)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Lukas Hejtmanek wrote:
> Public bug reported:
>
> Binary package hint: ttf-wqy-zenhei
>
> If the ttf-wqy-zenhei font is enabled in the fontconfig, the Qt (libqt4
> - 4.4.0-1ubuntu3, Ubuntu/intrepid) renders all the fonts non-
> antialiased.
>
> I think this is a known problem but without any fix.
>
If this is a known problem, can you please give links where this problem
is discussed?

Also, why do you think this is a bug in the font package and not in libqt4?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIKFyYbp/QbmhdHowRAg/qAJ0WwFxEC4zCJgMRCUVVQ0CzDa5qswCg2ATp
EUkkUYs0sslpOuawwMOIsYM=
=dK9t
-----END PGP SIGNATURE-----

[Qishuai Liu (lqs)]

Have you upgraded all packages to hardy?

[Lukas Hejtmanek (xhejtman)]

> If this is a known problem, can you please give links where this problem
> is discussed?

at least one point here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=448555

but the solution is to remove some fonts and antialiasing is back.

a friend told me that he saw discussion in Mandrake list some time ago but was unable to find it again and the resolution was to remove some 'buggy' fonts.

> Also, why do you think this is a bug in the font package and not in libqt4?

not sure. it could be libqt4 problem as well as buggy font.

[Pan, SZ (pan.sz)]

I can confirm it, on Kubuntu 8.04 KDE359 fresh install and upgrade
everything to the newest version, ttf-wqy-zenhei will render ALL chinese
text as non-antialiased (i.e. bitmap) even if the fonts is not
ttf-wqy-zenhei.

Remove the package does not fix it, I have to manually delete the
/etc/fonts/conf.d70-no-bitmaps.conf and restart X server to get rid of the
bitmap fonts.

Have to say we may need a pole on how many people prefer bitmaped fonts to
antialiased truetype fonts. Almost all of my colleagues remove the bitmap
inside the WQY after they installed ubuntu 8.04 and they like the
antialiased fonts much better.
--
Sincerely, Pan, Shi Zhu.

<email address hidden> 写于 2008.05.12 23:28:13:

> Have you upgraded all packages to hardy?

[Jiahua Huang (huangjiahua)]

On Tue, May 13, 2008 at 8:44 AM, Pan, Shi Zhu <email address hidden> wrote:
> Have to say we may need a pole on how many people prefer bitmaped fonts to
> antialiased truetype fonts. Almost all of my colleagues remove the bitmap
> inside the WQY after they installed ubuntu 8.04 and they like the
> antialiased fonts much better.
>

The same as you did,
we also like the antialiased truetype fonts much better.

[Arne Goetje (arnegoetje)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jiahua Huang wrote:
> On Tue, May 13, 2008 at 8:44 AM, Pan, Shi Zhu <email address hidden> wrote:
>> Have to say we may need a pole on how many people prefer bitmaped fonts to
>> antialiased truetype fonts. Almost all of my colleagues remove the bitmap
>> inside the WQY after they installed ubuntu 8.04 and they like the
>> antialiased fonts much better.
>>
>
> The same as you did,
> we also like the antialiased truetype fonts much better.
>

This bug report is *not* for polling about whether or not embedded
bitmaps should be enabled in the font. Please see
https://bugs.launchpad.net/bugs/203571 for why embedded bitmaps got enabled.

The point is: embedded bitmaps are enabled on purpose for this font.
However, this setting should *only* affect WQY ZenHei and not other
fonts on the system. If the renderer or application gets this wrong,
it's either a bug in the fontconfig configuration for this font (which I
don't believe to be the case), or the application is buggy.

Now, the question is in which applications this problem is appearing. If
it happens in *all* QT4 apps, but not in other applications (Gnome/GTK,
Mozilla, OpenOffice), it's most likely a bug in QT4.

As I know this bug does not happen in GTK, Mozilla and OpenOffice, I
suggest it's a bug in libqt4 and not in the font package.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIKPi5bp/QbmhdHowRArOqAKCkPz5DBcJgcNhBLudb3PZF4gfJswCgy69C
ex0/xOzrgg3/3NupnakVQKw=
=862V
-----END PGP SIGNATURE-----

[Pan, SZ (pan.sz)]

I am here to emphasis that, this does not only happen in QT4, but also in
QT3. Because it *does* happen in all of my QT3 applications.

i.e. fonts are affected for applications which does not use wqy-zen-hei at
all. and this is the case for both QT3 and QT4.

So I think it is rather a problem of the font or the font configuration
rather than issue of QT.

--
Sincerely, Pan, Shi Zhu.

<email address hidden> 写于 2008.05.13 10:11:05:
> The point is: embedded bitmaps are enabled on purpose for this font.
> However, this setting should *only* affect WQY ZenHei and not other
> fonts on the system. If the renderer or application gets this wrong,
> it's either a bug in the fontconfig configuration for this font (which I
> don't believe to be the case), or the application is buggy.
>
> Now, the question is in which applications this problem is appearing. If
> it happens in *all* QT4 apps, but not in other applications (Gnome/GTK,
> Mozilla, OpenOffice), it's most likely a bug in QT4.
>
> As I know this bug does not happen in GTK, Mozilla and OpenOffice, I
> suggest it's a bug in libqt4 and not in the font package.

[Qishuai Liu (lqs)]

2008/5/13 Pan, Shi Zhu <email address hidden>:

> I can confirm it, on Kubuntu 8.04 KDE359 fresh install and upgrade
> everything to the newest version, ttf-wqy-zenhei will render ALL chinese
> text as non-antialiased (i.e. bitmap) even if the fonts is not
> ttf-wqy-zenhei.
>
>
What about the latin characters? Are they also non-antialiased?

[Arne Goetje (arnegoetje)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Pan, Shi Zhu wrote:
> I can confirm it, on Kubuntu 8.04 KDE359 fresh install and upgrade
> everything to the newest version, ttf-wqy-zenhei will render ALL chinese
> text as non-antialiased (i.e. bitmap) even if the fonts is not
> ttf-wqy-zenhei.

The rendering of *Chinese* text with bitmaps is correct and not a bug.
The other Chinese font (AR PL UMing *) from the ttf-arphic-uming package
 also has embedded bitmaps enabled for the same reason as WQY ZenHei has.

If you display the text with AR PL UKai * however, this should *not* be
the case as that font does not include bitmaps and does not have bitmaps
configured in fontconfig.

Also, other scripts, like Arabic, Indic scripts, Thai, etc. should be
rendered normally.

For Latin, Greek and Cyrillic it may be that Chinese fonts get preferred
and therefor being rendered with bitmaps. But this depends on your
locale and font preferences in fontconfig.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIKQT8bp/QbmhdHowRAgAQAKDNed5dcKqBAOeO0P6M8O29MplqPgCg23JP
plgrUVxPLjbNtpbqhF2SajU=
=142Y
-----END PGP SIGNATURE-----

[Pan, SZ (pan.sz)]

I am using the SIMHEI.ttf, STXIHEI.ttf, STZHONGS.ttf as the mono, sans, and
serif fonts, all of them has absolutely no embedded bitmap, the preference
of them are only second to bitstream families. such configuration works
perfectly in 7.04 and 7.10.

My observation now is that SIMHEI and STXIHEI got wqy-zen-hei bitmap,
STZHONGS got non-antialiased without bitmap, all of them occur at 12pt and
14pt. other sizes not tested. It seems that wqy-zen-hei bitmap is mapped to
all sans-style fonts, not the wqy-zen-hei font alone. and similar, uming's
no-aa settings is applied to other serif-style fonts.

After one-hour-read of the fontconfig document and lots of changes in my
fontconfig files, I get all I want: the above three fonts all show
anti-aliased without any bitmap font at all. Since things *do* get right
after some configuration change, I think it is unlikely to be the issue of
Qt.

Of course, your mind may vary, and probably both Qt and the font
configuration has problem.

--
Sincerely, Pan, Shi Zhu.

> The rendering of *Chinese* text with bitmaps is correct and not a bug.
> The other Chinese font (AR PL UMing *) from the ttf-arphic-uming package
> also has embedded bitmaps enabled for the same reason as WQY ZenHei has.

[Arne Goetje (arnegoetje)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Pan, Shi Zhu wrote:
> I am using the SIMHEI.ttf, STXIHEI.ttf, STZHONGS.ttf as the mono, sans, and
> serif fonts, all of them has absolutely no embedded bitmap, the preference
> of them are only second to bitstream families. such configuration works
> perfectly in 7.04 and 7.10.
>
> My observation now is that SIMHEI and STXIHEI got wqy-zen-hei bitmap,
> STZHONGS got non-antialiased without bitmap, all of them occur at 12pt and
> 14pt. other sizes not tested. It seems that wqy-zen-hei bitmap is mapped to
> all sans-style fonts, not the wqy-zen-hei font alone. and similar, uming's
> no-aa settings is applied to other serif-style fonts.

No, they didn't "get" the bitmaps! The fonts got superseeded by WQY
ZenHei and AR PL UMing and that is indeed standard behavior and not a
bug! We don't ship proprietary fonts. If you want to use them, then you
are on your own!

> After one-hour-read of the fontconfig document and lots of changes in my
> fontconfig files, I get all I want: the above three fonts all show
> anti-aliased without any bitmap font at all. Since things *do* get right
> after some configuration change, I think it is unlikely to be the issue of
> Qt.

> Of course, your mind may vary, and probably both Qt and the font
> configuration has problem.

No, your "problem" is not a problem at all, but depends on how you set
fontconfig. Again, we only ship WQY ZenHei, AR PL UMing, AR PL UKai and
WQY Bitmap Song as Chinese fonts. And of course we configure the system
so that these fonts get preferred. Therefor it is expected behavior and
not a bug!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIKTsnbp/QbmhdHowRAq1iAKClydwqkfoFeEOkVey1J+65RwOOAACdGpR0
4Z0Ok68XeUxWI7dQay82xaU=
=Dzyx
-----END PGP SIGNATURE-----

[Thomas Hotz (thotz-deactivatedaccount)]

Is it so "not a bug"?