Hello community, here is the log from the commit of package fonts-config checked in at Thu Nov 16 01:07:23 CET 2006. -------- --- fonts-config/fonts-config.changes 2006-10-25 16:03:31.000000000 +0200 +++ /mounts/work_src_done/NOARCH/fonts-config/fonts-config.changes 2006-11-15 19:22:56.000000000 +0100 @@ -1,0 +2,10 @@ +Wed Nov 15 19:20:16 CET 2006 - mfabian@suse.de + +- Bugzilla #215602: don't use the embedded bitmaps in the IPA + fonts because they are only available in 12, 14, and 16 pixels. +- Bugzilla #215602: Don't use the autohinter for fonts where it + it distorts the metrics so badly that even the digits which + should be monospaced are not monospaced at all anymore. +- Don't use the autohinter for good quality TrueType fonts. + +------------------------------------------------------------------- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ fonts-config.spec ++++++ --- /var/tmp/diff_new_pack.JLHrza/_old 2006-11-16 01:06:59.000000000 +0100 +++ /var/tmp/diff_new_pack.JLHrza/_new 2006-11-16 01:06:59.000000000 +0100 @@ -11,7 +11,7 @@ # norootforbuild Name: fonts-config -License: GNU General Public License (GPL) - all versions +License: GNU General Public License (GPL) Group: System/X11/Fonts Provides: xf86tools:/usr/sbin/fonts-config Autoreqprov: on @@ -20,7 +20,7 @@ Recommends: ft2demos %endif Version: 20061025 -Release: 1 +Release: 6 Summary: Configures Fonts for X Windows and other applications Source: fonts-config Source1: SuSEconfig.fonts @@ -80,6 +80,13 @@ /var/adm/fillup-templates/sysconfig.fonts-config %changelog -n fonts-config +* Wed Nov 15 2006 - mfabian@suse.de +- Bugzilla #215602: don't use the embedded bitmaps in the IPA + fonts because they are only available in 12, 14, and 16 pixels. +- Bugzilla #215602: Don't use the autohinter for fonts where it + it distorts the metrics so badly that even the digits which + should be monospaced are not monospaced at all anymore. +- Don't use the autohinter for good quality TrueType fonts. * Wed Oct 25 2006 - mfabian@suse.de - Fate #300950: after the regular setup is done, source all scripts in /usr/lib/fonts-config/conf.d which might do additional setup. ++++++ suse-bitmaps.conf.template ++++++ --- fonts-config/suse-bitmaps.conf.template 2006-02-07 12:45:03.000000000 +0100 +++ /mounts/work_src_done/NOARCH/fonts-config/suse-bitmaps.conf.template 2006-11-15 19:24:32.000000000 +0100 @@ -81,4 +81,27 @@ _USE_EMBEDDED_BITMAPS_PLACEHOLDER_ +<!-- + The IPA fonts have bitmaps only in 12, 14, and 16 pixels. + That is rather useless, it is not nice to see a bitmaps at 12 + pixels, antialiased glyphs at 13 pixels and bitmaps at 14 + pixels again. +--> + <match target="font"> + <test name="family"> + <string>IPAMincho</string> + <string>IPAGothic</string> + <string>IPAPMincho</string> + <string>IPAPGothic</string> + <string>IPAUIGothic</string> + </test> + <edit name="autohint"> + <bool>false</bool> + </edit> + <edit name="embeddedbitmap"> + <bool>false</bool> + </edit> + </match> + + </fontconfig> ++++++ suse-hinting.conf.template ++++++ --- fonts-config/suse-hinting.conf.template 2006-04-28 19:16:51.000000000 +0200 +++ /mounts/work_src_done/NOARCH/fonts-config/suse-hinting.conf.template 2006-11-15 19:24:15.000000000 +0100 @@ -10,40 +10,18 @@ <!-- Hinting and antialiasing --> <!-- ************************************************************ --> + <!-- - Fonts which have high quality byte code interpreter instructions - can look very good in small sizes when rendered in black and white - (antialias=false) using the byte code interpreter (autohint=false). - The results look as good as high quality bitmap fonts. - - On the other hand, most Fonts do not have good byte code interpreter - instructions and look *very* ugly when rendered like this. - I.e. for most fonts autohint=true and antialias=true gives best - results. - - For fonts which do have good byte code instructions, it seems - to be a matter of taste. Most users apparently do not like the - bitmaps no matter how good they are and prefer to render - these fonts with anti-aliasing as well. - - When rendering fonts which do have good byte code with anti-aliasing - (antialias=true), the byte code apparently doesn't help much, to - the contrary, it produces strange rendering artifacts. - Therefore it is usually better to always use the autohinter (autohint=true) - when rendering with anti-aliasing. + Using hinting=true, hintstyle=hintfull and antialias=true + is a good default for most fonts. + Match on "pattern" for the default, not on "font" to make + it easier to override the default using FcPatternDel() + and FcPatternAdd...() (see bugzilla #104365). --> - <!-- - Using the autohinter, hintstyle=hintfull and anti-aliasing. - This is a good default for most fonts. - - Match on "pattern" for the default, not on "font" to make - it easier to override the default using FcPatternDel() - and FcPatternAdd...() (see bugzilla #104365). - --> <match target="pattern"> - <edit name="autohint"> + <edit name="hinting"> <bool>true</bool> </edit> <edit name="hintstyle"> @@ -54,6 +32,135 @@ </edit> </match> +<!-- + Set autohinter=true as the default, then add exceptions for certain fonts: +--> + + <match target="pattern"> + <edit name="autohint"> + <bool>true</bool> + </edit> + </match> + +<!-- + TrueType Fonts which have high quality byte code interpreter + instructions can look very good in even in small sizes when using + the byte code interpreter (autohint=false). This is true + both with and without anti-aliasing. + In black and white (antialias=false) the results when rendering + with the byte code interpreter may even look as good as high quality + bitmap fonts. + + On the other hand, some low quality TrueType Fonts do not have + byte code interpreter instructions at all or only very bad byte + code and may look better when the autohinter is used. + (See "FreeSans" for example, it looks better with the + autohinter which is especially obvious if anti-aliasing is off). +--> + + <!-- + Switch off the autohinter for TrueType fonts in order + to use the byte code interpreter. + --> + + <match target="font"> + <test name="fontformat"> + <string>TrueType</string> + </test> + <edit name="autohint"> + <bool>false</bool> + </edit> + </match> + + <!-- + Switch on the autohinter for a few TrueType fonts which + have no byte code or very bad byte code and look better + with the autohinter: + + But see also bug #215602 for many fonts the autohinter + seriously distorts the metrics so badly that + even the digits which should be monospaced are not + monospaced at all anymore. + + Because of this problem, better don't switch on + the autohinter for + + Sazanami + IPA + DejaVu Sans Light + DejaVu Sans Condensed + DejaVu Serif Condensed + FreeSans + FreeSerif + FreeMono + + and other fonts with similar problems until this is solved + in the autohinter. + --> + + <match target="font"> + <test name="fontformat"> + <string>TrueType</string> + </test> + <test name="family"> + <string>MS Gothic</string> + <string>MS PGothic</string> + <string>MS UI Gothic</string> + <string>MS Mincho</string> + <string>MS PMincho</string> + <string>HGPSoeiKakupoptai</string> + <string>HGSGothicE</string> + <string>HGSGothicM</string> + <string>HGKyokashotai</string> + <string>HGSSoeiKakugothicUB</string> + <string>HGPGothicB</string> + <string>HGPGothicE</string> + <string>HGPGothicM</string> + <string>HGSKyokashotai</string> + <string>HGMaruGothicMPRO</string> + <string>HGPSoeiKakugothicUB</string> + <string>HGMinchoL</string> + <string>HGPMinchoL</string> + <string>HGMinchoB</string> + <string>HGPMinchoB</string> + <string>HGSMinchoB</string> + <string>HGMinchoE</string> + <string>HGPMinchoE</string> + <string>HGSMinchoE</string> + <string>HGSoeiKakugothicUB</string> + <string>HGGyoshotai</string> + <string>HGPGyoshotai</string> + <string>HGSGyoshotai</string> + <string>HGSoeiKakupoptai</string> + <string>HGSSoeiPresenceEB</string> + <string>HGPSoeiPresenceEB</string> + <string>HGGothicB</string> + <string>HGGothicE</string> + <string>HGGothicM</string> + <string>HGSoeiPresenceEB</string> + <string>HGPKyokashotai</string> + <string>HGSSoeiKakupoptai</string> + <string>HGSeikaishotaiPRO</string> + <string>TLKyokashotai</string> + <string>TLMincho</string> + <string>TLPMincho</string> + <string>TLPGothic</string> + <string>TLPKyokashotai</string> + <string>TLMarugothicM</string> + <string>TLGyoshotai</string> + <string>TLPGyoshotai</string> + <string>TLSGyoshotai</string> + <string>TLPMarugothicM</string> + <string>TLSMarugothicM</string> + <string>TLSKyokashotai</string> + <string>TLGothic</string> + </test> + <edit name="autohint"> + <bool>true</bool> + </edit> + </match> + + <!-- The following rule sets up black and white rendering with the byte code interpreter for a small list of fonts which @@ -111,6 +218,12 @@ When "autohint" is set to "false", the byte code interpreter will be used if it has been enabled at all when compiling freetype2. + The Chinese fonts "MingLiu" and "PMingLiU" used to belong to the fonts + which absolutely require the byte code interpreter to be rendered + correctly. + But apparently the new versions of "MingLiU" and "PMingLiU" from Windows + Vista are rendered correctly without the byte code interpreter. + --> <match target="font"> @@ -126,11 +239,9 @@ <!-- Hinting for CJK fonts in freetype doesn't yet work as well as for Latin fonts. -But our freetype package has the patches by Takashi IWAI <tiwai@suse.de> -applied which improve the hinting results for CJK fonts a lot. - -If you are using a freetype package without these patches you may prefer -to switch off hinting by setting hintstyle=hintnone for CJK fonts. +Recently the autohinter in in freetype has been improved for CJK fonts +a lot but it is still not perfect. Therefore one might want to switch +off the autohinter for CJK fonts. This can be achieved by using the following rule: @@ -140,8 +251,8 @@ <string>zh</string> <string>ko</string> </test> - <edit name="hintstyle" mode="assign"> - <const>hintnone</const> + <edit name="autohint"> + <bool>false</bool> </edit> </match> --> @@ -158,8 +269,8 @@ <test name="family"> <string>Likhan</string> </test> - <edit name="hintstyle"> - <const>hintnone</const> + <edit name="autohint"> + <bool>false</bool> </edit> </match> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Remember to have fun... --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-commit+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-commit+help@opensuse.org