From owner-freebsd-doc Fri Oct 8 8: 0:23 1999 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id E701314E7D for ; Fri, 8 Oct 1999 08:00:00 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id IAA96234; Fri, 8 Oct 1999 08:00:00 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from terrapin.ru.ac.za (terrapin.ru.ac.za [146.231.128.6]) by hub.freebsd.org (Postfix) with ESMTP id 3E5101543F for ; Fri, 8 Oct 1999 07:50:50 -0700 (PDT) (envelope-from nbm@mithrandr.moria.org) Received: from duca.dialup.ru.ac.za ([146.231.98.24] helo=mithrandr.moria.org) by terrapin.ru.ac.za with esmtp (Exim 3.03 #1) id 11ZbM0-000MEZ-00 for FreeBSD-gnats-submit@freebsd.org; Fri, 08 Oct 1999 16:50:40 +0200 Received: (qmail 61049 invoked by uid 1001); 8 Oct 1999 14:50:38 -0000 Message-Id: <19991008145038.61048.qmail@mithrandr.moria.org> Date: 8 Oct 1999 14:50:38 -0000 From: nbm@rucus.ru.ac.za Reply-To: nbm@rucus.ru.ac.za To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: docs/14206: whitespace fixup for fonts article Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 14206 >Category: docs >Synopsis: whitespace fixup for fonts article >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Fri Oct 8 08:00:00 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Neil Blakey-Milner >Release: FreeBSD 4.0-CURRENT i386 >Organization: Rhodes University Computer Users' Society >Environment: FreeBSD mithrandr.moria.org 4.0-CURRENT FreeBSD 4.0-CURRENT #2: Wed Sep 29 17:30:21 SAST 1999 root@mithrandr.moria.org:/usr/src/sys/compile/MITHRANDR i386 >Description: This is an entirely whitespace change, which applies the new proposed indentation/whitespace style. Translators can ignore this, but should take note of the style. This patch relies on docs/14197. >How-To-Repeat: >Fix: --- article.sgml.old Thu Oct 7 21:57:25 1999 +++ article.sgml Fri Oct 8 14:54:08 1999 @@ -23,265 +23,294 @@ -->
+ + Fonts and FreeBSD + + A Tutorial + + + + Dave + + Bodenstab + + +
+ imdave@synet.net +
+ + + + + Wed Aug 7, 1996 + + + This document contains a description of the various font + files that may be used with FreeBSD and the syscons driver, + X11, Ghostscript and Groff. Cookbook examples are provided + for switching the syscons display to 80x60 mode, and for using + type 1 fonts with the above application programs. + + + + + Introduction + + There are many sources of fonts available, and one might ask + how they might be used with FreeBSD. The answer can be found by + carefully searching the documentation for the component that one + would like to use. This is very time consuming, so this + tutorial is an attempt to provide a shortcut for others who + might be interested. + + + + Basic terminology + + There are many different font formats and associated font + file suffixes. A few that will be addressed here are: + + + + .pfa, .pfb + + + Postscript type 1 fonts. The + .pfa is the + Ascii form and + .pfb the Binary + form. + + + + + .afm + + + The font metrics associated with a type 1 font. + + + + + .pfm + + + The printer font metrics associated with a type 1 + font. + + + + + .ttf + + + A TrueType font + + + + + .fot + + + An indirect reference to a TrueType font (not an + actual font) + + + + + .fon, .fnt + + + Bitmapped screen fonts + + + + + The .fot file is used by Windows as + sort of a symbolic link to the actual TrueType font + (.ttf) file. The .fon + font files are also used by Windows. I know of no way to use + this font format with FreeBSD. + + + + What font formats can I use? + + Which font file format is useful depends on the application + being used. FreeBSD by itself uses no fonts. Application + programs and/or drivers may make use of the font files. Here is + a small cross reference of application/driver to the font type + suffixes: + + + + Driver + + + + + syscons + + + .fnt + + + + + + + + Application + + + + + Ghostscript + + + .pfa, + .pfb, + .ttf + + + + + X11 + + + .pfa, + .pfb + + + + + Groff + + + .pfa, + .afm + + + + + Povray + + + .ttf + + + + + + + + The .fnt suffix is used quite + frequently. I suspect that whenever someone wanted to create a + specialized font file for their application, more often than not + they chose this suffix. Therefore, it is likely that files with + this suffix are not all the same format; specifically, the + .fnt files used by syscons under FreeBSD + may not be the same format as a .fnt file + one encounters in the MSDOS/Windows environment. I have not + made any attempt at using other .fnt files + other than those provided with FreeBSD. + + + + Setting a virtual console to 80x60 line mode + + First, a 8x8 font must be loaded. + /etc/sysconfig should contain the + lines: + + + +# Choose font 8x8 from /usr/share/syscons/fonts/* (or NO for default) +font8x8=/usr/share/syscons/fonts/cp437-8x8.fnt + + + + The command to actually switch the mode is + &man.vidcontrol.1: - -Fonts and FreeBSD -A Tutorial - - - -Dave -Bodenstab - -
imdave@synet.net
- - - - -Wed Aug 7, 1996 - -This document contains a description of the various -font files that may be used with FreeBSD and the syscons driver, X11, -Ghostscript and Groff. Cookbook examples are provided for switching -the syscons display to 80x60 mode, and for using type 1 fonts with -the above application programs. - - - - -Introduction - -There are many sources of fonts available, and one might ask -how they might be used with FreeBSD. The answer can be found by -carefully searching the documentation for the component that one -would like to use. This is very time consuming, so this tutorial is -an attempt to provide a shortcut for others who might be -interested. - - - - -Basic terminology - -There are many different font formats and associated font file -suffixes. A few that will be addressed here are: - - - -.pfa, .pfb - -Postscript type 1 fonts. The .pfa is the -Ascii form and .pfb the -Binary form. - - - -.afm - -The font metrics associated with a type 1 -font. - - - -.pfm - -The printer font metrics associated with a type 1 -font. - - - -.ttf - -A TrueType font - - - -.fot - -An indirect reference to a TrueType font (not an -actual font) - - - -.fon, .fnt - -Bitmapped screen fonts - - - - -The .fot file is used by Windows as sort -of a symbolic link to the actual TrueType font -(.ttf) file. The .fon font -files are also used by Windows. I know of no way to use this font -format with FreeBSD. - - - - -What font formats can I use? - -Which font file format is useful depends on the application -being used. FreeBSD by itself uses no fonts. Application programs -and/or drivers may make use of the font files. Here is a small cross -reference of application/driver to the font type suffixes: - - -Driver - - -syscons - -.fnt - - - - - - - - -Application - - - -Ghostscript - -.pfa, .pfb, .ttf - - - - -X11 - - -.pfa, .pfb - - - - -Groff - - -.pfa, .afm - - - - -Povray - - -.ttf - - - - - - - - - -The .fnt suffix is used quite frequently. -I suspect that whenever someone wanted to create a specialized font -file for their application, more often than not they chose this -suffix. Therefore, it is likely that files with this suffix are not -all the same format; specifically, the .fnt -files used by syscons under FreeBSD may not be the same format as a -.fnt file one encounters in the MSDOS/Windows -environment. I have not made any attempt at using other -.fnt files other than those provided with -FreeBSD. - - - - -Setting a virtual console to 80x60 line mode - -First, a 8x8 font must be loaded. -/etc/sysconfig should contain the lines: - - -# Choose font 8x8 from /usr/share/syscons/fonts/* (or NO for default) -font8x8=/usr/share/syscons/fonts/cp437-8x8.fnt - - -The command to actually switch the mode is -&man.vidcontrol.1: - - -bash$ vidcontrol VGA_80x60 - - -Various screen orientated programs, such as -&man.vi.1, must be able to -determine the current screen dimensions. These can be set with -&man.stty.1;: - - -bash$ stty crt rows 60 columns 80 - - -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 -do this is: - - - - -Modify /etc/sysconfig as above - - - -Add to /etc/rc.local: - -for tty in /dev/ttyv? + +bash$ vidcontrol VGA_80x60 + + + + Various screen orientated programs, such as &man.vi.1, must + be able to determine the current screen dimensions. These can + be set with &man.stty.1;: + + + +bash$ stty crt rows 60 columns 80 + + + + 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 do this is: + + + + Modify /etc/sysconfig as + above + + + + Add to /etc/rc.local: + + + +for tty in /dev/ttyv? do vidcontrol VGA_80x60 <$tty >/dev/null 2>&1 -done +done + - + + + + Add to /etc/profile: - -Add to /etc/profile: - -TTYNAME=`basename \`tty\`` + +TTYNAME=`basename \`tty\`` if expr "$TTYNAME" : 'ttyv' >/dev/null then stty crt rows 60 columns 80 -fi +fi + - + + + + References: &man.stty.1;, &man.vidcontrol.1;. + + + + Using type 1 fonts with X11 + + X11 can use either the .pfa or the + .pfb format fonts. The X11 fonts are + located in various subdirectories under + /usr/X11R6/lib/X11/fonts. Each font file + is cross referenced to its X11 name by the contents of the + fonts.dir file in each directory. + + There is already a directory named Type1. The + most straight forward way to add a new font is to put it into + this directory. A better way is to keep all new fonts in a + separate directory and use a symbolic link to the additional + font. This allows one to more easily keep track of ones fonts + without confusing them with the fonts that were originally + provided. For example: - - -References: -&man.stty.1;, -&man.vidcontrol.1;. - - - - -Using type 1 fonts with X11 - -X11 can use either the .pfa or the -.pfb format fonts. The X11 fonts are located in -various subdirectories under -/usr/X11R6/lib/X11/fonts. Each font file is -cross referenced to its X11 name by the contents of the -fonts.dir file in each directory. - -There is already a directory named Type1. The most -straight forward way to add a new font is to put it into this -directory. A better way is to keep all new fonts in a separate -directory and use a symbolic link to the additional font. This -allows one to more easily keep track of ones fonts without confusing -them with the fonts that were originally provided. For -example: - -Create a directory to contain the font files + +Create a directory to contain the font files bash$ mkdir -p /usr/local/share/fonts/type1 bash$ cd /usr/local/share/fonts/type1 @@ -292,16 +321,18 @@ bash$ cp /cdrom/fonts/atm/showboat/showboat.afm . Maintain an index to cross reference the fonts -bash$ echo showboat - InfoMagic CICA, Dec 1994, /fonts/atm/showboat >>INDEX +bash$ echo showboat - InfoMagic CICA, Dec 1994, /fonts/atm/showboat >>INDEX + - -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 -like: - + + 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 like: + --bitstream-charter-medium-r-normal-xxx-0-0-0-0-p-0-iso8859-1 - | | | | | | | | | | | | \ \ + +-bitstream-charter-medium-r-normal-xxx-0-0-0-0-p-0-iso8859-1 + | | | | | | | | | | | | \ \ | | | | | \ \ \ \ \ \ \ +----+- character set | | | | \ \ \ \ \ \ \ +- average width | | | | \ \ \ \ \ \ +- spacing @@ -310,18 +341,19 @@ | | | \ \ \ \ +- points | | | \ \ \ +- pixels | | | \ \ \ - foundry family weight slant width additional style + foundry family weight slant width additional style + - -A new name needs to be created for each new font. If you have -some information from the documentation that accompanied the font, -then it could serve as the basis for creating the name. If there is -no information, then you can get some idea by using -&man.strings.1; on the font -file. For example: - + + A new name needs to be created for each new font. If you + have some information from the documentation that accompanied + the font, then it could serve as the basis for creating the + name. If there is no information, then you can get some idea by + using &man.strings.1; on the font file. For example: + -bash$ strings showboat.pfb | more + +bash$ strings showboat.pfb | more %!FontType1-1.0: Showboat 001.001 %%CreationDate: 1/15/91 5:16:03 PM %%VMusage: 1024 45747 @@ -345,87 +377,113 @@ 1991 by David Rakowski. Alle Rechte Vorbehalten.) readonly def end readonly def /FontName /Showboat def ---stdin-- +--stdin-- + - -Using this information, a possible name might be: - - --type1-Showboat-medium-r-normal-decorative-0-0-0-0-p-0-iso8859-1 - - -The components of our name are: - - - -Foundry - -Lets just name all the new fonts type1. - - - -Family - -The name of the font. - - - -Weight - -Normal, bold, medium, semibold, etc. From the -strings1 output -above, it appears that this font has a weight of -medium. - - - -Slant - -roman, italic, oblique, -etc. Since the ItalicAngle is zero, -roman will be used. - - - -Width - -Normal, wide, condensed, extended, etc. Until it can be examined, -the assumption will be normal. - - - -Additional style - -Usually omitted, but this will indicate that -the font contains decorative capital letters. - - - -Spacing - -proportional or monospaced. Proportional -is used since isFixedPitch is false. - - - - - -All of these names are arbitrary, but one should strive to be -compatible with the existing conventions. A font is referenced by -name with possible wild cards by an X11 program, so the name chosen -should make some sense. One might begin by simply using - -…-normal-r-normal-…-p-… - -as the name, and then use -xfontsel1 to examine it -and adjust the name based on the appearance of the font. -So, to complete our example: - + Using this information, a possible name might be: + -Make the font accessible to X11 + +-type1-Showboat-medium-r-normal-decorative-0-0-0-0-p-0-iso8859-1 + + + + The components of our name are: + + + + Foundry + + + Lets just name all the new fonts + type1. + + + + + Family + + + The name of the font. + + + + + Weight + + + Normal, bold, medium, semibold, etc. From the + strings1 + output above, it appears that this font has a weight of + medium. + + + + + Slant + + + roman, italic, oblique, etc. Since the + ItalicAngle is zero, + roman will be used. + + + + + Width + + + Normal, wide, condensed, extended, etc. Until it can + be examined, the assumption will be + normal. + + + + + Additional style + + + Usually omitted, but this will indicate that the font + contains decorative capital letters. + + + + + Spacing + + + proportional or monospaced. + Proportional is used since + isFixedPitch is false. + + + + + All of these names are arbitrary, but one should strive to + be compatible with the existing conventions. A font is + referenced by name with possible wild cards by an X11 program, + so the name chosen should make some sense. One might begin by + simply using + + + +…-normal-r-normal-…-p-… + + + + as the name, and then use + xfontsel1 to + examine it and adjust the name based on the appearance of the + font. + + So, to complete our example: + + + +Make the font accessible to X11 bash$ cd /usr/X11R6/lib/X11/fonts/Type1 bash$ ln -s /usr/local/share/fonts/type1/showboat.pfb . @@ -449,29 +507,29 @@ bash$ xset fp rehash Examine the new font -bash$ xfontsel -pattern -type1-* +bash$ xfontsel -pattern -type1-* + - -References: -&man.xfontsel.1;, -&man.xset.1;, -The X Windows System in a Nutshell, O'Reilly & Associates. - - - - -Using type 1 fonts with Ghostscript - -Ghostscript references a font via its Fontmap -file. This must be modified in a similar way to the X11 -fonts.dir file. Ghostscript can use either the -.pfa or the .pfb format -fonts. Using the font from the previous example, here is how to use -it with Ghostscript: - + + References: &man.xfontsel.1;, &man.xset.1;, The X + Windows System in a Nutshell, O'Reilly & + Associates. + + + + Using type 1 fonts with Ghostscript + + Ghostscript references a font via its Fontmap + file. This must be modified in a similar way to the X11 + fonts.dir file. Ghostscript can use either + the .pfa or the .pfb + format fonts. Using the font from the previous example, here is + how to use it with Ghostscript: + -Put the font in Ghostscript's font directory + +Put the font in Ghostscript's font directory bash$ cd /usr/local/share/ghostscript/fonts bash$ ln -s /usr/local/share/fonts/type1/showboat.pfb . @@ -497,46 +555,51 @@ >>showpage, press <return> to continue<< >>showpage, press <return> to continue<< >>showpage, press <return> to continue<< -GS>quit +GS>quit + - -References: fonts.txt in the Ghostscript -4.01 distribution - - - - -Using type 1 fonts with Groff - -Now that the new font can be used by both X11 and Ghostscript, -how can one use the new font with groff? First of all, since we are -dealing with type 1 postscript fonts, the groff device that is -applicable is the ps device. A font file must be -created for each font that groff can use. A groff font name is just -a file in /usr/share/groff_font/devps. With our -example, the font file could be -/usr/share/groff_font/devps/SHOWBOAT. The file -must be created using tools provided by groff. - -The first tool is afmtodit. This is not normally -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: - + + References: fonts.txt in the + Ghostscript 4.01 distribution + + + + Using type 1 fonts with Groff + + Now that the new font can be used by both X11 and + Ghostscript, how can one use the new font with groff? First of + all, since we are dealing with type 1 postscript fonts, the + groff device that is applicable is the ps + device. A font file must be created for each font that groff + can use. A groff font name is just a file in + /usr/share/groff_font/devps. With our + example, the font file could be + /usr/share/groff_font/devps/SHOWBOAT. The + file must be created using tools provided by groff. + + The first tool is afmtodit. This is not + normally 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: + -bash$ cp /usr/src/gnu/usr.bin/groff/afmtodit/afmtodit.pl /tmp + +bash$ cp /usr/src/gnu/usr.bin/groff/afmtodit/afmtodit.pl /tmp bash$ ex /tmp/afmtodit.pl :1c #!/usr/bin/perl -P- . -:wq +:wq + - -This tool will create the groff font file from the metrics file -(.afm suffix.) Continuing with our -example: - + + This tool will create the groff font file from the metrics + file (.afm suffix.) Continuing with our + example: + -Many .afm files are in Mac format&hellip ^M delimited lines + +Many .afm files are in Mac format&hellip ^M delimited lines We need to convert them to unix style ^J delimited lines bash$ cd /tmp bash$ cat /usr/local/share/fonts/type1/showboat.afm | @@ -544,33 +607,38 @@ Now create the groff font file bash$ cd /usr/share/groff_font/devps -bash$ /tmp/afmtodit.pl -d DESC -e text.enc /tmp/showboat.afm generate/textmap SHOWBOAT +bash$ /tmp/afmtodit.pl -d DESC -e text.enc /tmp/showboat.afm generate/textmap SHOWBOAT + - -The font can now be referenced with the name SHOWBOAT. - -If ghostscript is used to drive the printers on the system, -then nothing more needs to be done. However, if true postscript -printers are used, then the font must be down loaded to the printer -in order for the font to be used (unless the printer happens to have -the showboat font built in or on an accessible font disk.) The final -step is to create a down loadable font. The pfbtops tool -is used to create the .pfa format of the font, -and the download file is modified to reference the new -font. The download file must reference the internal -name of the font. This can easily be determined from the groff font -file as illustrated: - + + The font can now be referenced with the name + SHOWBOAT. + + If ghostscript is used to drive the printers on the system, + then nothing more needs to be done. However, if true postscript + printers are used, then the font must be down loaded to the + printer in order for the font to be used (unless the printer + happens to have the showboat font built in or on an accessible + font disk.) The final step is to create a down loadable font. + The pfbtops tool is used to create the + .pfa format of the font, and the + download file is modified to reference the new + font. The download file must reference the + internal name of the font. This can easily be determined from + the groff font file as illustrated: + -Create the .pfa font file + +Create the .pfa font file bash$ pfbtops /usr/local/share/fonts/type1/showboat.pfb >showboat.pfa - -Of course, if the .pfa file is already -available, just use a symbolic link to reference it. - + + Of course, if the .pfa file is already + available, just use a symbolic link to reference it. + -Get the internal font name + +Get the internal font name bash$ fgrep internalname SHOWBOAT internalname Showboat @@ -579,13 +647,15 @@ :$a Showboat showboat.pfa . -:wq +:wq + - -To test the font: - + + To test the font: + -bash$ cd /tmp + +bash$ cd /tmp bash$ cat >example.t <<EOF .sp 5 .ps 16 @@ -618,16 +688,14 @@ bash$ ghostview example.ps To print it -bash$ lpr -Ppostscript example.ps +bash$ lpr -Ppostscript example.ps + - -References: -/usr/src/gnu/usr.bin/groff/afmtodit/afmtodit.man, -&man.groff.font.5;, -&man.groff.char.7;, -&man.pfbtops.1;. - - + + References: + /usr/src/gnu/usr.bin/groff/afmtodit/afmtodit.man, + &man.groff.font.5;, &man.groff.char.7;, &man.pfbtops.1;. + Converting TrueType fonts to a groff/postscript format for @@ -635,23 +703,23 @@ <para>This potentially requires a bit of work, simply because it depends on some utilities that are not installed as part of the - base system. They are:</para> + base system. They are:</para> <variablelist> <varlistentry> <term><command>ttf2pf</command></term> <listitem> - <para>TrueType to postscript convertsion utilities. This + <para>TrueType to postscript convertsion utilities. This allows conversion of a TrueType font to an ascii font metric (<filename>.afm</filename>) file.</para> - + <para>Currently available at <ulink - url="http://sunsite.icm.edu.pl/pub/GUST/contrib/BachoTeX98/ttf2pf/">http://sunsite.icm.edu.pl/pub/GUST/contrib/BachoTeX98/ttf2pf</ulink>. + url="http://sunsite.icm.edu.pl/pub/GUST/contrib/BachoTeX98/ttf2pf/">http://sunsite.icm.edu.pl/pub/GUST/contrib/BachoTeX98/ttf2pf</ulink>. Note: These files are postscript programs and must be downloaded to disk by holding down the - <keycap>Shift</keycap> key when clicking on the - link. Otherwise, your browser may try to launch + <keycap>Shift</keycap> key when clicking on the link. + Otherwise, your browser may try to launch <application>ghostview</application> to view them.</para> <para>The files of interest are:</para> @@ -673,8 +741,8 @@ <para>The funny upper/lower case is due to their being intended also for DOS shells. <filename>ttf2pf.ps</filename> makes use of the others as - upper case, so any renaming must be consistent with - this. (Actually, <filename>GS_TTF.PS</filename> and + upper case, so any renaming must be consistent with this. + (Actually, <filename>GS_TTF.PS</filename> and <filename>PFS2AFM.PS</filename> are supposedly part of the ghostscript distribution, but it's just as easy to use these as an isolated utility. FreeBSD doesn't seem to @@ -689,7 +757,7 @@ <listitem> <para>Creates font files for use with groff from ascii font - metrics file. This usually resides in the directory, + metrics file. This usually resides in the directory, <filename>/usr/src/contrib/groff/afmtodit</filename>, and requires some work to get going.</para> @@ -700,12 +768,12 @@ location.</para> </note> - <para>In the work area, you'll need to make the - utility. Just type:</para> + <para>In the work area, you'll need to make the utility. + Just type:</para> - <screen> +<screen> <prompt>#</prompt> <userinput>make -f Makefile.sub afmtodit</userinput> - </screen> +</screen> <para>You may also need to copy <filename>/usr/contrib/groff/devps/generate/textmap</filename> @@ -724,9 +792,9 @@ <para>Create the <filename>.afm</filename> file by typing:</para> - <screen> +<screen> <prompt>%</prompt> <userinput>gs <optional>-dNODISPLAY</optional> <optional>-q</optional> -- ttf2pf.ps <replaceable>TTF_name</replaceable> <optional><replaceable>PS_font_name</replaceable> <optional><replaceable>AFM_name</replaceable></optional></optional></userinput> - </screen> +</screen> <para>Where, <replaceable>TTF_name</replaceable> is your TrueType font file, <replaceable>PS_font_name</replaceable> @@ -739,32 +807,32 @@ <para>This also produces a <filename>.pfa</filename> file, the ascii postscript font metrics file - (<filename>.pfb</filename> is for the binrary form). This + (<filename>.pfb</filename> is for the binrary form). This won't be needed, but could (I think) be useful for a fontserver.</para> <para>For example, to convert the 30f9 Barcode font using the default file names, use the following command:</para> - <screen> +<screen> <prompt>%</prompt> <userinput>gs -dNODISPLAY -- ttf2pf.ps 3of9.ttf</userinput> Aladdin Ghostscript 5.10 (1997-11-23) Copyright (C) 1997 Aladdin Enterprises, Menlo Park, CA. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Converting 3of9.ttf to 3of9.pfa and 3of9.afm. - </screen> +</screen> <para>If you want the converted fonts to be stored in <filename>A.pfa</filename> and <filename>B.afm</filename>, then use this command:</para> - <screen> +<screen> <prompt>%</prompt> <userinput>gs -dNODISPLAY -- ttf2pf.ps 3of9.ttf A B</userinput> Aladdin Ghostscript 5.10 (1997-11-23) Copyright (C) 1997 Aladdin Enterprises, Menlo Park, CA. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Converting 3of9.ttf to A.pfa and B.afm. - </screen> +</screen> </listitem> <listitem> @@ -772,34 +840,33 @@ <para>Change directories to <filename>/usr/share/groff_font/devps</filename> so as to - make the following command easier to execute. You'll - probably need root priviledges for this. (Or, if you're + make the following command easier to execute. You'll + probably need root priviledges for this. (Or, if you're paranoid about working there, make sure you reference the files <filename>DESC</filename>, <filename>text.enc</filename> and <filename>generate/textmap</filename> as being in this directory.)</para> - <screen> +<screen> <prompt>%</prompt> <userinput>afmtodit -d DESC -e text.enc file.afm \ generate/textmap <replaceable>PS_font_name</replaceable></userinput> - </screen> +</screen> <para>Where, <filename>file.afm</filename> is the <replaceable>AFM_name</replaceable> created by <command>ttf2pf.ps</command> above, and <replaceable>PS_font_name</replaceable> is the font name used from that command, as well as the name that - &man.groff.1; - will use for references to this font. For example, assuming - you used the first <command>tiff2pf.ps</command> command - above, then the 3of9 Barcode font can be created using the - command:</para> + &man.groff.1; will use for references to this font. For + example, assuming you used the first + <command>tiff2pf.ps</command> command above, then the 3of9 + Barcode font can be created using the command:</para> - <screen> +<screen> <prompt>%</prompt> <userinput>afmtodit -d DESC -e text.enc 3of9.afm \ generate/textmap 3of9</userinput> - </screen> +</screen> <para>Ensure that the resulting <replaceable>PS_font_name</replaceable> file (e.g., @@ -814,137 +881,146 @@ <filename>.afm</filename> file prior to running <command>afmtodit</command>. This name must also match the one used in the Fontmap file if you wish to pipe - &man.groff.1; into - &man.gs.1;.</para> + &man.groff.1; into &man.gs.1;.</para> </listitem> </orderedlist> </sect1> -<sect1> -<title>Can TrueType fonts be used with other programs? + + Can TrueType fonts be used with other programs? + + The TrueType font format is used by Windows, Windows 95, and + Mac's. It is quite popular and there are a great number of + fonts available in this format. + + Unfortunately, there are few applications that I am aware of + that can use this format: Ghostscript and Povray come to mind. + Ghostscript's support, according to the documentation, is + rudimentary and the results are likely to be inferior to type 1 + fonts. Povray version 3 also has the ability to use TrueType + fonts, but I rather doubt many people will be creating documents + as a series of raytraced pages :-). + + This rather dismal situation may soon change. The FreeType Project is + currently developing a useful set of FreeType tools: + + + + The xfsft font server for X11 can + serve TrueType fonts in addition to regular fonts. Though + currently in beta, it is said to be quite useable. See + Juliusz + Chroboczek's page for further information. + Porting instructions for FreeBSD can be found at Stephen + Montgomery's software page. + + + + xfstt is another font server for X11, + available under + ftp://sunsite.unc.edu/pub/Linux/X11/fonts. + + + + A program called ttf2bdf can produce + BDF files suitable for use in an X environment from TrueType + files. Linux binaries are said to be available from ftp://crl.nmsu.edu/CLR/multiling/General/. + + + + For people requiring the use of Asian TrueType fonts, + the XTT font server may be worth a look. + Information about XTT can be found at + URL: http://hawk.ise.chuo-u.ac.jp/student/person/tshiozak/study/freebsd-at-random/x-tt/index-en.html. + + + + and others … + + + + The FreeType Projects + page is a good starting point for information on + these and other free TrueType projects. + + + + Where can additional fonts be obtained? + + Many fonts are available on the Internet. They are either + entirely free, or are share-ware. In addition, there are many + inexpensive CDROMs available that contain many fonts. Some + Internet locations (as of August 1996) are: + + + + ftp://ftp.winsite.com + (Formerly CICA) + + + + http://www.simtel.net/simcgi-bin/dosfind.cgi + + + + ftp://ftp.coast.net/ + + + + http://af-pc-plloyd.ecel.uwa.edu.au/fonts/index.html + + + + http://www.esselte.com/letraset/index.html + + + + http://www.inil.com/users/elfring/esf.htm + + + + + + Additional questions + + + + What use are the .pfm files? + + + + Can one generate the .afm file from + a .pfa or + .pfb? + -The TrueType font format is used by Windows, Windows 95, and -Mac's. It is quite popular and there are a great number of -fonts available in this format. - -Unfortunately, there are few applications that I am aware of -that can use this format: Ghostscript and Povray come to mind. -Ghostscript's support, according to the documentation, is rudimentary -and the results are likely to be inferior to type 1 fonts. -Povray version 3 also has the ability to use TrueType fonts, but -I rather doubt many people will be creating documents as a series of -raytraced pages :-). - -This rather dismal situation may soon change. -The FreeType Project -is currently developing a useful set of FreeType tools: - - - -The xfsft font server for X11 can serve -TrueType fonts in addition to regular fonts. Though currently in -beta, it is said to be quite useable. See Juliusz -Chroboczek's page for further information. Porting instructions -for FreeBSD can be found at Stephen Montgomery's -software page. - - - -xfstt is another font -server for X11, available under -ftp://sunsite.unc.edu/pub/Linux/X11/fonts. - - -A program called ttf2bdf can produce -BDF files suitable for use in an X environment from TrueType files. Linux -binaries are said to be available from ftp://crl.nmsu.edu/CLR/multiling/General/. - - - - -For people requiring the use of Asian TrueType fonts, the -XTT font server may be worth a look. Information about -XTT can be found at URL: http://hawk.ise.chuo-u.ac.jp/student/person/tshiozak/study/freebsd-at-random/x-tt/index-en.html. - - - -and others … - - - -The -FreeType Projects page - is a good starting point for information on these and other -free TrueType projects. - - - - -Where can additional fonts be obtained? - -Many fonts are available on the Internet. They are either -entirely free, or are share-ware. In addition, there are many -inexpensive CDROMs available that contain many fonts. Some Internet -locations (as of August 1996) are: - - - -ftp://ftp.winsite.com (Formerly -CICA) - -http://www.simtel.net/simcgi-bin/dosfind.cgi - -ftp://ftp.coast.net/ - -http://af-pc-plloyd.ecel.uwa.edu.au/fonts/index.html - -http://www.esselte.com/letraset/index.html - -http://www.inil.com/users/elfring/esf.htm - - - - - - -Additional questions - - - - -What use are the .pfm files? - - - -Can one generate the .afm file from a .pfa or .pfb? - - - -How to generate the groff character mapping files for postscript fonts -with non-standard character names? - - - -Can xditview and devX?? devices be setup to access all the new fonts? - - - -It would be good to have examples of using TrueType fonts with povray and -ghostscript. - - - - - + + How to generate the groff character mapping files for + postscript fonts with non-standard character names? + + + + Can xditview and devX?? devices be setup to access all + the new fonts? + + + + It would be good to have examples of using TrueType + fonts with povray and ghostscript. + + +
>Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message