[links-list] Re: font problem and fix
sven at convergence.de
Sat Nov 9 04:56:48 PST 2002
Petr Baudis <pasky at ucw.cz> writes:
> > svgalib-only machines
> > framebuffer-only machines
> These two can use freetype2 just fine - freetype2 isn't bound to X
> in any way. Ie. my graphviz uses freetype2 for generating pngs and
> so on.
you are perfectly right here. FreeType2 is on no way X11-dependant.
> > OS/2 PMShell
AFAIK FreeType2 works on OS/2 as well.
> I'm not saying "remove the fonts you're including now". I think it
> would be probably more feasible to provide the internal fonts as a
> fallback and use something else if possible (and if user doesn't say
> "use internal fonts"), as the "something else" will most probably
> have much more complete fonts available. You should only gain here -
> your fonts support will improve a lot, users won't loose anything
> except bandwidth (since you could make the internal fonts an
> external packages, thus people with thin line (modem people) will be
> able to download only the core and use the fonts they already
> have).. Ok, you will maybe loose antialiasing (it's probably not
> being done at run time, dunno). But again, users who will want to
> have antialiasing will just choose internal fonts, while those who
> rather care about complete fonts and/or size of the tarball they are
> going to download will choose the external fonts support.
I'd even go so far to say drop the internal fonts. The rendering
quality you get from FreeType2 is in my opinion much superior to the
internal font rendering.
Unsubscribe: send email to links-list-request at linuxfromscratch.org
and put unsubscribe in the subject header of the message
More information about the links-list