<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/fonts/article.sgml,v 1.5 1999/10/04 21:31:02 jesusr Exp $ -->

<!-- $FreeBSD: doc/en_US.ISO_8859-1/articles/fonts/article.sgml,v 1.5 1999/10/04 21:31:02 jesusr Exp $ -->

<!-- The FreeBSD Documentation Project -->

<!-- The FreeBSD Documentation Project -->

<!-- Recently, I wanted to figure out how to use some additional fonts that

<!-- Recently, I wanted to figure out how to use some additional fonts that

     I had accumulated.  I finally figured out *how to do it* from the various

     I had accumulated.  I finally figured out *how to do it* from the various

<para>There are many different font formats and associated font file

<para>There are many different font formats and associated font file

suffixes. A few that will be addressed here are:

suffixes. A few that will be addressed here are:

<variablelist>

<variablelist>

<varlistentry><term><filename>.pfa</>, <filename>.pfb</></term>

<varlistentry><term><filename>.pfa</>, <filename>.pfb</></term>

<listitem><para>Bitmapped screen fonts</para></listitem>

<listitem><para>Bitmapped screen fonts</para></listitem>

</varlistentry>

</varlistentry>

<para>The <filename>.fot</filename> file is used by Windows as sort

<para>The <filename>.fot</filename> file is used by Windows as sort

of a symbolic link to the actual TrueType font

of a symbolic link to the actual TrueType font

and/or drivers may make use of the font files.  Here is a small cross

and/or drivers may make use of the font files.  Here is a small cross

reference of application/driver to the font type suffixes:</para>

reference of application/driver to the font type suffixes:</para>

<variablelist>

<variablelist>

<varlistentry><term>Driver</term>

<varlistentry><term>Driver</term>

<listitem>

<listitem>

<variablelist>

<variablelist>

<varlistentry><term>syscons</term>

<varlistentry><term>syscons</term>

<listitem>

<listitem>

</listitem>

</listitem>

</varlistentry>

</varlistentry>

</variablelist>

</variablelist>

</listitem>

</listitem>

</varlistentry>

</varlistentry>

<varlistentry><term>Application</term>

<varlistentry><term>Application</term>

<listitem>

<listitem>

<variablelist>

<variablelist>

<varlistentry><term>Ghostscript</term>

<varlistentry><term>Ghostscript</term>

<listitem>

<listitem>

</listitem>

</listitem>

</varlistentry>

</varlistentry>

</variablelist>

</variablelist>

</listitem>

</listitem>

</varlistentry>

</varlistentry>

</variablelist>

</variablelist>

<para>The <filename>.fnt</filename> suffix is used quite frequently. 

<para>The <filename>.fnt</filename> suffix is used quite frequently. 

I suspect that whenever someone wanted to create a specialized font

I suspect that whenever someone wanted to create a specialized font

<para>First, a 8x8 font must be loaded. 

<para>First, a 8x8 font must be loaded. 

<filename>/etc/sysconfig</filename> should contain the lines:

<filename>/etc/sysconfig</filename> should contain the lines:

<informalexample>

<informalexample>

<programlisting># Choose font 8x8 from /usr/share/syscons/fonts/* (or NO for default)

<programlisting># Choose font 8x8 from /usr/share/syscons/fonts/* (or NO for default)

font8x8=/usr/share/syscons/fonts/cp437-8x8.fnt</programlisting>

font8x8=/usr/share/syscons/fonts/cp437-8x8.fnt</programlisting>

</informalexample>

</informalexample>

<para>The command to actually switch the mode is

<para>The command to actually switch the mode is

<informalexample>

<informalexample>

<screen>bash$ <userinput>vidcontrol VGA_80x60</userinput></screen>

<screen>bash$ <userinput>vidcontrol VGA_80x60</userinput></screen>

</informalexample>

</informalexample>

<para>Various screen orientated programs, such as

<para>Various screen orientated programs, such as

determine the current screen dimensions.  These can be set with

determine the current screen dimensions.  These can be set with

<informalexample>

<informalexample>

<screen>bash$ <userinput>stty crt rows 60 columns 80</userinput></screen>

<screen>bash$ <userinput>stty crt rows 60 columns 80</userinput></screen>

</informalexample>

