Source string Read only

(itstool) path: listitem/para
119/1190
Context English State
-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 <literal>type1</literal>.
Family
The name of the font.
Weight
Normal, bold, medium, semibold, etc. From the <citerefentry><refentrytitle>strings</refentrytitle><manvolnum>1</manvolnum></citerefentry> output above, it appears that this font has a weight of <emphasis>medium</emphasis>.
Slant
<emphasis remap="bf">r</emphasis>oman, <emphasis remap="bf">i</emphasis>talic, <emphasis remap="bf">o</emphasis>blique, etc. Since the <emphasis>ItalicAngle</emphasis> is zero, <emphasis>roman</emphasis> will be used.
Width
Normal, wide, condensed, extended, etc. Until it can be examined, the assumption will be <emphasis>normal</emphasis>.
Additional style
Usually omitted, but this will indicate that the font contains decorative capital letters.
Spacing
proportional or monospaced. <emphasis>Proportional</emphasis> is used since <emphasis>isFixedPitch</emphasis> is false.
…-normal-r-normal-…-p-…
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 <application>X11</application> program, so the name chosen should make some sense. One might begin by simply using <_:informalexample-1/> as the name, and then use <citerefentry vendor="xfree86"><refentrytitle>xfontsel</refentrytitle><manvolnum>1</manvolnum></citerefentry> to examine it and adjust the name based on the appearance of the font.
So, to complete our example:
<lineannotation>Make the font accessible to X11</lineannotation>
<prompt>%</prompt> <userinput>cd /usr/X11R6/lib/X11/fonts/Type1</userinput>
<prompt>%</prompt> <userinput>ln -s /usr/local/share/fonts/type1/showboat.pfb .</userinput>

<lineannotation>Edit fonts.dir and fonts.scale, adding the line describing the font
and incrementing the number of fonts which is found on the first line.</lineannotation>
<prompt>%</prompt> <userinput>ex fonts.dir
:1p
25
:1c
26
.
:$a
showboat.pfb -type1-showboat-medium-r-normal-decorative-0-0-0-0-p-0-iso8859-1
.
:wq</userinput>

<lineannotation>fonts.scale seems to be identical to fonts.dir…</lineannotation>
<prompt>%</prompt> <userinput>cp fonts.dir fonts.scale</userinput>

<lineannotation>Tell X11 that things have changed</lineannotation>
<prompt>%</prompt> <userinput>xset fp rehash</userinput>

<lineannotation>Examine the new font</lineannotation>
<prompt>%</prompt> <userinput>xfontsel -pattern -type1-*</userinput>
References: <citerefentry vendor="xfree86"><refentrytitle>xfontsel</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry vendor="xfree86"><refentrytitle>xset</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citetitle>The X Windows System in a Nutshell</citetitle>, <link xlink:href="http://www.ora.com/">O'Reilly &amp; Associates</link>.
Using Type 1 Fonts with Ghostscript
<application>Ghostscript</application> references a font via its <filename>Fontmap</filename>. This must be modified in a similar way to the <application>X11</application> <filename>fonts.dir</filename>. <application>Ghostscript</application> can use either the <filename>.pfa</filename> or the <filename>.pfb</filename> format fonts. Using the font from the previous example, here is how to use it with <application>Ghostscript</application>:
<lineannotation>Put the font in Ghostscript's font directory</lineannotation>
<prompt>%</prompt> <userinput>cd /usr/local/share/ghostscript/fonts</userinput>
<prompt>%</prompt> <userinput>ln -s /usr/local/share/fonts/type1/showboat.pfb .</userinput>

<lineannotation>Edit Fontmap so Ghostscript knows about the font</lineannotation>
<prompt>%</prompt> <userinput>cd /usr/local/share/ghostscript/4.01</userinput>
<prompt>%</prompt> <userinput>ex Fontmap
:$a
/Showboat (showboat.pfb) ; % From CICA /fonts/atm/showboat
.
:wq</userinput>

<lineannotation>Use Ghostscript to examine the font</lineannotation>
<prompt>%</prompt> <userinput>gs prfont.ps</userinput>
Aladdin Ghostscript 4.01 (1996-7-10)
Copyright (C) 1996 Aladdin Enterprises, Menlo Park, CA. All rights
reserved.
This software comes with NO WARRANTY: see the file PUBLIC for details.
Loading Times-Roman font from /usr/local/share/ghostscript/fonts/tir_____.pfb...
/1899520 581354 1300084 13826 0 done.
GS&gt;<userinput>Showboat DoFont</userinput>
Loading Showboat font from /usr/local/share/ghostscript/fonts/showboat.pfb...
1939688 565415 1300084 16901 0 done.
&gt;&gt;showpage, press &lt;return&gt; to continue&lt;&lt;
&gt;&gt;showpage, press &lt;return&gt; to continue&lt;&lt;
&gt;&gt;showpage, press &lt;return&gt; to continue&lt;&lt;
GS&gt;<userinput>quit</userinput>
References: <filename>fonts.txt</filename> in the <application>Ghostscript 4.01</application> distribution
Using Type 1 Fonts with Groff
Now that the new font can be used by both <application>X11</application> and <application>Ghostscript</application>, how can one use the new font with <application>groff</application>? First of all, since we are dealing with type 1 <trademark class="registered">PostScript</trademark> fonts, the <application>groff</application> device that is applicable is the <emphasis>ps</emphasis> device. A font file must be created for each font that <application>groff</application> can use. A <application>groff</application> font name is just a file in <filename>/usr/share/groff_font/devps</filename>. With our example, the font file could be <filename>/usr/share/groff_font/devps/SHOWBOAT</filename>. The file must be created using tools provided by <application>groff</application>.
The first tool is <command>afmtodit</command>. 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:
<prompt>%</prompt> <userinput>cp /usr/src/gnu/usr.bin/groff/afmtodit/afmtodit.pl /tmp</userinput>
<prompt>%</prompt> <userinput>ex /tmp/afmtodit.pl
:1c
#!/usr/bin/perl -P-
.
:wq</userinput>
This tool will create the <application>groff</application> font file from the metrics file (<filename>.afm</filename> suffix.) Continuing with our example:
<lineannotation>Many .afm files are in Mac format… ^M delimited lines
We need to convert them to <trademark class="registered">UNIX</trademark> style ^J delimited lines</lineannotation>
<prompt>%</prompt> <userinput>cd /tmp</userinput>
<prompt>%</prompt> <userinput>cat /usr/local/share/fonts/type1/showboat.afm |
tr '\015' '\012' &gt;showboat.afm</userinput>

<lineannotation>Now create the groff font file</lineannotation>
<prompt>%</prompt> <userinput>cd /usr/share/groff_font/devps</userinput>
<prompt>%</prompt> <userinput>/tmp/afmtodit.pl -d DESC -e text.enc /tmp/showboat.afm generate/textmap SHOWBOAT</userinput>

Loading…

No matching activity found.

Browse all component changes

Glossary

English English
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: listitem/para
Flags
read-only
Source string location
article.translate.xml:461
String age
a year ago
Source string age
a year ago
Translation file
articles/fonts.pot, string 81