home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!paladin.american.edu!howland.reston.ans.net!sol.ctr.columbia.edu!ira.uka.de!sbusol.rz.uni-sb.de!coli.uni-sb.de!coli.uni-sb.de!usenet
- From: ulma@coli.uni-sb.de (Ulrich Mayring)
- Newsgroups: comp.os.ms-windows.setup
- Subject: Re: TrueTypeFont-Bug!
- Date: 8 Jan 1993 12:21:50 +0100
- Organization: Computational Linguistics Dept., U Saarbruecken
- Lines: 27
- Message-ID: <1ijo4eINN4ln@coli-gate.coli.uni-sb.de>
- References: <1ce6da9b@p7.f7521.n241.z2.fidonet.org> <1993Jan8.001646.3334@cbfsb.cb.att.com>
- NNTP-Posting-Host: coli-gate.coli.uni-sb.de
-
- rnichols@cbnewsg.cb.att.com (robert.k.nichols) writes:
-
- >In article <1ce6da9b@p7.f7521.n241.z2.fidonet.org> in comp.os.ms-windows.setup
- > Kai_Rohrbacher@p7.badendoor.fido.de (Kai Rohrbacher) writes:
- >>
- >> I discovered a very annoying bug with Windows' 3.1 TrueTypeFonts
- >> (TTF's) and I can't imagine being the first one:
- >> When using complex TTF's (especially the three ornamented fonts
- >> "CarrickCaps", "KonanurKaps" and "Starburst"; others too), the chars
- >> display well at the screen, but get printed out as empty, rectangular
- >> boxes!
- >...
- >> I suspect that by default, Windows doesn't set aside enough RAM for
- >> the font-handling; does anybody know how to fix that?
-
- >The problem doesn't seem to be just with Windows drivers. I ran into
- >this exact problem with some of the fonts you mentioned and various
- >others. I tried to use Atech's Alltype conversion utility to convert
- >the offending fonts to type-1 PostScript, but it died with a general
- >protection fault on every one!
-
- Yes, I had the same problem. Interesting enough: Some letters print fine, others
- don't. Presumably the more complex ones. As always: Use REAL fonts, if you can't
- afford it -> suffer.
-
- Ulrich.
-
-