Return to BSD News archive
Xref: sserve comp.windows.x.i386unix:15572 comp.os.386bsd.questions:16809 comp.windows.x:76826 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!gmi!zombie.ncsc.mil!news.mathworks.com!udel!gatech!howland.reston.ans.net!math.ohio-state.edu!jussieu.fr!uvsq.fr!frmug.fr.net!eddy.frmug.fr.net!eddy.frmug.fr.net!not-for-mail From: zarkdav@eddy.frmug.fr.net (Benjamin Ryzman) Newsgroups: comp.windows.x.i386unix,comp.os.386bsd.questions,comp.windows.x Subject: Re: What's wrong with this font? Followup-To: comp.windows.x Date: 25 Feb 1995 11:57:07 +0100 Organization: Setec Astronomy Lines: 33 Message-ID: <3in2e3$an@eddy.frmug.fr.net> References: <D4F270.6s1@cogsci.ed.ac.uk> NNTP-Posting-Host: eddy.frmug.fr.net Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Richard Tobin ecrivait recemment: >I'm using XFree86 3.1.1 under FreeBSD 2.0. >The font -adobe-times-medium-r-*-*-16-*-*-*-*-*-*-* looks awful! So >does the 20 pixel version, but the others are ok. These fonts look >fine under X11R6 on my Sun. The fonts freely available with X11 are mostly bitmap fonts in size 8 10 12 14 18 24. Adobe Times is such a bitmap font, so when you request a 16pt Adobe Times, the server zoom the 14pt one to give it a 16pt size, resulting in an awful aliasing. On many Sun, the fonts are Type 1 PostScript programs and are fully scalable (they are mathematical and vectorial representations), so when you request a 16pt font, you get a very good representation of one (hinting problems aside). >About half the characters have problems like this. These fonts are >used by Mosaic, which consequently looks really bad. >Can anyone explain this? In order to correct your problem, you should buy Type 1 fonts (Adobe Type Basic would be a good package for this) and install them in your font path while deleting the old bitmap fonts (the Xserver I have doesnt seem to mix bitmaps and scalable fonts very well when they are of the same foundry-family)... Followup redirected to comp.windows.x as it is not a problem specifc to XFree86 or Free/NetBSDs. -- Amicalement, "Benj" Email: ZarkDav@Eddy.FrMUG.Fr.Net