|
Lines 66-72
Link Here
|
| 66 |
<abstract> |
66 |
<abstract> |
| 67 |
<para>This document contains a description of the various font |
67 |
<para>This document contains a description of the various font |
| 68 |
files that may be used with FreeBSD and the syscons driver, |
68 |
files that may be used with FreeBSD and the syscons driver, |
| 69 |
X11, Ghostscript and Groff. Cookbook examples are provided |
69 |
<application>X11</application>, <application>Ghostscript</application> |
|
|
70 |
and <application>Groff</application>. Cookbook examples are provided |
| 70 |
for switching the syscons display to 80x60 mode, and for using |
71 |
for switching the syscons display to 80x60 mode, and for using |
| 71 |
type 1 fonts with the above application programs.</para> |
72 |
type 1 fonts with the above application programs.</para> |
| 72 |
</abstract> |
73 |
</abstract> |
|
Lines 184-190
Link Here
|
| 184 |
<listitem> |
185 |
<listitem> |
| 185 |
<variablelist> |
186 |
<variablelist> |
| 186 |
<varlistentry> |
187 |
<varlistentry> |
| 187 |
<term>Ghostscript</term> |
188 |
<term><application>Ghostscript</application></term> |
| 188 |
|
189 |
|
| 189 |
<listitem> |
190 |
<listitem> |
| 190 |
<para><filename>.pfa</filename>, |
191 |
<para><filename>.pfa</filename>, |
|
Lines 194-200
Link Here
|
| 194 |
</varlistentry> |
195 |
</varlistentry> |
| 195 |
|
196 |
|
| 196 |
<varlistentry> |
197 |
<varlistentry> |
| 197 |
<term>X11</term> |
198 |
<term><application>X11</application></term> |
| 198 |
|
199 |
|
| 199 |
<listitem> |
200 |
<listitem> |
| 200 |
<para><filename>.pfa</filename>, |
201 |
<para><filename>.pfa</filename>, |
|
Lines 203-209
Link Here
|
| 203 |
</varlistentry> |
204 |
</varlistentry> |
| 204 |
|
205 |
|
| 205 |
<varlistentry> |
206 |
<varlistentry> |
| 206 |
<term>Groff</term> |
207 |
<term><application>Groff</application></term> |
| 207 |
|
208 |
|
| 208 |
<listitem> |
209 |
<listitem> |
| 209 |
<para><filename>.pfa</filename>, |
210 |
<para><filename>.pfa</filename>, |
|
Lines 212-218
Link Here
|
| 212 |
</varlistentry> |
213 |
</varlistentry> |
| 213 |
|
214 |
|
| 214 |
<varlistentry> |
215 |
<varlistentry> |
| 215 |
<term>Povray</term> |
216 |
<term><application>Povray</application></term> |
| 216 |
|
217 |
|
| 217 |
<listitem> |
218 |
<listitem> |
| 218 |
<para><filename>.ttf</filename></para> |
219 |
<para><filename>.ttf</filename></para> |
|
Lines 274-286
Link Here
|
| 274 |
</sect1> |
275 |
</sect1> |
| 275 |
|
276 |
|
| 276 |
<sect1> |
277 |
<sect1> |
| 277 |
<title>Using type 1 fonts with X11</title> |
278 |
<title>Using type 1 fonts with <application>X11</application></title> |
| 278 |
|
279 |
|
| 279 |
<para>X11 can use either the <filename>.pfa</filename> or the |
280 |
<para><application>X11</application> can use either the <filename>.pfa</filename> or the |
| 280 |
<filename>.pfb</filename> format fonts. The X11 fonts are |
281 |
<filename>.pfb</filename> format fonts. The <application>X11</application> fonts are |
| 281 |
located in various subdirectories under |
282 |
located in various subdirectories under |
| 282 |
<filename>/usr/X11R6/lib/X11/fonts</filename>. Each font file |
283 |
<filename>/usr/X11R6/lib/X11/fonts</filename>. Each font file |
| 283 |
is cross referenced to its X11 name by the contents of the |
284 |
is cross referenced to its <application>X11</application> name by the contents of the |
| 284 |
<filename>fonts.dir</filename> file in each directory.</para> |
285 |
<filename>fonts.dir</filename> file in each directory.</para> |
| 285 |
|
286 |
|
| 286 |
<para>There is already a directory named <filename>Type1</filename>. The |
287 |
<para>There is already a directory named <filename>Type1</filename>. The |
|
Lines 306-313
Link Here
|
| 306 |
&prompt.user; <userinput>echo showboat - InfoMagic CICA, Dec 1994, /fonts/atm/showboat >>INDEX</userinput></screen> |
307 |
&prompt.user; <userinput>echo showboat - InfoMagic CICA, Dec 1994, /fonts/atm/showboat >>INDEX</userinput></screen> |
| 307 |
</informalexample> |
308 |
</informalexample> |
| 308 |
|
309 |
|
| 309 |
<para>Now, to use a new font with X11, one must make the font file |
310 |
<para>Now, to use a new font with <application>X11</application>, one must make the font file |
| 310 |
available and update the font name files. The X11 font names |
311 |
available and update the font name files. The <application>X11</application> font names |
| 311 |
look like:</para> |
312 |
look like:</para> |
| 312 |
|
313 |
|
| 313 |
<informalexample> |
314 |
<informalexample> |
|
Lines 439-445
Link Here
|
| 439 |
|
440 |
|
| 440 |
<para>All of these names are arbitrary, but one should strive to |
441 |
<para>All of these names are arbitrary, but one should strive to |
| 441 |
be compatible with the existing conventions. A font is |
442 |
be compatible with the existing conventions. A font is |
| 442 |
referenced by name with possible wild cards by an X11 program, |
443 |
referenced by name with possible wild cards by an <application>X11</application> program, |
| 443 |
so the name chosen should make some sense. One might begin by |
444 |
so the name chosen should make some sense. One might begin by |
| 444 |
simply using |
445 |
simply using |
| 445 |
|
446 |
|
|
Lines 492-503
Link Here
|
| 492 |
<sect1> |
493 |
<sect1> |
| 493 |
<title>Using type 1 fonts with Ghostscript</title> |
494 |
<title>Using type 1 fonts with Ghostscript</title> |
| 494 |
|
495 |
|
| 495 |
<para>Ghostscript references a font via its <filename>Fontmap</filename> |
496 |
<para><application>Ghostscript</application> references a font via its <filename>Fontmap</filename> |
| 496 |
file. This must be modified in a similar way to the X11 |
497 |
file. This must be modified in a similar way to the <application>X11</application> |
| 497 |
<filename>fonts.dir</filename> file. Ghostscript can use either |
498 |
<filename>fonts.dir</filename> file. <application>Ghostscript</application> can use either |
| 498 |
the <filename>.pfa</filename> or the <filename>.pfb</filename> |
499 |
the <filename>.pfa</filename> or the <filename>.pfb</filename> |
| 499 |
format fonts. Using the font from the previous example, here is |
500 |
format fonts. Using the font from the previous example, here is |
| 500 |
how to use it with Ghostscript:</para> |
501 |
how to use it with <application>Ghostscript</application>:</para> |
| 501 |
|
502 |
|
| 502 |
<informalexample> |
503 |
<informalexample> |
| 503 |
<screen><lineannotation>Put the font in Ghostscript's font directory</lineannotation> |
504 |
<screen><lineannotation>Put the font in Ghostscript's font directory</lineannotation> |
|
Lines 530-551
Link Here
|
| 530 |
</informalexample> |
531 |
</informalexample> |
| 531 |
|
532 |
|
| 532 |
<para>References: <filename>fonts.txt</filename> in the |
533 |
<para>References: <filename>fonts.txt</filename> in the |
| 533 |
Ghostscript 4.01 distribution</para> |
534 |
<application>Ghostscript 4.01</application> distribution</para> |
| 534 |
</sect1> |
535 |
</sect1> |
| 535 |
|
536 |
|
| 536 |
<sect1> |
537 |
<sect1> |
| 537 |
<title>Using type 1 fonts with Groff</title> |
538 |
<title>Using type 1 fonts with Groff</title> |
| 538 |
|
539 |
|
| 539 |
<para>Now that the new font can be used by both X11 and |
540 |
<para>Now that the new font can be used by both <application>X11</application> and |
| 540 |
Ghostscript, how can one use the new font with groff? First of |
541 |
<application>Ghostscript</application>, how can one use the new font |
|
|
542 |
with <application>groff</application>? First of |
| 541 |
all, since we are dealing with type 1 &postscript; fonts, the |
543 |
all, since we are dealing with type 1 &postscript; fonts, the |
| 542 |
groff device that is applicable is the <emphasis>ps</emphasis> |
544 |
<application>groff</application> device that is applicable is the <emphasis>ps</emphasis> |
| 543 |
device. A font file must be created for each font that groff |
545 |
device. A font file must be created for each font that <application>groff</application> |
| 544 |
can use. A groff font name is just a file in |
546 |
can use. A <application>groff</application> font name is just a file in |
| 545 |
<filename>/usr/share/groff_font/devps</filename>. With our |
547 |
<filename>/usr/share/groff_font/devps</filename>. With our |
| 546 |
example, the font file could be |
548 |
example, the font file could be |
| 547 |
<filename>/usr/share/groff_font/devps/SHOWBOAT</filename>. The |
549 |
<filename>/usr/share/groff_font/devps/SHOWBOAT</filename>. The |
| 548 |
file must be created using tools provided by groff.</para> |
550 |
file must be created using tools provided by <application>groff</application>.</para> |
| 549 |
|
551 |
|
| 550 |
<para>The first tool is <command>afmtodit</command>. This is not |
552 |
<para>The first tool is <command>afmtodit</command>. This is not |
| 551 |
normally installed, so it must be retrieved from the source |
553 |
normally installed, so it must be retrieved from the source |
|
Lines 561-567
Link Here
|
| 561 |
:wq</userinput></screen> |
563 |
:wq</userinput></screen> |
| 562 |
</informalexample> |
564 |
</informalexample> |
| 563 |
|
565 |
|
| 564 |
<para>This tool will create the groff font file from the metrics |
566 |
<para>This tool will create the <application>groff</application> font file from the metrics |
| 565 |
file (<filename>.afm</filename> suffix.) Continuing with our |
567 |
file (<filename>.afm</filename> suffix.) Continuing with our |
| 566 |
example:</para> |
568 |
example:</para> |
| 567 |
|
569 |
|
|
Lines 580-587
Link Here
|
| 580 |
<para>The font can now be referenced with the name |
582 |
<para>The font can now be referenced with the name |
| 581 |
SHOWBOAT.</para> |
583 |
SHOWBOAT.</para> |
| 582 |
|
584 |
|
| 583 |
<para>If ghostscript is used to drive the printers on the system, |
585 |
<para>If <application>Ghostscript</application> is used to drive the printers on the system, |
| 584 |
then nothing more needs to be done. However, if true PostScript |
586 |
then nothing more needs to be done. However, if true &postscript; |
| 585 |
printers are used, then the font must be down loaded to the |
587 |
printers are used, then the font must be down loaded to the |
| 586 |
printer in order for the font to be used (unless the printer |
588 |
printer in order for the font to be used (unless the printer |
| 587 |
happens to have the showboat font built in or on an accessible |
589 |
happens to have the showboat font built in or on an accessible |
|
Lines 705-711
Link Here
|
| 705 |
upper case, so any renaming must be consistent with this. |
707 |
upper case, so any renaming must be consistent with this. |
| 706 |
(Actually, <filename>GS_TTF.PS</filename> and |
708 |
(Actually, <filename>GS_TTF.PS</filename> and |
| 707 |
<filename>PFS2AFM.PS</filename> are supposedly part of the |
709 |
<filename>PFS2AFM.PS</filename> are supposedly part of the |
| 708 |
ghostscript distribution, but it is just as easy to use |
710 |
<application>Ghostscript</application> distribution, but it is just as easy to use |
| 709 |
these as an isolated utility. FreeBSD does not seem to |
711 |
these as an isolated utility. FreeBSD does not seem to |
| 710 |
include the latter.) You also may want to have these |
712 |
include the latter.) You also may want to have these |
| 711 |
installed to |
713 |
installed to |
|
Lines 717-723
Link Here
|
| 717 |
<term><command>afmtodit</command></term> |
719 |
<term><command>afmtodit</command></term> |
| 718 |
|
720 |
|
| 719 |
<listitem> |
721 |
<listitem> |
| 720 |
<para>Creates font files for use with groff from ascii font |
722 |
<para>Creates font files for use with <application>groff</application> from ascii font |
| 721 |
metrics file. This usually resides in the directory, |
723 |
metrics file. This usually resides in the directory, |
| 722 |
<filename>/usr/src/contrib/groff/afmtodit</filename>, and |
724 |
<filename>/usr/src/contrib/groff/afmtodit</filename>, and |
| 723 |
requires some work to get going.</para> |
725 |
requires some work to get going.</para> |
|
Lines 793-799
Link Here
|
| 793 |
</listitem> |
795 |
</listitem> |
| 794 |
|
796 |
|
| 795 |
<listitem> |
797 |
<listitem> |
| 796 |
<para>Create the groff PostScript file:</para> |
798 |
<para>Create the <application>groff</application> PostScript file:</para> |
| 797 |
|
799 |
|
| 798 |
<para>Change directories to |
800 |
<para>Change directories to |
| 799 |
<filename>/usr/share/groff_font/devps</filename> so as to |
801 |
<filename>/usr/share/groff_font/devps</filename> so as to |
|
Lines 849-858
Link Here
|
| 849 |
fonts available in this format.</para> |
851 |
fonts available in this format.</para> |
| 850 |
|
852 |
|
| 851 |
<para>Unfortunately, there are few applications that I am aware of |
853 |
<para>Unfortunately, there are few applications that I am aware of |
| 852 |
that can use this format: Ghostscript and Povray come to mind. |
854 |
that can use this format: <application>Ghostscript</application> |
| 853 |
Ghostscript's support, according to the documentation, is |
855 |
and <application>Povray</application> come to mind. |
|
|
856 |
<application>Ghostscript's</application> support, according to the documentation, is |
| 854 |
rudimentary and the results are likely to be inferior to type 1 |
857 |
rudimentary and the results are likely to be inferior to type 1 |
| 855 |
fonts. Povray version 3 also has the ability to use TrueType |
858 |
fonts. <application>Povray</application> version 3 also has the ability to use TrueType |
| 856 |
fonts, but I rather doubt many people will be creating documents |
859 |
fonts, but I rather doubt many people will be creating documents |
| 857 |
as a series of raytraced pages :-).</para> |
860 |
as a series of raytraced pages :-).</para> |
| 858 |
|
861 |
|
|
Lines 871-877
Link Here
|
| 871 |
</listitem> |
874 |
</listitem> |
| 872 |
|
875 |
|
| 873 |
<listitem> |
876 |
<listitem> |
| 874 |
<para>The <command>xfsft</command> font server for X11 can |
877 |
<para>The <command>xfsft</command> font server for <application>X11</application> can |
| 875 |
serve TrueType fonts in addition to regular fonts. Though |
878 |
serve TrueType fonts in addition to regular fonts. Though |
| 876 |
currently in beta, it is said to be quite usable. See |
879 |
currently in beta, it is said to be quite usable. See |
| 877 |
<ulink |
880 |
<ulink |
|
Lines 883-889
Link Here
|
| 883 |
</listitem> |
886 |
</listitem> |
| 884 |
|
887 |
|
| 885 |
<listitem> |
888 |
<listitem> |
| 886 |
<para><command>xfstt</command> is another font server for X11, |
889 |
<para><application>xfstt</application> is another font server for |
|
|
890 |
<application>X11</application>, |
| 887 |
available under <ulink url=" |
891 |
available under <ulink url=" |
| 888 |
ftp://sunsite.unc.edu/pub/Linux/X11/fonts/"></ulink>.</para> |
892 |
ftp://sunsite.unc.edu/pub/Linux/X11/fonts/"></ulink>.</para> |
| 889 |
</listitem> |
893 |
</listitem> |
|
Lines 965-971
Link Here
|
| 965 |
</listitem> |
969 |
</listitem> |
| 966 |
|
970 |
|
| 967 |
<listitem> |
971 |
<listitem> |
| 968 |
<para>How to generate the groff character mapping files for |
972 |
<para>How to generate the <application>groff</application> character mapping files for |
| 969 |
PostScript fonts with non-standard character names?</para> |
973 |
PostScript fonts with non-standard character names?</para> |
| 970 |
</listitem> |
974 |
</listitem> |
| 971 |
|
975 |
|
|
Lines 976-982
Link Here
|
| 976 |
|
980 |
|
| 977 |
<listitem> |
981 |
<listitem> |
| 978 |
<para>It would be good to have examples of using TrueType |
982 |
<para>It would be good to have examples of using TrueType |
| 979 |
fonts with povray and ghostscript.</para> |
983 |
fonts with <application>Povray</application> and <application>Ghostscript</application>.</para> |
| 980 |
</listitem> |
984 |
</listitem> |
| 981 |
</itemizedlist> |
985 |
</itemizedlist> |
| 982 |
</sect1> |
986 |
</sect1> |