On 16-Nov-00, Rob Little wrote:
>> AWeb should be set up in the OS to lay out the HTML and print to
>> PostScript? Then Voyager could just collect the files and pass them
>> on to AWeb.
>
> I don't follow you there - what does AWeb have to do with this? It's
> another browser, so what's the relevance??
It's the browser that is supplied with the OS.
> Regardless of the fact that you are overstating the importance of and
> discriminating in favour of postscript, you're missing the point. It's
> printer *drivers* (part of the OS) that should handle the language.
> All the browser should do is speak to the driver.
PostScript is the standard professional printing technology.
When the browser "speaks" to the driver, what is it saying? It has to
tell the driver
1. What font is in use
2. What size
3. Where each word or character is on the page
4. Where each image is
5. Image scale/size
6. List the image pixels.
All of these can be expressed simply in Postscript code. So for PS you
don't need a driver in the OS. There is a driver built into the printer.
> You obviously CAN write apps to speak particular languages and
> dialects but it just isn't sensible and certainly shouldn't be
> expected.
So what language _should_ the program output? It has to have some set of
organised and logical commands - ie a language. Why not Postscript?
This language is specifically designed for graphics.
It would make more sense to me if the OS used a PostScript interpreter
as the driver for bitmap based printers, rather than each program having
to make its own bitmaps as Voyager does now.
Regards
--
Don Cox
[EMAIL PROTECTED]
_____________________________________________________________________
Voyager Mailing List - http://v3.vapor.com/
Voyager FAQ....: http://faq.vapor.com/voyager/
Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP
Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
