HDTenEightyP/NetNews huggingface dataset:
From: sharma@Warren.MENTORG.COM (Sharma Kunapalli)
Newsgroups: comp.lang.postscript
Subject: How to do refresh screen in postscript
Date: 19 Nov 1992 17:57:37 -0500
Organization: Mentor Graphics Corp. -- IC Group
Distribution: world
NNTP-Posting-Host: euler.warren.mentorg.com

Hi All,
	I have recently started to learn postscript.
What I want to be able to do is to 

draw a box
display it
pause for a sec
delete the box
move the box
refresh screen

which in a sense is animation. Is this at all possible
using postscript? (I am more interested in the pause, 
delete and refresh features)

Thanks in advance

Sharma
-- 
The opinions expressed here are solely mine. My company has nothing
to do with these.

Email: sharma@euler.warren.mentorg.com
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.lang.postscript
Subject: Re: WANTED:tutorial manual or books info
Date: 20 Nov 1992 00:28:14 GMT
Organization: HST Wide Field/Planetary Camera
Distribution: world
Reply-To: carl@SOL1.GPS.CALTECH.EDU
NNTP-Posting-Host: sol1.gps.caltech.edu

In article <1992Nov19.203415.10299@trilithon.mpk.ca.us>, henry@trilithon.mpk.ca.us (Henry McGilton) writes:
=    *  do we have any tutorial manual on the
=    *  postscript? I just begin to learn the
=    *  postscript language, and would like to
=    *  find a good tutorial manual or book
=    *  of the language.
=    *  can someone give me some suggestion?
=    *  Thanks in advance!
=
=Our new book is called ``PostScript by Example''.  It is a
=tutorial book on PostScript and covers PostScript Level Two
=patterns, forms, composite fonts, rect operators, and color models.
=
=Look for ``PostScript by Example'', by Mary Campione and
=Henry McGilton. Published by Addison  Wesley.
=648 pages.  Over 500 examples. Over 750 pictures.
=
=A disk is also available separately.  The disk
=contains 13,000 lines of PostScript code from the book.

Or, of course, one could buy that little-known book called the _PostScript_
_Tutorial_and_Cookbook_ (a.k.a. the blue book) from Adobe.
--------------------------------------------------------------------------------
Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL

Disclaimer:  Hey, I understand VAXen and VMS.  That's what I get paid for.  My
understanding of astronomy is purely at the amateur level (or below).  So
unless what I'm saying is directly related to VAX/VMS, don't hold me or my
organization responsible for it.  If it IS related to VAX/VMS, you can try to
hold me responsible for it, but my organization had nothing to do with it.
Xref: sparky comp.lang.postscript:5639 comp.periphs.printers:3387 comp.text.frame:3454
From: mark@gizzmo.UUCP (Mark Hilliard)
Newsgroups: comp.lang.postscript,comp.periphs.printers,comp.text.frame
Subject: HP 300XL Postscript BUG!!
Date: 21 Nov 92 03:49:11 GMT
Reply-To: mark@gizzmo.UUCP (Mark Hilliard)
Followup-To: comp.lang.postscript
Organization: Eastman Kodak


I have discovered a MAJOR BUG in the postscript version  of  HP's
new  HP  300XL PS printer when used with FrameMaker under SCO ODT
486, and on a SUN IPC. The problem is that  when  you  capture  a
color  image greater than 16 colors and import it into your frame
document (put in several colored lines of text to  verify  proper
color  maps),  It will only print around 8 of the total colors in
the image.  This makes for a VERY STRANGE  looking  document.   I
have  printed  to a file and then tried the file on various other
printers and THEY ALL WORK! The HP tech said that  I  was  crazy,
that  this  is  Postscript level 2, and it has been fully tested!
Come on HP, when you ship the SAME file to  2  printers  side  by
side  through the SAME PRINT SPOOLER and the HP printer dies then
HP has a problem.  I am  tired  of  finding  repeatable  bugs  in
various  Post  Script  color  printers only to have their support
tech act like I am calling their product trash and refuse to work
with me on the problem.