</informalexample>

<para>To make this more seamless, one can embed these commands in the

<para>To make this more seamless, one can embed these commands in the

startup scripts so it takes place when the system boots.  One way to

startup scripts so it takes place when the system boots.  One way to

do this is:

do this is:

<orderedlist>

<orderedlist>

<listitem>

<listitem>

<listitem>

<listitem>

<para>Add to <filename>/etc/rc.local</filename>:

<para>Add to <filename>/etc/rc.local</filename>:

<informalexample>

<informalexample>

<programlisting>for tty in /dev/ttyv?

<programlisting>for tty in /dev/ttyv?

do

do

  vidcontrol VGA_80x60 <$tty >/dev/null 2>&1

  vidcontrol VGA_80x60 <$tty >/dev/null 2>&1

done</programlisting>

done</programlisting>

</listitem>

</listitem>

<listitem>

<listitem>

<para>Add to <filename>/etc/profile</filename>:

<para>Add to <filename>/etc/profile</filename>:

<informalexample>

<informalexample>

<programlisting>TTYNAME=`basename \`tty\``

<programlisting>TTYNAME=`basename \`tty\``

if expr "$TTYNAME" : 'ttyv' >/dev/null

if expr "$TTYNAME" : 'ttyv' >/dev/null

  stty crt rows 60 columns 80

  stty crt rows 60 columns 80

fi</programlisting>

fi</programlisting>

</informalexample>

</informalexample>

</listitem>

</listitem>

</orderedlist>

</orderedlist>

<para>References:

<para>References:

</sect1>

</sect1>

allows one to more easily keep track of ones fonts without confusing

allows one to more easily keep track of ones fonts without confusing

them with the fonts that were originally provided.  For

them with the fonts that were originally provided.  For

example:

example:

<informalexample>

<informalexample>

<screen><lineannotation>Create a directory to contain the font files</>

<screen><lineannotation>Create a directory to contain the font files</>

bash$ <userinput>mkdir -p /usr/local/share/fonts/type1</>

bash$ <userinput>mkdir -p /usr/local/share/fonts/type1</>

<lineannotation>Maintain an index to cross reference the fonts</>

<lineannotation>Maintain an index to cross reference the fonts</>

bash$ <userinput>echo showboat - InfoMagic CICA, Dec 1994, /fonts/atm/showboat &gt;&gt;INDEX</></screen>

bash$ <userinput>echo showboat - InfoMagic CICA, Dec 1994, /fonts/atm/showboat &gt;&gt;INDEX</></screen>

</informalexample>

</informalexample>

<para>Now, to use a new font with X11, one must make the font file

<para>Now, to use a new font with X11, one must make the font file

available and update the font name files.  The X11 font names look

available and update the font name files.  The X11 font names look

like:

like:

<informalexample>

<informalexample>

<screen>-bitstream-charter-medium-r-normal-xxx-0-0-0-0-p-0-iso8859-1

<screen>-bitstream-charter-medium-r-normal-xxx-0-0-0-0-p-0-iso8859-1

     |        |      |    |   |     |  | | | | | |    \    \ 

     |        |      |    |   |     |  | | | | | |    \    \ 

     |        |      |        \     \	   \

     |        |      |        \     \	   \

  foundry  family  weight   slant  width  additional style</screen>

  foundry  family  weight   slant  width  additional style</screen>

</informalexample>

</informalexample>

<para>A new name needs to be created for each new font.  If you have

<para>A new name needs to be created for each new font.  If you have

some information from the documentation that accompanied the font,

some information from the documentation that accompanied the font,

then it could serve as the basis for creating the name.  If there is

then it could serve as the basis for creating the name.  If there is

no information, then you can get some idea by using

no information, then you can get some idea by using

file.  For example:

file.  For example:

<informalexample>

<informalexample>

<screen>bash$ <userinput>strings showboat.pfb | more</>

<screen>bash$ <userinput>strings showboat.pfb | more</>

%!FontType1-1.0: Showboat 001.001

%!FontType1-1.0: Showboat 001.001

end readonly def

end readonly def

/FontName /Showboat def

/FontName /Showboat def

--stdin--</screen>

--stdin--</screen>

<para>Using this information, a possible name might be:

