old-www/HOWTO/Font-HOWTO/fix.html

608 lines
13 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML
><HEAD
><TITLE
>The Easy Steps to Enlighten Your Desktop</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="Optimal Use of Fonts on Linux"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Why Fonts on Linux Aren't Straight Forward ?"
HREF="notgood.html"><LINK
REL="NEXT"
TITLE="Font Packages"
HREF="fonts.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>Optimal Use of Fonts on Linux</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="notgood.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="fonts.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="fix"
></A
>3. The Easy Steps to Enlighten Your Desktop</H1
><P
>You'll have to:</P
><P
></P
><OL
TYPE="1"
><LI
><P
>&#13; <A
HREF="fix.html#freetype"
>Update the FreeType library package on your system with one compiled with BCI support</A
>.</P
></LI
><LI
><P
>Install the <A
HREF="fonts.html#msfonts"
>Webcore Fonts package (a.k.a. Microsoft fonts)</A
>.</P
></LI
><LI
><P
>Follow the instructions below on <A
HREF="fix.html#desktop"
>how to configure your desktop and common applications</A
>.</P
></LI
></OL
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="freetype"
></A
>3.1. Get a Better FreeType <SPAN
CLASS="acronym"
>RPM</SPAN
></H2
><P
>FreeType compiled with BCI presented much better screen font rendering results.</P
><P
>Get <SPAN
CLASS="acronym"
>RPM</SPAN
>s for your distribution here:</P
><P
></P
><UL
><LI
><P
><A
HREF="http://avi.alkalay.net/software/freetype.bci/FC6/"
TARGET="_top"
>Fedora 6 <SPAN
CLASS="acronym"
>RPM</SPAN
>s</A
>.</P
></LI
><LI
><P
><A
HREF="http://avi.alkalay.net/software/freetype.bci/FC5/"
TARGET="_top"
>Fedora 5 <SPAN
CLASS="acronym"
>RPM</SPAN
>s</A
> by Cody DeHaan.</P
></LI
><LI
><P
><A
HREF="http://avi.alkalay.net/software/freetype.bci/FC3-FC4-RHEL3-RHEL4/"
TARGET="_top"
>CentoOS or Red Hat Enterprise Linux 3 and 4, and Fedora 3 and 4 <SPAN
CLASS="acronym"
>RPM</SPAN
>s</A
>.</P
></LI
><LI
><P
><A
HREF="http://plf.zarb.org/"
TARGET="_top"
>Mandrake <SPAN
CLASS="acronym"
>RPM</SPAN
>s</A
> through the Penguin Liberation Front website. The package name is <EM
>libfreetype6</EM
>.</P
></LI
><LI
><P
>Debian Sarge users have the BCI enabled FreeType from the "testing" and "unstable" package repositories. Next stable Debian version will include it as their default. The Debian package name is <EM
>libfreetype6</EM
>.</P
></LI
></UL
><P
>If you use one of these distributions, but on a platform that binary RPMs are not being provided, you can easily compile your own (even if you don't have any software compilation skills) following the instructions on <A
HREF="bcisrcrpm.html"
>Appendix B</A
>.</P
><P
>WE WILL ACCEPT CONTRIBUTIONS of distribution specific FreeType repackaging, so if you can <A
HREF="mailto:avi at unix DOT sh"
TARGET="_top"
>contact us</A
>, we appreciate.</P
><P
>If you are interested in repackaging your own FreeType, see how we repackage the Fedora Core and Red Hat <SPAN
CLASS="acronym"
>RPM</SPAN
>s with BCI on the <A
HREF="bci.html"
>Appendix A</A
> as a reference.</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="desktop"
></A
>3.2. Configure Your Desktop</H2
><H4
CLASS="BRIDGEHEAD"
><A
NAME="AEN255"
></A
>General Guidelines</H4
><P
>The main idea is to use good hinted fonts all around. As a general rule, we'll use <EM
>Tahoma 8pt</EM
> for desktop widgets, <EM
>LucidaTypewriter 8pt</EM
> for monospace text, and <EM
>Verdana 8pt, 9pt or 10pt</EM
> for fluent text reading or web surfing. These are the default font sizes on a Microsoft Windows desktop, and they look good on a 1024x768 screen. If you have a better screen resolution (1280x1024, 1600x1200) our suggestion is to stick with these fonts but increase their sizes.</P
><P
>We choose these fonts, specially <A
HREF="fonts.html#msfonts"
>Microsoft's <EM
>Tahoma</EM
> and <EM
>Verdana</EM
></A
>, because they look perfect at small sizes (8pt, due to their excellent hinting), providing a more efficient screen utilization. They'll make your desktop look beautiful, professional, clean and comfortable. These fonts were designed for this purpose.</P
><P
>For window titles or text that will appear in bigger sizes, you may choose whatever you want because bigger sizes hinting are not so relevant.</P
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="antialiasing"
></A
>3.2.1. A Note About Anti-Aliasing</H3
><P
>Anti-Aliasing is a technique used to reduce the "steeper" effect on low-resolution medias, so it can be used to improve the quality of text on the screen. It is also used to blur the imperfections of bad hinted fonts at small sizes. For desktop widgets (usually with small size), some people think it makes the desktop look dirty.</P
><P
>So a practical conclusion we found is to use Anti-Aliasing for sizes bigger than 10pt, and use good hinted fonts for smaller sizes without Anti-Aliasing. Currently the best hinted fonts you can find, as we cited before, are the ones found in the <A
HREF="fonts.html#msfonts"
>Webcore font package</A
>.</P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="kde"
></A
>3.2.2. KDE</H3
><P
>To configure KDE, use the Control Center (<B
CLASS="command"
>kcontrol</B
> in the command line). This is how I have it configured.</P
><DIV
CLASS="figure"
><A
NAME="AEN274"
></A
><P
><B
>Figure 1. General KDE font configuration</B
></P
><P
><IMG
SRC="kde.png"></P
></DIV
><P
>So we basically chose <EM
>Trebuchet 12pt</EM
> as the window title font, the bitmap font <EM
>LucidaTypewriter 8pt</EM
> for fixed size text, and <EM
>Tahoma 8pt</EM
> for everything else, which includes menus, buttons, etc. The 2 first should follow your taste, but <EM
>Tahoma 8pt</EM
> for all the rest is the optimal configuration, also used by MS Windows 2000 and XP.</P
><P
>One other thing to note is that I disabled anti-aliasing for font sizes up to 9 points. Look at the entire dialog and see how all text is clearly rendered, looks clean precise and professional.</P
><P
>Konqueror (KDE's browser and file manager) also needs font configuration for beautiful web browsing and file management. </P
><DIV
CLASS="figure"
><A
NAME="AEN284"
></A
><P
><B
>Figure 2. Konqueror File Management font configuration</B
></P
><P
><IMG
SRC="konqf.png"></P
></DIV
><P
>We used the same <EM
>Tahoma 8pt</EM
> for rendering the list of files in Konqueror's window, because <EM
>Tahoma</EM
> was simply designed with this purpose in mind, with <EM
>8pt</EM
> being its most important size, with no need of anti-aliasing to be clear and beautiful.</P
><DIV
CLASS="figure"
><A
NAME="AEN291"
></A
><P
><B
>Figure 3. Konqueror Web Browsing font configuration</B
></P
><P
><IMG
SRC="konqw.png"></P
></DIV
><P
>And this is finally for web browsing. We are using <EM
>Verdana</EM
> as the general font because it was simply designed for the purpose of fluent text reading on the screen. And the old <EM
>LucidaTypewriter</EM
> when a web page requested a fixed size font. Some may choose fonts like <EM
>Courier</EM
> or <EM
>Bistream Vera Mono</EM
> here.</P
><P
>We left all other fonts blank, to let the page choose it. But you may use <EM
>Times New Roman</EM
> as the Serif Font. Read more about serif fonts in <A
HREF="typography.html#serif"
>Section 7.2.2</A
>.</P
><P
>The sizes of the fonts for browsing are a bit personal and depends on how healthy are your eyes, and the resolution of your screen. In my 1024x768 screen I use default size as 8pt, and I don't want web pages to use sizes smaller than 7pt. In the end of the day, to set the size is not so effective because modern web pages use to set them with absolute values. So it is more practical to use the browsers <SPAN
CLASS="guimenu"
>View</SPAN
> menu to "zoom" the page you are currently seeing.</P
><P
>One more thing to note is the <SPAN
CLASS="guilabel"
>Default Encoding</SPAN
>. This is a quite complex subject that deserves an entire HOWTO, but it is generally OK to leave it as the Language Encoding. You may need to change it if you frequently browse pages with non pure ASCII (international text) made by irresponsible webmasters that still don't use UTF-8 for the web. But here also it may be more practical to use the <SPAN
CLASS="guimenu"
>View</SPAN
> menu to set the encoding for the current page you are browsing.</P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="gnome"
></A
>3.2.3. Gnome</H3
><P
>We'll use our generic rules here too: <EM
>Tahoma 8pt</EM
> for everything. Navigate preferences menu to invoke the following dialog or just run <B
CLASS="command"
>gnome-font-properties</B
> from the command line.</P
><DIV
CLASS="figure"
><A
NAME="AEN312"
></A
><P
><B
>Figure 4. Gnome Font Configurations</B
></P
><P
><IMG
SRC="gnome.png"></P
></DIV
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="ooo"
></A
>3.2.4. OpenOffice.org</H3
><P
>As of Fedora Core 3 time, OpenOffice.org 1.1.2 has look (but not feel) integration with KDE and Gnome. This means that your environment should tell OOo how to use widget fonts. But we found it didn't really work. With further investigation we found that only the non-AA configuration we made was not propagated to OOo. So we used OOo's own dialogs to change it.</P
><DIV
CLASS="figure"
><A
NAME="AEN318"
></A
><P
><B
>Figure 5. OpenOffice.org font configuration, using my KDE themes etc.</B
></P
><P
><IMG
SRC="ooo.png"></P
></DIV
><P
>So we basically selected <SPAN
CLASS="guimenu"
>Tool</SPAN
>, <SPAN
CLASS="guimenuitem"
>Options</SPAN
> menu, and in the <SPAN
CLASS="guilabel"
>View</SPAN
> section we enable OOo to do anti-aliasing at font sizes beginning with 12 pixels (approximately 9pt), and the result is what you can see above: clean and comfortable widgets with <EM
>Tahoma 8pt</EM
>.</P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="firefox"
></A
>3.2.5. Mozilla Firefox</H3
><P
>Mozilla Firefox follows the same Konqueror rules.</P
><DIV
CLASS="figure"
><A
NAME="AEN329"
></A
><P
><B
>Figure 6. Firefox fonts for web browsing</B
></P
><P
><IMG
SRC="firefox.png"></P
></DIV
><P
>So we <SPAN
CLASS="guimenu"
>Edit</SPAN
>-&#62;<SPAN
CLASS="guimenuitem"
>Preferences</SPAN
> and then <EM
>&#13; <SPAN
CLASS="guibutton"
>Fonts &#38; Colors</SPAN
>
</EM
>, and selected <EM
>Verdana 14px</EM
> for general browsing and <EM
>LucidaTypewriter 11px</EM
> for monospace text.</P
><P
>Firefox is a Gnome application, so it will use Gnome's font settings for widgets.</P
><P
>Additionaly, a very interesting way to configure some font rendering aspects of Firefox is described in a <A
HREF="http://mandrake.vmlinuz.ca/bin/view/Main/FireFoxFonts"
TARGET="_top"
>Mandrake Wiki</A
>.</P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="nomsfonts"
></A
>3.2.6. Beautiful Alternatives Without <A
HREF="fonts.html#msfonts"
>Webcore Fonts</A
></H3
><P
>If you want to stay away from patents and proprietary fonts, the best way to go is with <EM
>Bitstream Vera Sans 8pt</EM
>, <EM
>Nimbus Sans 8 or 9pt</EM
>, or <EM
>Luxi Sans 8 or 9pt (also known as Sans, simply)</EM
> for desktop widgets, and bigger sizes for fluent text reading. You'll need Anti-Aliasing to blur the low quality of the hinting of these fonts.</P
><P
>Here are some screen shots about the usage of these fonts on KDE. You should pay attention on how the widgets text on this window are rendered.</P
><DIV
CLASS="figure"
><A
NAME="AEN350"
></A
><P
><B
>Figure 7. Bitstream Vera 8pt with Anti-Aliasing</B
></P
><P
><IMG
SRC="vera8aa.png"></P
></DIV
><DIV
CLASS="figure"
><A
NAME="AEN353"
></A
><P
><B
>Figure 8. Luxi 8pt with Anti-Aliasing</B
></P
><P
><IMG
SRC="luxi8aa.png"></P
></DIV
><DIV
CLASS="figure"
><A
NAME="AEN356"
></A
><P
><B
>Figure 9. Luxi 9pt with Anti-Aliasing</B
></P
><P
><IMG
SRC="luxi9aa.png"></P
></DIV
><DIV
CLASS="figure"
><A
NAME="AEN359"
></A
><P
><B
>Figure 10. Nimbus 9pt with Anti-Aliasing</B
></P
><P
><IMG
SRC="nimbus9aa.png"></P
></DIV
><P
>As you can see, the results aren't so good as <EM
>Tahoma 8pt</EM
>.</P
></DIV
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="notgood.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="fonts.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Why Fonts on Linux Aren't Straight Forward ?</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Font Packages</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>