Has anyone  else tried this little color test in  Frame?  I  have
found  other  printers  that  will fail this one (Seiko 4104, but
they bent over backwards to FIX it!), but except for  HP  all  of
the  other companies fixed the problem as soon as I brought it to
their attention.

The HP 300XL is a very nice (fast processing but  slow  printing)
Postscript   printer   in   every  other application  except  for
Frame.  It is low cost, and gives  VERY HIGH QUALITY output,  but
the folks at HP support  are  making  it into  a  trash  printer.
Come on HP get on the ball and fix this thing!
-- 
Mark Hilliard, Eastman Kodak  - mark@kodak.COM
                              - uunet!kodak!gizzmo!mark
Newsgroups: comp.lang.postscript
From: goldman@cray.com (Matthew D. Goldman)
Subject: oops... corrected source follows.
Date: 19 Nov 92 11:35:28 CST

Sorry about that.  Try this.

%!
/SectorTitle {          % string x y r > -
        gsave                           % save graphics state
                /R exch def             % Pull info off stack.
                /Y exch def             %   remember first in and
                /X exch def             %   last out queue.
                0 setgray               % color to black
                /Times-Roman findfont   % select font
                32 scalefont            % set pointsize
                setfont                 % use this as the default font
                X Y moveto              % select x and y
                R rotate                % orient text
                currentpoint translate  % not quite sure why this is necessary
                show                    % put the letter on the page
        grestore                        % put graphics state back
} def

(Test Info - 590 36 90) 590 36 90 SectorTitle
(Test Info - 75 600 270) 75 600 270 SectorTitle

showpage
-- 
Matthew Goldman              E-mail: goldman@orac.cray.com
Fax: (612) 683-3099                   Work: (612) 683-3061
      "Say George, I don't mean to interrupt, but 
       there's a glowing red dot on your forehead."
From: mkant+@cs.cmu.edu (Mark Kantrowitz)
Newsgroups: comp.lang.postscript
Subject: Re: Postscript Font Scaling & Reduction
Date: 22 Nov 92 06:02:39 GMT
Article-I.D.: cs.By3ssn.CBJ.1
Distribution: na
Organization: School of Computer Science, Carnegie Mellon

In article <1992Nov19.174800.23493@adobe.com> delahunt@adobe.com (Jim DeLaHunt) writes:
>The hints make adjustments based on the number of device pixel spanned by 
>the scaled outline, not based on the point size per se.  Hinting will have
>the same effect on a 10-point font on a 300 dpi device as on a 5-point font 
>on a 600 dpi device.

More precisely, hints make adjustments based on the number of lines to
the em square. A 12 point font on a 300 dpi device will have
	12 points x 1 inch / 72 points x 300 dpi = 50 lines
(Strictly speaking, that 72 should be 72.289, but lets not nitpick.)

Most intelligent scan conversion algorithms do not work well below
about 24 lines (though I've seen Bitstream's fontware work well on
Helvetica at 6 lines). That's why most systems that generate screen
fonts use canned bitmaps below 18 point. 
Newsgroups: comp.lang.postscript
From: mcovingt@aisun3.ai.uga.edu (Michael Covington)
Subject: Word Perfect driver?
Organization: AI Programs, University of Georgia, Athens
Date: Tue, 24 Nov 1992 03:11:02 GMT

Which Word Perfect printer driver is best for generating "generic"
PostScript files that are to be distributed by FTP for printing on
unpredictable kinds of printers?

I was using the Apple Laserwriter one, but its output gives an error
when previewing on a Sun under Pageview.

-- 
:-  Michael A. Covington     internet mcovingt@uga.cc.uga.edu 
:-  Artificial Intelligence Programs       phone 706 542-0358
:-  The University of Georgia                fax 706 542-0349
:-  Athens, Georgia 30602-7415 U.S.A.     amateur radio N4TMI
Newsgroups: comp.lang.postscript
From: rthomson@mesa.dsd.es.com (Rich Thomson)
Subject: Re: Is there interest in comp.sources.postscript?
Reply-To: rthomson@dsd.es.com (Rich Thomson)
Organization: Design Systems Division, Evans & Sutherland, SLC, UT
Date: Sun, 22 Nov 92 22:50:42 GMT