<para>Using this information, a possible name might be:

<informalexample>

<informalexample>

<screen>-type1-Showboat-medium-r-normal-decorative-0-0-0-0-p-0-iso8859-1</screen>

<screen>-type1-Showboat-medium-r-normal-decorative-0-0-0-0-p-0-iso8859-1</screen>

</informalexample>

</informalexample>

<para>The components of our name are:

<para>The components of our name are:

<variablelist>

<variablelist>

<varlistentry><term>Foundry</term>

<varlistentry><term>Foundry</term>

</varlistentry>

</varlistentry>

</variablelist>

</variablelist>

<para>All of these names are arbitrary, but one should strive to be

<para>All of these names are arbitrary, but one should strive to be

compatible with the existing conventions.  A font is referenced by

compatible with the existing conventions.  A font is referenced by

and adjust the name based on the appearance of the font.</para>

and adjust the name based on the appearance of the font.</para>

<para>So, to complete our example:

<para>So, to complete our example:

<informalexample>

<informalexample>

<screen><lineannotation>Make the font accessible to X11</>

<screen><lineannotation>Make the font accessible to X11</>

bash$ <userinput>cd /usr/X11R6/lib/X11/fonts/Type1</>

bash$ <userinput>cd /usr/X11R6/lib/X11/fonts/Type1</>

<lineannotation>Examine the new font</>

<lineannotation>Examine the new font</>

bash$ <userinput>xfontsel -pattern -type1-*</></screen>

bash$ <userinput>xfontsel -pattern -type1-*</></screen>

</informalexample>

</informalexample>

<para>References:

<para>References:

<citetitle>The X Windows System in a Nutshell</>, <ulink

<citetitle>The X Windows System in a Nutshell</>, <ulink

URL="http://www.ora.com/">O'Reilly &amp; Associates</ulink>.</para>

URL="http://www.ora.com/">O'Reilly &amp; Associates</ulink>.</para>

<filename>.pfa</filename> or the <filename>.pfb</filename> format

<filename>.pfa</filename> or the <filename>.pfb</filename> format

fonts.  Using the font from the previous example, here is how to use

fonts.  Using the font from the previous example, here is how to use

it with Ghostscript:

it with Ghostscript:

<informalexample>

<informalexample>

<screen><lineannotation>Put the font in Ghostscript's font directory</>

<screen><lineannotation>Put the font in Ghostscript's font directory</>

bash$ <userinput>cd /usr/local/share/ghostscript/fonts</>

bash$ <userinput>cd /usr/local/share/ghostscript/fonts</>

>>showpage, press <return> to continue<<

>>showpage, press <return> to continue<<

GS&gt;<userinput>quit</></screen>

GS&gt;<userinput>quit</></screen>

</informalexample>

</informalexample>

<para>References: <filename>fonts.txt</filename> in the Ghostscript

<para>References: <filename>fonts.txt</filename> in the Ghostscript

4.01 distribution</para>

4.01 distribution</para>

<para>The first tool is <command>afmtodit</>.  This is not normally

<para>The first tool is <command>afmtodit</>.  This is not normally

installed, so it must be retrieved from the source distribution.  I

installed, so it must be retrieved from the source distribution.  I

found I had to change the first line of the file, so I did:

found I had to change the first line of the file, so I did:

<informalexample>

<informalexample>

<screen>bash$ <userinput>cp /usr/src/gnu/usr.bin/groff/afmtodit/afmtodit.pl /tmp</>

<screen>bash$ <userinput>cp /usr/src/gnu/usr.bin/groff/afmtodit/afmtodit.pl /tmp</>

bash$ <userinput>ex /tmp/afmtodit.pl

bash$ <userinput>ex /tmp/afmtodit.pl

.

.

:wq</></screen>

:wq</></screen>

</informalexample>

</informalexample>

<para>This tool will create the groff font file from the metrics file

<para>This tool will create the groff font file from the metrics file

(<filename>.afm</filename> suffix.) Continuing with our

(<filename>.afm</filename> suffix.) Continuing with our

example:

example:

<informalexample>

<informalexample>

<screen><lineannotation>Many <filename>.afm</> files are in Mac format&hellip ^M delimited lines

<screen><lineannotation>Many <filename>.afm</> files are in Mac format&hellip ^M delimited lines

