On Wednesday 12 July 2006 18:47, Donnie Berkholz wrote:
> Richard Fish wrote:
> > Just make sure that every directory produced by this command has a
> > FontPath entry:
> > find /usr/share/fonts/* -type d
>
> I wouldn't worry too much about this anyhow, only really old apps use
> FontPath entries. Most new ones use fontconfig, which searches
> /usr/share/fonts/ recursively.

Although the fonts are there:
=========================================
$ find /usr/share/fonts/* -type d
/usr/share/fonts/100dpi
/usr/share/fonts/75dpi
/usr/share/fonts/TTF
/usr/share/fonts/Type1
/usr/share/fonts/artwiz-aleczapka-en
/usr/share/fonts/corefonts
/usr/share/fonts/cyrillic
/usr/share/fonts/default
/usr/share/fonts/default/ghostscript
/usr/share/fonts/encodings
/usr/share/fonts/encodings/large
/usr/share/fonts/freefont
/usr/share/fonts/local
/usr/share/fonts/misc
/usr/share/fonts/sharefonts
/usr/share/fonts/terminus
/usr/share/fonts/ttf-bitstream-vera
/usr/share/fonts/ukr
/usr/share/fonts/unifont
/usr/share/fonts/util
=========================================

I am also getting errors loading some of them:
=========================================
Could not init font path element /usr/share/fonts/default, removing from list!
Could not init font path element /usr/share/fonts/encodings, removing from 
list!
Could not init font path element /usr/share/fonts/local, removing from list!
(**) RADEON(0): RADEONSaveScreen(2)
(**) RADEON(0): RADEONSaveScreen(2)
Warning: FreeTypeRasteriseGlyph() returns an error,
        so the backend tries to set a white space.
Warning: FreeTypeRasteriseGlyph() returns an error,
        so the backend tries to set a white space.
Warning: FreeTypeRasteriseGlyph() returns an error,
        so the backend tries to set a white space.
FreeType: couldn't open face /usr/share/fonts/TTF/VeraIt.ttf: 1
FreeType: couldn't open face /usr/share/fonts/TTF/VeraIt.ttf: 1
Warning: FreeTypeRasteriseGlyph() returns an error,
        so the backend tries to set a white space.
=========================================

Any idea why - can I fix it?

-- 
Regards,
Mick

Attachment: pgpwTofwq5fuU.pgp
Description: PGP signature

Reply via email to