#47 Terminus font not found on Fedora 16

[Richard Shaw]

When I try to run xqodem, xterm complains that the terminus-20 font isn't found. I changed the term-font environment variable in the xqodem script from:
font_xterm="terminus-20"
to a more old school method:
font_xterm="-*-terminus-*-*-normal-*-20-*-*-*-*-*-*-*"

and that fixed it for me. I'm not sure why this works on other systems (I'm assuming it works anyway).

[Autumn Lamonte]

Thank you for reporting this.

When I used "-*-terminus-*-*-normal-*-20-*-*-*-*-*-*-*" I got italic and a lot of missing CP437 glyphs (menu lines in phonebook for example).

However this looked the way "terminus-20" does on Debian:

font_xterm="-*-terminus-*-r-normal-*-20-*-*-*-*-*-iso10646-*"

How does this look for you? If it works, I'll commit the change to CVS.

[Richard Shaw]

I'm not sure why but that doesn't work for me...

$ xqodem
xterm: cannot load font '-*-terminus-*-r-normal-*-20-*-*-*-*-*-iso10646-*'
xterm: cannot load font '-*-terminus-*-r-normal-*-20-*-*-*-*-*-iso10646-*'

I wonder if this is a difference in the way the terminus fonts are packaged between distros?

I'd like to see if we can find something that works for both but an alternative approach may be to make it configurable from ./configure.

[Richard Shaw]

Interesting, it didn't work over ssh/x11 forwarding via cygwin, but now that I'm at home it worked fine.

[Autumn Lamonte]

[Autumn Lamonte]

I changed xqodem to look for both terminus and bolkov-vga (in that order) for uxterm, and resort to a hardcoded terminus if neither are found by xlsfonts. Other fonts can be added to the search list (FONTS="... ...") as we find more that include all the CP437 glyphs. If none of these are found, uxterm will complain and switch to "fixed".

How does that look for you?

[Richard Shaw]

Seemed to work fine!

Thanks,
Richard

[Autumn Lamonte]

Brought forward to the git repo.