We need to convert them to unix style ^J delimited lines</>

We need to convert them to unix style ^J delimited lines</>

bash$ <userinput>cd /usr/share/groff_font/devps</>

bash$ <userinput>cd /usr/share/groff_font/devps</>

bash$ <userinput>/tmp/afmtodit.pl -d DESC -e text.enc /tmp/showboat.afm generate/textmap SHOWBOAT</></screen>

bash$ <userinput>/tmp/afmtodit.pl -d DESC -e text.enc /tmp/showboat.afm generate/textmap SHOWBOAT</></screen>

</informalexample>

</informalexample>

<para>The font can now be referenced with the name SHOWBOAT.</para>

<para>The font can now be referenced with the name SHOWBOAT.</para>

font.  The <filename>download</> file must reference the internal

font.  The <filename>download</> file must reference the internal

name of the font.  This can easily be determined from the groff font

name of the font.  This can easily be determined from the groff font

file as illustrated:

file as illustrated:

<informalexample>

<informalexample>

<screen><lineannotation>Create the <filename>.pfa</> font file</>

<screen><lineannotation>Create the <filename>.pfa</> font file</>

bash$ <userinput>pfbtops /usr/local/share/fonts/type1/showboat.pfb &gt;showboat.pfa</></screen>

bash$ <userinput>pfbtops /usr/local/share/fonts/type1/showboat.pfb &gt;showboat.pfa</></screen>

</informalexample>

</informalexample>

Of course, if the <filename>.pfa</filename> file is already

Of course, if the <filename>.pfa</filename> file is already

available, just use a symbolic link to reference it.

available, just use a symbolic link to reference it.

<informalexample>

<informalexample>

<screen><lineannotation>Get the internal font name</>

<screen><lineannotation>Get the internal font name</>

bash$ <userinput>fgrep internalname SHOWBOAT</>

bash$ <userinput>fgrep internalname SHOWBOAT</>

.

.

:wq</></screen>

:wq</></screen>

</informalexample>

</informalexample>

<para>To test the font:

<para>To test the font:

<informalexample>

<informalexample>

<screen>bash$ <userinput>cd /tmp</>

<screen>bash$ <userinput>cd /tmp</>

bash$ <userinput>cat &gt;example.t &lt;&lt;EOF

bash$ <userinput>cat &gt;example.t &lt;&lt;EOF

<lineannotation>To print it</>

<lineannotation>To print it</>

bash$ <userinput>lpr -Ppostscript example.ps</></screen>

bash$ <userinput>lpr -Ppostscript example.ps</></screen>

</informalexample>

</informalexample>

<para>References:

<para>References:

<filename>/usr/src/gnu/usr.bin/groff/afmtodit/afmtodit.man</filename>,

<filename>/usr/src/gnu/usr.bin/groff/afmtodit/afmtodit.man</filename>,

</sect1>

</sect1>

	  <command>ttf2pf.ps</command> above, and

	  <command>ttf2pf.ps</command> above, and

	  <replaceable>PS_font_name</replaceable> is the font name

	  <replaceable>PS_font_name</replaceable> is the font name

	  used from that command, as well as the name that

	  used from that command, as well as the name that

	  will use for references to this font. For example, assuming

	  will use for references to this font. For example, assuming

	  you used the first <command>tiff2pf.ps</command> command

	  you used the first <command>tiff2pf.ps</command> command

	  above, then the 3of9 Barcode font can be created using the

	  above, then the 3of9 Barcode font can be created using the

	  <filename>.afm</filename> file prior to running

	  <filename>.afm</filename> file prior to running

	  <command>afmtodit</command>.  This name must also match the

	  <command>afmtodit</command>.  This name must also match the

	  one used in the Fontmap file if you wish to pipe

	  one used in the Fontmap file if you wish to pipe

      </listitem>

      </listitem>

    </orderedlist>

    </orderedlist>

  </sect1>

  </sect1>

<para>This rather dismal situation may soon change.  

<para>This rather dismal situation may soon change.  

The <ulink url="http://www.freetype.org/">FreeType Project</ulink> 

The <ulink url="http://www.freetype.org/">FreeType Project</ulink> 

is currently developing a useful set of FreeType tools:

