Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!uwm.edu!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!morris
From: morris@ux1.cso.uiuc.edu
Newsgroups: comp.sys.mac
Subject: Re: Royal vs Adobe
Message-ID: <18000050@ux1.cso.uiuc.edu>
Date: 10 Apr 90 00:39:30 GMT
References: <27618215MES@MSU>
Lines: 17
Nf-ID: #R:<27618215MES@MSU>:-17:ux1.cso.uiuc.edu:18000050:000:1126
Nf-From: ux1.cso.uiuc.edu!morris    Apr  9 12:15:00 1990


Remember, Apple is not dumping postscript, it is only dumping Adobe fonts.
They licensed a postcript clone interpreter from Microsoft. Royal fonts will
be easier to use because they will be incorperated into the system, not with
a hack like ATM, they will be installed by dragging them into a folder, which
eliminates pesky font ID problems (anyone who has worked with different fonts
and a Lino service knows these) and Apple will publish their full specifications
which will allow all the type makers free access (and public domain & 
shareware font makers). All this will be gracefully integrated into System 7.0
which means any software which uses standard system calls will work (about 98%).
The only programs that will have a problem are ones that don't use standard
system calls (and ones that use postscript font rendering stuff).

Why will Royal be better? Faster rendering for slightly larger files, fully
integrated screen and printer fonts (not like the mess there is now), true
WYSIWYG, peace with fonts, peace on earth! No more nasty cludges and third
party font wars (like with bitstream and other companies).