From: Florian Boor <florian.boor@kernelconcepts.de>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: [RFC] gtk+ and fonts
Date: Mon, 07 Dec 2009 16:41:30 +0100 [thread overview]
Message-ID: <4B1D222A.90105@kernelconcepts.de> (raw)
Hi,
our current GTK+ packages recommend a single Truetype font (ttf-dejavu-sans).
This might pull in a quite large font collection that might be different from
what the user wants. For a Japanese image e.g. you might not want these at all
or you might just want different fonts (like the Android ones).
I would be fine removing this RRECOMMENDS entry without any replacement. Another
option would be to create a virtual provider for basic ttf fonts and define a
matching run time dependency.
What do you think?
Greetings
Florian
--
The dream of yesterday Florian Boor
is the hope of today Tel: +49 271-771091-15
and the reality of tomorrow. Fax: +49 271-771091-19
[Robert Hutchings Goddard, 1904] florian.boor@kernelconcepts.de
http://www.kernelconcepts.de/en
next reply other threads:[~2009-12-07 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 15:41 Florian Boor [this message]
2009-12-07 16:33 ` [RFC] gtk+ and fonts Koen Kooi
2009-12-07 16:42 ` Phil Blundell
2009-12-07 17:05 ` Florian Boor
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=4B1D222A.90105@kernelconcepts.de \
--to=florian.boor@kernelconcepts.de \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.