In article <6764@m1.cs.man.ac.uk>
	lilleyc@cs.man.ac.uk (Chris Lilley) writes:
>   [proposal for comp.sources.postscript and comp.sources.postscript.d]
>
>There are two reasons why the suggested names are a good idea.
>Firstly, they follow existing net conventions of a sources or binaries
>group paired with another group with the ".d" appended - meaning the
>discussion group. Conforming to the defacto naming standard seems a
>good thing in itself - people know what to expect of the group simply
>by looking at its name.

I disagree.  My experience indicates that many people either don't
realize there is a ".d" group and don't know that "d" means
discussion, either.  All you have to do is to take a look at any of
the unmoderated pictures groups to see that there are tons of people
who won't follow this convention, _even_ when they do understand it.

>Secondly, it ensures that discussion - which can be quite lengthy and
>can diverge wildly from the original topic before the thread dies - is
>in a separate group.

A moderator ensures that discussion doesn't end up in the sources
group.  The moderator can simply point them back to
comp.lang.postscript.

>Moderated. Make that three reasons. A moderated sources group would be
>a good idea IMHO, wheras I feel the discussion group would be better
>unmoderated.

Exactly.  With a moderated sources group, there is no need for an
"extra" discussion group.  I could see the argument for creating
another discussion group if the volume of comp.lang.postscript was
already high, but any extra discussion can easily find room here.

						-- Rich
-- 
		      Don't blame me; I voted Libertarian
Disclaimer: I speak for myself, except as noted; Copyright 1992 Rich Thomson
UUCP: ...!uunet!dsd.es.com!rthomson			Rich Thomson
Internet: rthomson@dsd.es.com	IRC: _Rich_		PEXt Programmer
Newsgroups: comp.lang.postscript
From: lwv26@cas.org (Larry W. Virden)
Subject: Re: Wanted s/w Simple Postscript Typesetting for Slides ...??
Followup-To: comp.lang.postscript
Reply-To: lvirden@cas.org (Larry W. Virden)
Organization: Nedriv Software and Shoe Shiners, Uninc.
Date: Wed, 18 Nov 1992 13:08:39 GMT

There is a similar program for the SPARC and probably most other Unix boxes
now as well.  I believe it is called Perspecta Presents!.  There is some
info and a version on ftp.uu.net (perhaps in /tmp - if not, in the
/vendors under perspecta I would guess).
-- 
Larry W. Virden                 UUCP: osu-cis!chemabs!lvirden
Same Mbox: BITNET: lvirden@cas  INET: lvirden@cas.org
Personal: 674 Falls Place,   Reynoldsburg, OH 43068-1614
Newsgroups: comp.lang.postscript
From: delahunt@adobe.com (Jim DeLaHunt)
Subject: Re: Postscript Font Scaling & Reduction
Organization: Adobe Systems Incorporated
Distribution: na
Date: Wed, 18 Nov 1992 18:11:37 GMT

In article <1992Nov18.045514.4005@oucsace.cs.ohiou.edu> 
carlip@oucsace.cs.ohiou.edu (Walter C3arlip) writes:

>... As I understand it, a given style of type will
>have a different design depending upon the point size it is to be printed
>at, e.g., Times Roman at 12pt will have lines that are wider and darker
>relative to the hight of the letter than Times Roman at 20pt.

