Re: [jessie] how to use fonts from cm-super-x11 in X?
Quoting D. R. Evans (doc.evans@gmail.com):
> David Wright wrote on 07/15/2015 09:43 PM:
>
> > They appear just fine here (jessie) so it's tricky to think of what's wrong.
> >
> > Do you have any other type1 fonts that work ok? If there's a mistake
>
> Yep.
>
> $ fc-list :spacing=mono
> includes, for example,
> /usr/share/fonts/X11/Type1/c0582bt_.pfb: Courier 10 Pitch:style=Italic
> /usr/share/fonts/X11/Type1/c0583bt_.pfb: Courier 10 Pitch:style=Bold
and so I can type uxterm -fn '-bitstream-courier 10 pitch-medium-i-normal--0-0-0-0-m-0-iso10646-1'
and get a useable (italic) xterm.
> > [...] appear in /var/log/Xorg.0.log ?
>
> yes:
>
> [ 26.650] (**) FontPath set to:
> /usr/share/fonts/X11/misc,
> /usr/share/fonts/X11/100dpi/:unscaled,
> /usr/share/fonts/X11/75dpi/:unscaled,
> /usr/share/fonts/X11/Type1,
> /usr/share/fonts/X11/100dpi,
> /usr/share/fonts/X11/75dpi,
> built-ins,
> /usr/share/fonts/X11/misc,
> /usr/share/fonts/X11/100dpi/:unscaled,
> /usr/share/fonts/X11/75dpi/:unscaled,
> /usr/share/fonts/X11/Type1,
> /usr/share/fonts/X11/100dpi,
> /usr/share/fonts/X11/75dpi,
> built-ins
> [
>
> I don't know why the list appears twice, but that shouldn't do any harm.
Might you perhaps get that if you had an xorg.conf which still has
Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/X11/misc:unscaled"
...
EndSection
in it? This should all be picked up automatically nowadays without any
such configuration.
> > Just out of interest, what do you intend using these fonts for?
>
> I wanted to see if any of them looked good in a particular xterm ncurses
> application. It's very hard to find a really good monospaced font in which all
> the characters look nice. I have always rather liked cmtt (in other
> applications), and wanted to try something like that.
Hm. What I see for -p- (proportional) fonts, eg
p052003l.pfb -urw-urw palladio l-regular-r-normal--0-0-0-0-p-0-iso8859-1
The output lines from .bashrc and the prompt are corrctly written. The
cursor is twice as far to the right as it should be. My typing is all
double-spaced. Bash-completion is single spaced. If I type abcde (and
it's reflected double-spaced) and press <tab> the abcde jump into
their correct positions, but the cursor stays where it is. Carry on
typing efgh and you can repeat this jumping.
What I see for most -m- and -c- fonts, eg
lmtt10.pfb -unregistered-Latin Modern Typewriter-medium-r-normal--0-0-0-0-c-0-iso8859-15
Everything is double-spaced. The exception is fonts like
c0419bt_.pfb -bitstream-courier 10 pitch-medium-r-normal--0-0-0-0-m-0-iso10646-1
and those you mentioned at the top, which work normally.
I took a look at some of the .afm files for these fonts. The files
have a couple of lines like
IsFixedPitch true
FontBBox -44 -299 664 858
near the beginning, and then the characters themselves are in lines like
C 39 ; WX 602 ; N quoteright ; B 215 317 396 579 ;
C 40 ; WX 602 ; N parenleft ; B 201 -196 401 597 ;
where those numbers at the end look suspiciously like individual
character bounding boxes.
Looking at the lmtt10 font (bad) I see FontBBox -451 -316 731 1016
(δX=1182) whereas c0419bt_ (good) has FontBBox -44 -299 664 858
(δX=708). And running a quick grep:
cd /usr/share/fonts/ ; grep -i fontbbox X11/Type1/*afm type1/gsfonts/*afm | sort | less
I don't think it's my imagination that the fonts which work have a
smaller δX in the bounding box than the ones that don't.
Cheers,
David.
Reply to: