Bug 4869 - Netscape doesn't use installed fonts + TrueDoc doesn't work
Summary: Netscape doesn't use installed fonts + TrueDoc doesn't work
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: netscape
Version: 6.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
URL: http://www.bitstream.com/webfont/gall...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-09-02 23:31 UTC by murray
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 1999-09-03 14:48:59 UTC
Embargoed:


Attachments (Terms of Use)

Description murray 1999-09-02 23:31:55 UTC
This is SUPPOSED to demonstrate the dynamic downloadable
fonts in Netscape Communicator using the TrueDoc
technology.  (The initial Netscape page on load-up mentions
"TrueDoc" as one of its licensed technologies.)  On an older
Red Hat 5.2 system I have this stuff actually works.  (If
you go to the page, you should see some fonts appear as
pieces of candy and others to be obviously non-standard
fonts.)

I've reproduced this problem on five very different
computers running Red Hat 6.0.

I've also downloaded the most recent version of Communicator
directly from Netscape, installed it and still the same
problem happens.

What's worse, this is only part of the problem.  Netscape
will not display standard installed X-Fonts on the system.
Try running the Gnome font selector, pick the font of your
choice, make a simple web page that selects that font.  It
won't display.

I don't know for a fact that other non-RH distributions have
the same problem or not (maybe it's a bug in newer XF86!)
Does anybody have any info?

Comment 1 Bill Nottingham 1999-09-03 14:48:59 UTC
TrueDoc support is not available in the glibc build of communicator.
If you'd like to see this available, talk to Bitstream about
releasing a glibc version of their library for Netscape to
ship...


Note You need to log in before you can comment on or make changes to this bug.