Closed Bug 132367 Opened 23 years ago Closed 23 years ago

freetype support fails to recognize font families

Categories

(Core Graveyard :: GFX, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 130661

People

(Reporter: cloos, Assigned: bstell)

Details

With freetype support on, and a freetype-rendered font selected, you get only the glyphs from a single font file; stylizations such as bold an italic are lost, and often an italic or bold fint is used as the base font. Inlcude the directory .../jdk1.3/jre/lib/fonts/ or equivilent and choose Lucida Sans Typewriter for the mono font; only Lucida Sans Typewriter Bold will be used. Include a directory containing the MS fonts and choose Georgia as the serif font; only GEORGIA.TTF will be loaded, the bold, italic and bold italic files are ignored. For some fonts this shows up in the font list in the prefs dialog. Bold, italic, etc versions are included in the menu list. For others the menu only lists the family, but still only picks one font file to load. (tested w/ suse's rpms and my compile of freetype-2.0.9. The rpms use this configure line: ./configure --enable-configure --disable-tests \ --disable-debug --enable-optimize="$RPM_OPT_FLAGS" \ --disable-dtd-debug --sysconfdir=/etc \ --disable-logging --enable-extensions \ --with-default-mozilla-five-home=/opt/mozilla \ --disable-short-wchar --prefix=/opt/mozilla \ --enable-crypto --enable-mathml \ --enable-xinerama --enable-reorder --enable-strip \ --enable-xft )
.
Assignee: asa → bstell
Component: Browser-General → Compositor
this is the same as bug 130661 *** This bug has been marked as a duplicate of 130661 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.