Actually, Terminal does use the Monaco that's in the font folder. I found this out the hard way when I cleaned out my font folders, and accidentally took Monaco out. Terminal defaulted to "null, 0 pt" and was rendered useless. Took me ages to figure that one out...
On 5/30/06, Tony Spencer <[EMAIL PROTECTED]> wrote:
On 29 May 2006, at 00:12, Ben Farhner wrote: > Hm.. but somehow Terminal.app manages to display Monaco 10 without > anti-aliasing even though my preferences say to use anti-aliasing > all the way down to size 4 >_> > > I know it's possible, I just need to know how. I don't know for sure, but I would suspect that Terminal has a built in version of Monaco that it uses and doesn't go through the normal font handling processes. This is so you can still use it to fix problems you might have where the font folder can't be seen etc. Kinda like what's built in to DOS. As such it is likely to be included only as a bitmap font, hence there is no possibility of anti-aliasing. Tony Spencer St Rémy de Provence (13) France http://tonyspencer.blogspot.com/ _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
-- -- Philip Regan [EMAIL PROTECTED] http://homepage.mac.com/pregan REALBasic 2005r4, Applescript Mac OS 10.3.9 _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
