chilidog.highland.cc.ks.us/chilidog.highland.cc.ks.us.zip/chilidog.highland.cc.ks.us/backup/bradford.20120305.etc.tar.gz/bradford.20120305.etc.tar/etc/fonts/suse-hinting.conf

Extensible Markup Language | 2006-06-09 | 7KB | 168 lines

<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>

<!-- Generated by SuSEconfig.fonts, don't edit, your changes will get lost. -->
<!-- Edit /etc/sysconfig/fonts-config instead.                              -->
<!-- Or put rules into your personal config file ~/.fonts.conf.             -->

<!-- ************************************************************ -->
<!-- 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 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">
                        <bool>true</bool>
                </edit>
                <edit name="hintstyle">
                        <const>hintfull</const>
                </edit>
                <edit name="antialias">
                        <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
            are known to have good byte code and give bitmap quality
            results at small sizes.
            The pixelsize limit is set to '0' though, which effectively
            disables this rule by default because most users don't like
            that bitmap look and feel.
            If you like a bitmap look and feel of your desktop,
            copy this rule into your ~/.fonts.conf file and replace the '0'
            with non-zero pixelsize limit. Using '18' as the pixelsize
            limit is a good choice if you have the fonts in this list installed
            and like a bitmap look and feel.
        -->
        <match target="font">
                <test name="family">
                        <string>Andale Mono</string>
                        <string>Arial</string>
                        <string>Comic Sans MS</string>
                        <string>Georgia</string>
                        <string>Impact</string>
                        <string>Trebuchet MS</string>
                        <string>Verdana</string>
                        <string>Courier New</string>
                        <string>Times New Roman</string>
                        <string>Tahoma</string>
                        <string>Webdings</string>
                        <string>Albany AMT</string>
                        <string>Thorndale AMT</string>
                        <string>Cumberland AMT</string>
                        <string>Andale Sans</string>
                        <string>Andy MT</string>
                        <string>Bell MT</string>
                        <string>Monotype Sorts</string>
                </test>
        <test name="pixelsize" compare="less_eq">
                <double>0</double>
        </test>
                <edit name="autohint">
                        <bool>false</bool>
                </edit>
                <edit name="antialias">
                        <bool>false</bool>
                </edit>
        </match>


<!--
  Some CJK fonts require the byte code interpreter to be rendered correctly.

  These are composite fonts which store components and composing information
  and compose the glyphs on the fly using the hinting instructions.

  For all such fonts we switch off the autohinter here.
  When "autohint" is set to "false", the byte code interpreter will
  be used if it has been enabled at all when compiling freetype2.

-->

        <match target="font">
                <test name="family">
                        <string>MingLiU</string>
                        <string>PMingLiU</string>
                </test>
                <edit name="autohint">
                        <bool>false</bool>
                </edit>
        </match>

<!--
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 <[e-mail]>
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.

This can be achieved by using the following rule:

        <match target="font">
                <test name="lang" compare="contains">
                        <string>ja</string>
                        <string>zh</string>
                        <string>ko</string>
                </test>
                <edit name="hintstyle" mode="assign">
                        <const>hintnone</const>
                </edit>
        </match>
-->

<!--
for some Bengali fonts (e.g. "Mukti Narrow"), the autohinter works well
with the patch from http://www.kde.gr.jp/~akito/patch/freetype2/2.1.7
applied. But for "Likhan" it still doesn't work that well
(look how the "matra" lines at the top line up). Therefore, switch
off the autohinter for the "Likhan" font:
-->

        <match target="font">
                <test name="family">
                        <string>Likhan</string>
                </test>
                <edit name="hintstyle">
                        <const>hintnone</const>
                </edit>
        </match>


</fontconfig>