In the good old days of cold lead type (and maybe hot lead type, I don't know)
this was true.  A 'font' consisted of a certain typeface at a certain size,
so a different mold or type slug was used for each different size.
This in turn allowed the design to be varied among sizes in the way you 
describe.

When the industry switched to phototypesetters, this variation was lost.
The 'font' was then a collection of transparent masks at a single size, and
optics scaled the mask linearly to the desired size.

PostScript technology preserved this linear scaling.  The glyph outline
is described in bezier curves, and the PostScript interpreter scales the
outline linearly to the desired size.  Therefore, most PostScript typefaces
have a single design which is used for all sizes.

I say *most*, because Multiple Master font technology returns the 
flexibility type designers had with hot lead.  A Multiple Master typeface
contains two or more 'master designs', and you can create 'font instances'
which are a mixture of the two master designs.  If the designers choose,
they can make masters with two different 'design sizes'.  Adobe's Minion
Multiple Master typeface contains masters with optical sizes ranging from
(I think) 6 points to 72 points.

I don't claim to be Adobe's expert on type, but the above is a rough
explanation, and may show why you got two opposite answers to your question.

To give a practical answer to your practical question, I'd say that 
printing at a larger size with lower resolution and then photo-reducing 
down has always worked pretty well for me.  But then, I'm an engineer, not
a designer.

>_____________________________________________________________________________
>Walter C3arlip				    **** carlip@ace.cs.ohiou.edu ****
>(the "3" is silent)			

	--Jim DeLaHunt, Developer Support, Adobe Systems Incorporated	
delahunt@mv.us.adobe.com  ...!{apple,decwrl}!adobe!delahunt    +1-415-962-3790
From: bkph@kauai.ai.mit.edu (Berthold K.P. Horn)
Newsgroups: comp.lang.postscript
Subject: Re: Who bakes the Best PostScript?
Date: 16 Nov 1992 17:02:54 GMT
Organization: MIT Artificial Intelligence Lab
NNTP-Posting-Host: kauai.ai.mit.edu
In-reply-to: nick@sw.stratus.com's message of 13 Nov 92 13:41:35 GMT


Talking of which, why are there still losts of programs around that
understand DSC 2.0, but not DSC 3.0? Hasn't it been two or three years
since the revision was made?  I am thinking particularly of page imposition
software (can ANY read DSC 3.0?), PostScript previewers etc.

Berthold K.P. Horn
Cambridge, Massachusetts, USA
From: brown@vidiot.UUCP (Vidiot)
Newsgroups: comp.lang.postscript
Subject: Re: EPS files inside procedures or loops
Date: 21 Nov 92 05:30:03 GMT
Reply-To: brown@vidiot.UUCP (Vidiot)
Organization: Vidiot's Hangout

In article <1992Nov18.210823.8944@dsg.cs.tcd.ie> cjmchale@dsg.cs.tcd.ie (Ciaran McHale) writes:
<
<If I want something (e.g., a logo) to appear on each page of a document
<then I could either write the code once for each page, or write a
<procedure (which goes into the document's prolog) which does the
<necessary and then invoke this procedure for every page. One benefit of
<this latter solution is a reduction in the size of the PS file.
<
<But what if the thing I want to appear on each page is an EPS file? Is
<it legal to have code like the following:
<
<	/foo
<	{
<		"some housekeeping before including EPS file"
<		... included EPS file here
<		"some housekeeping after including EPS file"
<	} def
<
<and then invoke foo multiple times in the document? I looked in the Red
<Book (the new one for PS Level 2) at the sections which deal with EPS
<files and couldn't find any discussion of this.
<
<What I think would prevent the above from working is if the EPS file
<contained an image whose data was read directly from "currentfile" (as
<is often the case with images).

All of this should work, including images, though that I haven't done
personally.

The part that may get you is that if the included EPS file doesn't place
its definitions into a dictionary, you will run out of dictionary space.
You will have to increase the dictionary size in order to be able to
include the EPS file.

I do a few neat things with groff and I plan on posting a description of what
I do to get it to work.  I've combined the power of groff and the power of
PostScript and done some fancy things.  Soon I plan and providing examples
of what I have done.  Maybe someone else could use what I have done.
-- 
      harvard\                          spool.cs.wisc.edu!astroatc!vidiot!brown
Vidiot  ucbvax!uwvax..........!astroatc!vidiot!brown
      rutgers/            INTERNET:vidiot!brown%astroatc.UUCP@spool.cs.wisc.edu
                                   brown@wi.extrel.com
Newsgroups: comp.lang.postscript
From: jott@tagore.helios.nd.edu (John Ott)
Subject: Re: psnup
Reply-To: jott@tagore.helios.nd.edu (John Ott)
Organization: Univ. of Notre Dame
Date: Tue, 17 Nov 1992 13:48:53 GMT

In article <3998@ecicrl.ocunix.on.ca>, clewis@ferret.ocunix.on.ca (Chris Lewis) writes:
|> In article <BxtJzn.7By@hermes.hrz.uni-bielefeld.de> mib@bio128.uni-bielefeld.de writes:
|> >In article <1e1ug7INNf0v@agate.berkeley.edu> pinghua@emily9.Berkeley.EDU  
|> >(Pinghua Young) writes:
|> >> This may be a dumb questions, but is there a psnup program that
|> >> works with PostScript file which itself contains EPS files?
|>  
|> >> I tried the pnsup from wuarchive.wustl.edu but it didn't work
|> >> with included EPS graphics (I mean it didn't shrink the graphs). 
|> 
|> >I had the same problem with psnup (don t remember the version). The solution  
|> >was mpage.
|> 
|> Yeah, but mpage insists on borders...
|> 
|> It might be worth checking the PostScript to see if it does saves
|> and restores around the EPSes.  If it's not, try inserting some
|> and see if the situation improves.
|> -- 
|> Chris Lewis; clewis@ferret.ocunix.on.ca; Phone: Canada 613 832-0541
|> Psroff 3.0 info: psroff-request@ferret.ocunix.on.ca
|> Ferret list: ferret-request@ferret.ocunix.on.ca

Then what does the -b switch do?

John
jott@tagore.helios.nd.edu
Organization: Arizona State University
Date: Tuesday, 17 Nov 1992 13:19:58 MST
From: Ben Goren <AUBXG@ASUACAD.BITNET>
Newsgroups: comp.lang.postscript
Subject: Re: Who bakes the Best PostScript?

(Sorry I can't quote from the original article--this newsreader is
somewhat primitive....)
As far as the worst PostScript goes, I'd say that Finale (a music
notation program for the Macintosh) has to win the prize hands down.
I'd even go so far as to say that it's the worst programming I've
ever seen, and I'm including my own feeble attemps at BASIC on an
Apple II almost a decade ago.

What makes PostScript "good"? I'd say that, first of all, it must
conform to the DSC. Even hand-written code can do this quite nicely,
and it gives a good structure to the program. Beyond that, my personal
preference is for short, highly-tuned code that (hopefully) executes
quickly. Rather than individually draw a hundred squares of varying
shades of gray on the page, as in a color calibration sheet, I'd try
to get the whole thing in a single line with a couple of for loops.

I generally don't like to see things repeated in any computer language.
If you can type out the same line, with minor modifications, a dozen
times to get what you want, the computer can probably do the same thing,
but quicker, if you just have it loop. Most machines now have some sort
of instruction or data cache that make such things highly efficient.

Of course, all this must be balanced with the realities of the situation.
If I needed to get something done in the next five minutes, I'd probably
use cut-and-paste, and figure the extra interpretation time is worth it.
Newsgroups: comp.lang.postscript
From: mkant+@cs.cmu.edu (Mark Kantrowitz)
Subject: Re: Postscript Font Scaling & Reduction
Organization: School of Computer Science, Carnegie Mellon
Distribution: na
Date: Thu, 19 Nov 1992 17:23:09 GMT

In article <4007@ecicrl.ocunix.on.ca> clewis@ferret.ocunix.on.ca (Chris Lewis) writes:
>I was under the impression that the "hints" allow the font machinery
>to do adjustments based on target point size.  From my experiments, linear
>font scaling doesn't look that great.

Adobe hints are used in rasterization of an outline. They try to
ensure that strokes have the same width, and so on. But they can't fix
an outline designed for 72 point to work well at 6 point. When you
reduce sizes, you need to make open spaces larger, thins relatively
thicker, and so on.

However, Bitstream's hints are much more intelligent, and in practice
alter the way they rasterize an outline at small point sizes to avoid
some of the problems with using an outline designed at a different size.
That's why Bitstream's fontware produces better looking output than
Adobe or Compugraphic.

--mark
Xref: sparky comp.lang.postscript:5551 comp.unix.sysv386:16517 comp.sources.wanted:5069 comp.unix.sys5.misc:60
From: pb@idca.tds.philips.nl (Peter Brouwer)
Newsgroups: comp.lang.postscript,comp.unix.sysv386,comp.sources.wanted,comp.unix.sys5.misc
Subject: postscript for printer banner page wanted.
Date: 16 Nov 92 08:22:09 GMT
Reply-To: pb@idca.tds.philips.nl (Peter Brouwer)
Organization: Digital Equipment Enterprise B.V.,Apeldoorn,The Netherlands.

X-Disclaimer: This opinion is mine alone

I am looking for source ( postscript ) for a banner page to be used
for postscript printers.
--
#  Peter Brouwer,                | Digital Equipment Enterprise ,              #
#  NET  : pb@idca.tds.philips.nl | Integration Industry Standard Systems,      #
#  PHONE:ext [+31] [-0]55 432992,| Dept Systems Enginering, Bld V1/B4          #
#  FAX  :ext [+31] [-0]55 432070 | P.O.Box 245,7300AE Apeldoorn,The Netherlands#
From: lilleyc@cs.man.ac.uk (Chris Lilley)
Newsgroups: comp.lang.postscript
Subject: Re: Is there interest in comp.sources.postscript?
Date: 19 Nov 92 14:25:33 GMT
Organization: Dept Computer Science, University of Manchester, U.K.

In article <1992Nov14.235834.9723@dsd.es.com> rthomson@dsd.es.com
(Rich Thomson) writes: 

>In article <1992Nov14.034205.7362@gvl.unisys.com>
>	wrp@pslsrv1.gvl.unisys.com (Bill Pringle) writes:

>>If you don't have both groups, then you
>>have to weed through lots of comments to get the sources.

>This is one of the many reasons for moderating a sources group.  The
>moderator would simply weed out any comments and not approve them.

You mean, just discard them? Why? Are you trying to stop any of the
discussion that would occur when sources were posted?

Or are you suggesting that the moderator(s) should redirect discussion
to the comp.lang.postscript?

--
Chris Lilley
---------------------------------------------------------------------------
Technical Author, ITTI Computer Graphics and Visualisation Training Project
Computer Graphics Unit, Manchester Computing Centre, Manchester, UK
Internet:   lilley@cgu.mcc.ac.uk        Janet:   lilley@uk.ac.mcc.cgu
Voice:      +44 (0)61 275 6095          Fax:     +44 (0)61 275 6040
---------------------------------------------------------------------------
From: clewis@ferret.ocunix.on.ca (Chris Lewis)
Newsgroups: comp.lang.postscript
Subject: Re: Text formatters turn PostScript upside down -- why?
Date: 20 Nov 92 00:28:22 GMT
Organization: Elegant Communications Inc., Ottawa, Canada

In article <4438@vidiot.UUCP> brown@vidiot.UUCP (Vidiot) writes:
|In article <1992Nov14.222532.8727@cs.brown.edu> jgm@cs.brown.edu (Jonathan Monsarrat) writes:
|<Why do text formatters/converters like dvips (for TeX) and grops (for Troff)
|<define everything upside down in PostScript?

|<Just to be mean?

|Upside down?  Nope.  I believe it has to do with printing the page from top
|down, which is how the text is formatted.  But, PostScript's origin is the
|lower-left corner.  So, groff moves it to the top-left corner, so that the
|output can be top down.

|OK, so it looks like the document should print upside-down, but it really
|doesn't.  I'm not positive (James Clark will have to say for sure), but I
|think that the fonts are re-encoded upside-down.  I couldn't find anyplace
|else where it could be.  But a little test I did with my stuff seems to prove
|out that theory.

|So, in the end, everything comes out right-side up.

|Is it mean to upside-down the upside-down?  While it is a necessary evil,
|it definately keeps you on your PostScript toes.

It's not necessary.

This is really simply a matter of the guy writing the driver deciding
which set of coordinates that he wants to think in.  As a counter example,
the PostScript that Psroff generates is right-side-up w.r.t. PostScript
with no rotates, scales or translates of any kind.  Then I didn't have
to think about font transform matrices, and it only costs a subtraction
in the driver.  There is no real penalty, because psroff has to cope
with multiple frame resolutions/orientations anyways.
-- 
Chris Lewis; clewis@ferret.ocunix.on.ca; Phone: Canada 613 832-0541
Psroff 3.0 info: psroff-request@ferret.ocunix.on.ca
Ferret list: ferret-request@ferret.ocunix.on.ca