The translation is temporarily closed for contributions due to maintenance, please come back later.

Source string Read only

(itstool) path: listitem/para
Context English State
The funny upper/lower case is due to their being intended also for DOS shells. <filename></filename> makes use of the others as 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 <application>Ghostscript</application> distribution, but it is just as easy to use these as an isolated utility. FreeBSD does not seem to include the latter.) You also may want to have these installed to <filename>/usr/local/share/groff_font/devps</filename>(?).
Creates font files for use with <application>groff</application> from ascii font metrics file. This usually resides in the directory, <filename>/usr/src/contrib/groff/afmtodit</filename>, and requires some work to get going.
If you are paranoid about working in the <filename>/usr/src</filename> tree, simply copy the contents of the above directory to a work location.
In the work area, you will need to make the utility. Just type:
<prompt>#</prompt> <userinput>make -f Makefile.sub afmtodit</userinput>
You may also need to copy <filename>/usr/contrib/groff/devps/generate/textmap</filename> to <filename>/usr/share/groff_font/devps/generate</filename> if it does not already exist.
Once all these utilities are in place, you are ready to commence:
Create <filename>.afm</filename> by typing:
<prompt>%</prompt> <userinput>gs -dNODISPLAY -q -- <replaceable>TTF_name</replaceable> <replaceable>PS_font_name</replaceable> <replaceable>AFM_name</replaceable></userinput>
Where, <replaceable>TTF_name</replaceable> is your TrueType font file, <replaceable>PS_font_name</replaceable> is the file name for <filename>.pfa</filename>, <replaceable>AFM_name</replaceable> is the name you wish for <filename>.afm</filename>. If you do not specify output file names for the <filename>.pfa</filename> or <filename>.afm</filename> files, then default names will be generated from the TrueType font file name.
This also produces a <filename>.pfa</filename>, the ascii PostScript font metrics file (<filename>.pfb</filename> is for the binary form). This will not be needed, but could (I think) be useful for a fontserver.
For example, to convert the 30f9 Barcode font using the default file names, use the following command:
<prompt>%</prompt> <userinput>gs -dNODISPLAY -- 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.
If you want the converted fonts to be stored in <filename>A.pfa</filename> and <filename>B.afm</filename>, then use this command:
<prompt>%</prompt> <userinput>gs -dNODISPLAY -- 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.
Create the <application>groff</application> PostScript file:
Change directories to <filename>/usr/share/groff_font/devps</filename> so as to make the following command easier to execute. You will probably need root privileges for this. (Or, if you are 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.)
<prompt>%</prompt> <userinput>afmtodit -d DESC -e text.enc file.afm generate/textmap <replaceable>PS_font_name</replaceable></userinput>
Where, <filename>file.afm</filename> is the <replaceable>AFM_name</replaceable> created by <command></command> above, and <replaceable>PS_font_name</replaceable> is the font name used from that command, as well as the name that <citerefentry><refentrytitle>groff</refentrytitle><manvolnum>1</manvolnum></citerefentry> will use for references to this font. For example, assuming you used the first <command></command> above, then the 3of9 Barcode font can be created using the command:
<prompt>%</prompt> <userinput>afmtodit -d DESC -e text.enc 3of9.afm generate/textmap 3of9</userinput>
Ensure that the resulting <replaceable>PS_font_name</replaceable> file (e.g., <filename>3of9</filename> in the example above) is located in the directory <filename>/usr/share/groff_font/devps</filename> by copying or moving it there.
Note that if <filename></filename> assigns a font name using the one it finds in the TrueType font file and you want to use a different name, you must edit the <filename>.afm</filename> prior to running <command>afmtodit</command>. This name must also match the one used in the Fontmap file if you wish to pipe <citerefentry><refentrytitle>groff</refentrytitle><manvolnum>1</manvolnum></citerefentry> into <citerefentry vendor="ports"><refentrytitle>gs</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
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: <application>Ghostscript</application> and <application>Povray</application> come to mind. <application>Ghostscript's</application> support, according to the documentation, is rudimentary and the results are likely to be inferior to type 1 fonts. <application>Povray</application> 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 <link xlink:href="">FreeType Project</link> is currently developing a useful set of FreeType tools:
The <command>xfsft</command> font server for <application>X11</application> can serve TrueType fonts in addition to regular fonts. Though currently in beta, it is said to be quite usable. See <link xlink:href="">Juliusz Chroboczek's page</link> for further information. Porting instructions for FreeBSD can be found at <link xlink:href="">Stephen Montgomery's software page</link>.


No matching activity found.

Browse all component changes

Source information

Source string comment
(itstool) path: listitem/para
Source string location
String age
a year ago
Source string age
a year ago
Translation file
articles/fonts.pot, string 126