is currently developing a useful set of FreeType tools:

<itemizedlist>

<itemizedlist>

<listitem>

<listitem>

TrueType fonts in addition to regular fonts.  Though currently in 

TrueType fonts in addition to regular fonts.  Though currently in 

beta, it is said to be quite useable.  See <ulink 

beta, it is said to be quite useable.  See <ulink 

url="http://www.dcs.ed.ac.uk/home/jec/programs/xfsft/">Juliusz 

url="http://www.dcs.ed.ac.uk/home/jec/programs/xfsft/">Juliusz 

for FreeBSD can be found at <ulink 

for FreeBSD can be found at <ulink 

url="http://math.missouri.edu/~stephen/software/">Stephen Montgomery's

url="http://math.missouri.edu/~stephen/software/">Stephen Montgomery's

software page</ulink>.

software page</ulink>.

</listitem>

</listitem>

<listitem>

<listitem>

server for X11, available under <ulink 

server for X11, available under <ulink 

url=" ftp://sunsite.unc.edu/pub/Linux/X11/fonts">

url=" ftp://sunsite.unc.edu/pub/Linux/X11/fonts">

ftp://sunsite.unc.edu/pub/Linux/X11/fonts</ulink>.

ftp://sunsite.unc.edu/pub/Linux/X11/fonts</ulink>.

</listitem>

</listitem>

BDF files suitable for use in an X environment from TrueType files.  Linux

BDF files suitable for use in an X environment from TrueType files.  Linux

binaries are said to be available from <ulink 

binaries are said to be available from <ulink 

url="ftp://crl.nmsu.edu/CLR/multiling/General">ftp://crl.nmsu.edu/CLR/multiling/General/</ulink>.

url="ftp://crl.nmsu.edu/CLR/multiling/General">ftp://crl.nmsu.edu/CLR/multiling/General/</ulink>.

</listitem>

</listitem>

<listitem>

<listitem>

For people requiring the use of Asian TrueType fonts, the

For people requiring the use of Asian TrueType fonts, the

<command>XTT</command> font server may be worth a look.  Information about 

<command>XTT</command> font server may be worth a look.  Information about 

<command>XTT</command> can be found at URL: <ulink 

<command>XTT</command> can be found at URL: <ulink 

url="http://hawk.ise.chuo-u.ac.jp/student/person/tshiozak/study/freebsd-at-random/x-tt/index-en.html">http://hawk.ise.chuo-u.ac.jp/student/person/tshiozak/study/freebsd-at-random/x-tt/index-en.html</ulink>.

url="http://hawk.ise.chuo-u.ac.jp/student/person/tshiozak/study/freebsd-at-random/x-tt/index-en.html">http://hawk.ise.chuo-u.ac.jp/student/person/tshiozak/study/freebsd-at-random/x-tt/index-en.html</ulink>.

</listitem>

</listitem>

<listitem>

<listitem>

</listitem>

</listitem>

</itemizedlist>

</itemizedlist>

<para>

<para>

The 

The 

<ulink url="http://www.freetype.org/projects.htm">FreeType Projects page

<ulink url="http://www.freetype.org/projects.htm">FreeType Projects page

entirely free, or are share-ware.  In addition, there are many

entirely free, or are share-ware.  In addition, there are many

inexpensive CDROMs available that contain many fonts.  Some Internet

inexpensive CDROMs available that contain many fonts.  Some Internet

locations (as of August 1996) are:

locations (as of August 1996) are:

<itemizedlist>

<itemizedlist>

<listitem><para><ulink

<listitem><para><ulink

<listitem><para><ulink

<listitem><para><ulink

url="http://www.inil.com/users/elfring/esf.htm">http://www.inil.com/users/elfring/esf.htm</ulink></para></listitem>

url="http://www.inil.com/users/elfring/esf.htm">http://www.inil.com/users/elfring/esf.htm</ulink></para></listitem>

</sect1>

</sect1>

<sect1>

<sect1>

<title>Additional questions</title>

<title>Additional questions</title>

<itemizedlist>

<itemizedlist>

<listitem>

<listitem>

</listitem>

</listitem>

</itemizedlist>

</itemizedlist>

</sect1>

</sect1>

</article>

</article>