From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] /usr/share/fonts/TTF doesn't exist
Date: Wed, 12 Jul 2006 20:15:23 +0100 [thread overview]
Message-ID: <200607122015.34078.michaelkintzios@gmail.com> (raw)
In-Reply-To: <44B535CD.3050000@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2149 bytes --]
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 #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-07-12 19:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 14:02 [gentoo-user] /usr/share/fonts/TTF doesn't exist Ozan Enginoglu
2006-07-12 17:14 ` Richard Fish
2006-07-12 17:47 ` Donnie Berkholz
2006-07-12 19:15 ` Mick [this message]
2006-07-12 19:59 ` Donnie Berkholz
2006-07-12 21:22 ` Mick
2006-07-12 22:52 ` Richard Fish
2006-07-13 22:22 ` Mick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200607122015.34078.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox