This is an archive of CompuServe forum messages from 1985 to 1995, as saved in transcripts by John Foust.
Search Results (20 messages)
No. Again: Illustrator documents, be it 88 or otherwise, has the printer name in the file. You could actually download the Adobe file itself to the PS printer (providing the origin was placed properly and that you had appended 'showpage' at the end) and everything would be perfect (and a…
Important to remember, though, that changes to PostScript from Adobe are merely enhancements for speed improvement and device specific things such as halftoning accuracy/speed. Any increment to the PostScript version will never make the RED book obsolete, nor any printer adhering to at least version 23.0 obsolete (the version of…
Why are you using a PC anyway? Mac is better.
What you could try is to print Illustrator documents using the Adobe Separator utility. Unless your customers have a tendency to leave scattered art all over the page.
This anti-aliasing, if it could be called that with 1 bit pixels, seems logical but would take an astronimcal amount of calculations comparatively.
Chances are that updates would be impossible in existing LW's unless you'd agree to an expensive board swap (might be just as easy to buy the latest LW with the upgrade in it).
What would be ideal, using the two master theory, is for the font description to be device smart. It would pull the default matrix and use it to test what size/resolution ratio it's printing at. At that point it would grab two versions of the same character, each specified for…
Notice that showpage was 'appended'. This means that a call to showpage from any program will still call showpage, only now it will be YOUR showpage. Just remember that when you actually wish to print a page, you must now call showpage* or whatever you redefined the true procedure to…
Interesting to note (I run a service bureau in Columbus, Ohio): Illustrator knows the printer font names, unlike any other DTP program. This means that screen fonts need not be loaded for output (no substitution occurs, it's already done at your level). Just thought you'd like to know.
The better method of accomplishing what you seek can be better obtained using Font Harmony (coupled with Suitcase II). Remember, the important thing isn't that you have such and such number for Palatino FOND and such and such number for Palatino Roman FONT or NFNT, but that all are different.…
I personally have yet to see ANYTHING on PC's that look anything but clunky (however you wish the term to apply). Yes the work can get done, but it's a pain in the A*S, even if you're expert at MS-DOS, etc. Now the MAC is a different story. Not only…
Font numbers from one system to the next ARE NOT SIGNIFICANT if the application using the fonts is written properly. Pagemaker, Freehand, Adobe, Quark and many programs like them (you'll need to check which ones) store fonts by FOND name, not by FOND number or by FONT or NFNT number.…
Whoops, that message was garbled when sent… It should read, ahem… /*showpage /showpage load def /showpage { *showpage} bind def Hope that works better.
All you have to do is redefine 'showpage'… *showpage /showpage load def showpage { *showpage} bind def Tis all…
I believe the following sequence of codes will work: statusdict begin pagecount end 20 string cvs At the end of this sequence a single object is left on the stack which is a 'show'-able string of the integer value returned by 'pagecount'.
Type 1 fonts are fonts that are encrypted (secret code) and use Adobe's proprietary hinting technology for low resolution display. Type 1 fonts decode the font information using the 'eexec' operator (documentation to which should be released within a few months). Type 3 fonts are fonts created by anybody else…
Steve: exitserver can be executed anytime there are no composite objects still on the stack or defined in dictionaries. Basically, as long as the environment of the interpeter is the same as the beginning of a job (easily attained by proper use of save/restore) an exitserver could even be done…
Mike You can send as many exitserver routines as you wish in a single blow. But you can only exit the server loop once in a 'connect'. Once you've executed 'serverdict begin exitserver', you can stay there till you turn blue in the face changing persistent parameters till they're worn…
Glad I could help.
Exitserver routines can only be ended by breaking communication with the Interpreter. The interpreter resets itself to the server mode so that the next time you connect, you are back in the server mode.