Closed
Bug 190347
Opened 22 years ago
Closed 13 years ago
Let FreeType2 handle Type1/etc rendering too.
Categories
(Core :: Graphics, enhancement)
Tracking
()
RESOLVED
FIXED
People
(Reporter: adam, Unassigned)
References
Details
Mozilla has the neat innate ability to use the FreeType2 library to render
anti-aliased truetype fonts. You point the config file at the directory in
which you keep your .tff fonts, and the world is good.
FreeType2 also nicely renders and optionally anti-aliases Type1 (as typically
used by X servers for scalable fonts) and some other font types. But just
dropping Type1 fonts and other random font types into the same directory as the
.tff fonts doesn't work; the fonts are skipped with an error when mozilla starts
up and scans the directory.
It would be nice if I could use my usual X11 Type1 fonts in the same way as I
use my truetype fonts. FreeType claims to offer a fairly homogenous interface
to accessing various font types, so I imagine that Mozilla's code is already
close to having this just work.
Comment 1•22 years ago
|
||
Yeah, it might be pretty simple. I'll look into it. Do you have some decent
sample fonts to play with?
Blocks: xft_tracking
Reporter | ||
Comment 2•22 years ago
|
||
The scaleable fonts I have are the usual ones that come with
XFree86 4, plus the sharefonts package found on gimp.org that
you're probably already familiar with.
Comment 3•17 years ago
|
||
Does it work in a recent trunk build?
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/
Assignee | ||
Updated•16 years ago
|
Product: Core → Core Graveyard
Comment 4•13 years ago
|
||
This might still be a valid enhancement request; redirecting to Core:Graphics.
Assignee: blizzard → nobody
Component: GFX: Gtk → Graphics
Product: Core Graveyard → Core
QA Contact: ian → thebes
Updated•13 years ago
|
Status: NEW → UNCONFIRMED
Ever confirmed: false
Comment 5•13 years ago
|
||
We use Freetype for all text rendering on Linux now.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•