From: foser <foser@gentoo.org>
To: gentoo-desktop-research@gentoo.org
Subject: Re: [gentoo-desktop-research] One research problem we could research
Date: Thu, 09 Oct 2003 23:29:27 +0200 [thread overview]
Message-ID: <1065734966.3824.78.camel@rivendell> (raw)
In-Reply-To: <200310092000.09203.pauldv@gentoo.org>
On Thu, 2003-10-09 at 20:00, Paul de Vrieze wrote:
> Well, actually the ttf fonts are the best looking on my system (yes and non-AA
> in the sizes 8-17 as I don't like fuzzy fonts). I agree that bitmap fonts
> give better results, but only if they are not scaled. What also goes wrong
> sometimes is ps fonts.
You shouldn't scale bitmaps.. i mean _quality_ bitmaps, where there's
proper bitmaps for every size.
> They have to, if say, the desktop-guide would give that information it would
> save them (and me, as my girlfriend wants to be able to read and write
> Chinese (simplified)) a lot of headaches.
Nah, much to dense for a desktop-guide. An extra doc referenced ok i can
see that, but this should be optional info. For a normal user the
defaults should do.
Documentation is only as good as it is thin, see the current install
docs for how it gets out of hand. In my opinion there's way too much
unneeded cruft in there, all these little notes and subsections make it
less and less usable. We should beware of that phenomenon in another
important user guide.
> And the same fonts are chosen for the same name. fontconfig plays it's own
> little role, just as the core font protocol does. And pango and qt as
> wrappers around the font system.
Only fontconfig and freetype influence font rendering. And fontconfig
probably plays the major role in seting things up.
- foser
--
gentoo-desktop-research@gentoo.org mailing list
next prev parent reply other threads:[~2003-10-09 21:31 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 9:21 [gentoo-desktop-research] One research problem we could research Paul de Vrieze
2003-10-09 13:09 ` foser
2003-10-09 13:22 ` Paul de Vrieze
2003-10-09 13:43 ` foser
2003-10-09 14:09 ` dams
2003-10-09 14:19 ` Paul de Vrieze
2003-10-09 14:31 ` foser
2003-10-09 14:46 ` Paul de Vrieze
2003-10-09 15:37 ` foser
2003-10-09 18:00 ` Paul de Vrieze
2003-10-09 21:29 ` foser [this message]
2003-10-10 7:53 ` Paul de Vrieze
2003-10-10 9:28 ` dams
2003-10-09 14:46 ` dams
2003-10-09 15:49 ` foser
2003-10-09 14:09 ` Paul de Vrieze
2003-10-09 14:14 ` Paul de Vrieze
2003-10-09 14:33 ` foser
2003-10-09 18:00 ` Paul de Vrieze
2003-10-09 17:21 ` Tiemo Kieft
2003-10-09 21:33 ` foser
2003-10-09 21:19 ` Tiemo Kieft
2003-10-10 9:31 ` dams
2003-10-10 9:36 ` Paul de Vrieze
2003-10-10 9:46 ` [gentoo-desktop-research] Fonts rendering and configuration Was: " dams
2003-10-10 10:06 ` Paul de Vrieze
2003-10-10 10:23 ` dams
2003-10-20 3:52 ` [gentoo-desktop-research] Dead? Gerald J. Normandin Jr.
2003-10-20 5:14 ` Tiemo Kieft
2003-10-20 10:47 ` [gentoo-desktop-research] desktop problems dams
2003-10-20 19:21 ` Paul de Vrieze
2003-10-21 9:37 ` dams
2003-10-21 9:42 ` Paul de Vrieze
2003-10-21 9:46 ` dams
2003-10-21 9:59 ` Paul de Vrieze
2003-10-21 10:07 ` dams
2003-10-21 14:59 ` Luca Barbato
2003-10-21 15:45 ` Tiemo Kieft
2003-10-26 12:53 ` [gentoo-desktop-research] IMPORTANT definitions draft dams
2003-10-26 15:30 ` Gerald J. Normandin Jr.
2003-10-26 15:53 ` Luca Barbato
2003-10-20 10:38 ` [gentoo-desktop-research] Dead? dams
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=1065734966.3824.78.camel@rivendell \
--to=foser@gentoo.org \
--cc=gentoo-desktop-research@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