* Justin B Rye ([EMAIL PROTECTED]) wrote: > Package: gozer > Version: 0.7.nofont.1-1 > Severity: normal > > If I don't specify a font, gozer falls back on a compiled-in default > which is now very unlikely to be installed on the system: > > [EMAIL PROTECTED]:~$ gozer -t text file.png > gozer error: failed to load font helmetr/16 > > This is true even if I have downloaded that non-DFSG-compliant font > to /usr/local/share/fonts/truetype, because /etc/gozerrc resets the > fontpath to ignore everything outside /usr/share/fonts/truetype (the > directory itself, not its populated subdirectories) and the > nonexistent /usr/share/fonts/truetype/openoffice. Specifying an > appropriate fontpath on the commandline doesn't help - the packaged > rcfile takes priority.
Are you sure the package rcfile takes priority? Looking at the code this really doesn't seem to be the case. > You could reduce the number of hoops users have to jump through by > resetting the default to some font you then provide. (Or one in a > package you recommend; but full dependencies are usually frowned on, > since apps should in principle be able to use a remote fontserver.) -- Eric Dorland <[EMAIL PROTECTED]> ICQ: #61138586, Jabber: [EMAIL PROTECTED] 1024D/16D970C6 097C 4861 9934 27A0 8E1C 2B0A 61E9 8ECF 16D9 70C6 -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GCS d- s++: a-- C+++ UL+++ P++ L++ E++ W++ N+ o K- w+ O? M++ V-- PS+ PE Y+ PGP++ t++ 5++ X+ R tv++ b+++ DI+ D+ G e h! r- y+ ------END GEEK CODE BLOCK------
signature.asc
Description: Digital signature
