home *** CD-ROM | disk | FTP | other *** search
/ Chip 2007 January, February, March & April / Chip-Cover-CD-2007-02.iso / boot / i386 / root / etc / fonts / suse-hinting.conf < prev    next >
Extensible Markup Language  |  2006-11-29  |  10KB  |  279 lines
  1. <?xml version="1.0"?>
  2. <!DOCTYPE fontconfig SYSTEM "fonts.dtd">
  3. <fontconfig>
  4.  
  5. <!-- Generated by SuSEconfig.fonts, don't edit, your changes will get lost. -->
  6. <!-- Edit /etc/sysconfig/fonts-config instead.                              -->
  7. <!-- Or put rules into your personal config file ~/.fonts.conf.             -->
  8.  
  9. <!-- ************************************************************ -->
  10. <!-- Hinting and antialiasing                                     -->
  11. <!-- ************************************************************ -->
  12.  
  13.  
  14. <!--
  15.     Using hinting=true, hintstyle=hintfull and antialias=true
  16.     is a good default for most fonts.
  17.  
  18.     Match on "pattern" for the default, not on "font" to make
  19.     it easier to override the default using FcPatternDel()
  20.     and FcPatternAdd...() (see bugzilla #104365).
  21. -->
  22.  
  23.         <match target="pattern">
  24.                 <edit name="hinting">
  25.                         <bool>true</bool>
  26.                 </edit>
  27.                 <edit name="hintstyle">
  28.                         <const>hintfull</const>
  29.                 </edit>
  30.                 <edit name="antialias">
  31.                         <bool>true</bool>
  32.                 </edit>
  33.         </match>
  34.  
  35. <!--
  36.     Set autohinter=true as the default, then add exceptions for certain fonts:
  37. -->
  38.     
  39.         <match target="pattern">
  40.                 <edit name="autohint">
  41.                         <bool>true</bool>
  42.                 </edit>
  43.         </match>
  44.  
  45. <!--
  46.     TrueType Fonts which have high quality byte code interpreter
  47.     instructions can look very good in even in small sizes when using
  48.     the byte code interpreter (autohint=false). This is true
  49.     both with and without anti-aliasing. 
  50.     In black and white (antialias=false) the results when rendering
  51.     with the byte code interpreter may even look as good as high quality
  52.     bitmap fonts.
  53.  
  54.     On the other hand, some low quality TrueType Fonts do not have
  55.     byte code interpreter instructions at all or only very bad byte
  56.     code and may look better when the autohinter is used.
  57.     (See "FreeSans" for example, it looks better with the
  58.     autohinter which is especially obvious if anti-aliasing is off).
  59. -->
  60.  
  61.     <!--
  62.         Switch off the autohinter for TrueType fonts in order
  63.             to use the byte code interpreter.
  64.     -->
  65.         
  66.     <match target="font">
  67.         <test name="fontformat">
  68.             <string>TrueType</string>
  69.         </test>
  70.                 <edit name="autohint">
  71.                         <bool>false</bool>
  72.                 </edit>
  73.     </match>
  74.  
  75.     <!--
  76.         Switch on the autohinter for a few TrueType fonts which
  77.             have no byte code or very bad byte code and look better
  78.             with the autohinter:
  79.  
  80.             But see also bug #215602 for many fonts the autohinter
  81.             seriously distorts the metrics so badly that
  82.             even the digits which should be monospaced are not
  83.             monospaced at all anymore.
  84.  
  85.             Because of this problem, better don't switch on
  86.             the autohinter for
  87.  
  88.                Sazanami
  89.                IPA
  90.                DejaVu Sans Light
  91.                DejaVu Sans Condensed
  92.                DejaVu Serif Condensed
  93.                FreeSans
  94.                FreeSerif
  95.                FreeMono
  96.  
  97.             and other fonts with similar problems until this is solved
  98.             in the autohinter.
  99.     -->
  100.  
  101.     <match target="font">
  102.         <test name="fontformat">
  103.             <string>TrueType</string>
  104.         </test>
  105.         <test name="family">
  106.             <string>MS Gothic</string>
  107.             <string>MS PGothic</string>
  108.             <string>MS UI Gothic</string>
  109.             <string>MS Mincho</string>
  110.             <string>MS PMincho</string>
  111.             <string>HGPSoeiKakupoptai</string>
  112.             <string>HGSGothicE</string>
  113.             <string>HGSGothicM</string>
  114.             <string>HGKyokashotai</string>
  115.             <string>HGSSoeiKakugothicUB</string>
  116.             <string>HGPGothicB</string>
  117.             <string>HGPGothicE</string>
  118.             <string>HGPGothicM</string>
  119.             <string>HGSKyokashotai</string>
  120.             <string>HGMaruGothicMPRO</string>
  121.             <string>HGPSoeiKakugothicUB</string>
  122.             <string>HGMinchoL</string>
  123.             <string>HGPMinchoL</string>
  124.             <string>HGMinchoB</string>
  125.             <string>HGPMinchoB</string>
  126.             <string>HGSMinchoB</string>
  127.             <string>HGMinchoE</string>
  128.             <string>HGPMinchoE</string>
  129.             <string>HGSMinchoE</string>
  130.             <string>HGSoeiKakugothicUB</string>
  131.             <string>HGGyoshotai</string>
  132.             <string>HGPGyoshotai</string>
  133.             <string>HGSGyoshotai</string>
  134.             <string>HGSoeiKakupoptai</string>
  135.             <string>HGSSoeiPresenceEB</string>
  136.             <string>HGPSoeiPresenceEB</string>
  137.             <string>HGGothicB</string>
  138.             <string>HGGothicE</string>
  139.             <string>HGGothicM</string>
  140.             <string>HGSoeiPresenceEB</string>
  141.             <string>HGPKyokashotai</string>
  142.             <string>HGSSoeiKakupoptai</string>
  143.             <string>HGSeikaishotaiPRO</string>
  144.             <string>TLKyokashotai</string>
  145.             <string>TLMincho</string>
  146.             <string>TLPMincho</string>
  147.             <string>TLPGothic</string>
  148.             <string>TLPKyokashotai</string>
  149.             <string>TLMarugothicM</string>
  150.             <string>TLGyoshotai</string>
  151.             <string>TLPGyoshotai</string>
  152.             <string>TLSGyoshotai</string>
  153.             <string>TLPMarugothicM</string>
  154.             <string>TLSMarugothicM</string>
  155.             <string>TLSKyokashotai</string>
  156.             <string>TLGothic</string>
  157.         </test>
  158.                 <edit name="autohint">
  159.                         <bool>true</bool>
  160.                 </edit>
  161.     </match>
  162.  
  163.  
  164.         <!--
  165.             The following rule sets up black and white rendering with
  166.             the byte code interpreter for a small list of fonts which
  167.             are known to have good byte code and give bitmap quality
  168.             results at small sizes.
  169.             The pixelsize limit is set to '0' though, which effectively
  170.             disables this rule by default because most users don't like
  171.             that bitmap look and feel.
  172.             If you like a bitmap look and feel of your desktop,
  173.             copy this rule into your ~/.fonts.conf file and replace the '0'
  174.             with non-zero pixelsize limit. Using '18' as the pixelsize
  175.             limit is a good choice if you have the fonts in this list installed
  176.             and like a bitmap look and feel. 
  177.         -->
  178.         <match target="font">
  179.                 <test name="family">
  180.                         <string>Andale Mono</string>
  181.                         <string>Arial</string>
  182.                         <string>Comic Sans MS</string>
  183.                         <string>Georgia</string>
  184.                         <string>Impact</string>
  185.                         <string>Trebuchet MS</string>
  186.                         <string>Verdana</string>
  187.                         <string>Courier New</string>
  188.                         <string>Times New Roman</string>
  189.                         <string>Tahoma</string>
  190.                         <string>Webdings</string>
  191.                         <string>Albany AMT</string>
  192.                         <string>Thorndale AMT</string>
  193.                         <string>Cumberland AMT</string>
  194.                         <string>Andale Sans</string>
  195.                         <string>Andy MT</string>
  196.                         <string>Bell MT</string>
  197.                         <string>Monotype Sorts</string>
  198.                 </test>
  199.         <test name="pixelsize" compare="less_eq">
  200.                 <double>0</double>
  201.         </test>
  202.                 <edit name="autohint">
  203.                         <bool>false</bool>
  204.                 </edit>
  205.                 <edit name="antialias">
  206.                         <bool>false</bool>
  207.                 </edit>
  208.         </match>
  209.  
  210.  
  211. <!--
  212.   Some CJK fonts require the byte code interpreter to be rendered correctly.
  213.  
  214.   These are composite fonts which store components and composing information
  215.   and compose the glyphs on the fly using the hinting instructions.
  216.  
  217.   For all such fonts we switch off the autohinter here.
  218.   When "autohint" is set to "false", the byte code interpreter will
  219.   be used if it has been enabled at all when compiling freetype2.
  220.  
  221.   The Chinese fonts "MingLiu" and "PMingLiU" used to belong to the fonts
  222.   which absolutely require the byte code interpreter to be rendered
  223.   correctly. 
  224.   But apparently the new versions of "MingLiU" and "PMingLiU" from Windows
  225.   Vista are rendered correctly without the byte code interpreter.
  226.  
  227. -->
  228.  
  229.         <match target="font">
  230.                 <test name="family">
  231.                         <string>MingLiU</string>
  232.                         <string>PMingLiU</string>
  233.                 </test>
  234.                 <edit name="autohint">
  235.                         <bool>false</bool>
  236.                 </edit>
  237.         </match>
  238.  
  239. <!-- 
  240. Hinting for CJK fonts in freetype doesn't yet work as well as for Latin fonts.
  241.  
  242. Recently the autohinter in in freetype has been improved for CJK fonts
  243. a lot but it is still not perfect. Therefore one might want to switch
  244. off the autohinter for CJK fonts. 
  245.  
  246. This can be achieved by using the following rule:
  247.  
  248.         <match target="font">
  249.                 <test name="lang" compare="contains">
  250.                         <string>ja</string>
  251.                         <string>zh</string>
  252.                         <string>ko</string>
  253.                 </test>
  254.                 <edit name="autohint">
  255.                         <bool>false</bool>
  256.                 </edit>
  257.         </match>
  258. -->
  259.  
  260. <!--
  261. for some Bengali fonts (e.g. "Mukti Narrow"), the autohinter works well
  262. with the patch from http://www.kde.gr.jp/~akito/patch/freetype2/2.1.7
  263. applied. But for "Likhan" it still doesn't work that well
  264. (look how the "matra" lines at the top line up). Therefore, switch
  265. off the autohinter for the "Likhan" font:
  266. -->
  267.  
  268.         <match target="font">
  269.                 <test name="family">
  270.                         <string>Likhan</string>
  271.                 </test>
  272.                 <edit name="autohint">
  273.                         <bool>false</bool>
  274.                 </edit>
  275.         </match>
  276.  
  277.  
  278. </fontconfig>
  279.