HDTenEightyP/NetNews huggingface dataset:
From: hebert@OCE.ORST.EDU (Dave Hebert)
Newsgroups: comp.lang.postscript
Subject: Eye Chart
Date: 20 Nov 92 14:29:15 GMT
Article-I.D.: gaia.1eisnrINNbjn
Organization: College of Oceanography, Oregon State Univ
NNTP-Posting-Host: kaibab.oce.orst.edu


Does anyone have a postscript file that makes the classical eye testing chart?
Newsgroups: comp.lang.postscript
From: goldman@cray.com (Matthew D. Goldman)
Subject: Help request
Keywords: text along a line
Date: 16 Nov 92 12:59:29 CST


Hello!  I have a question that I hope someone out there can
answer for me.

I want to be able to center text along a line between two points.

How should I go about it?

Thanks for your time.

Matt
goldman@orac.cray.com
-- 
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: clewis@ferret.ocunix.on.ca (Chris Lewis)
Newsgroups: comp.lang.postscript
Subject: Re: Finding out the real page counter.
Date: 17 Nov 92 02:10:59 GMT
Organization: Elegant Communications Inc., Ottawa, Canada

In article <2600@irit.irit.fr> stolte@irit.irit.fr (Nilo STOLTE) writes:
><somebody said>
>>>problem. (I.e. a program that determines the number of pages in a any
>>>given PS-file)

>  Simply count the number of "%%Page:" that there is in your PostScript file. You
>can write easily a program to do that...

Please read the PostScript FAQ.  This doesn't work, in general, because
not all PostScript has %%Page: comments in them.

The original poster should be able to delay the pagecount evaluation until
end of the job.
-- 
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
From: stolte@irit.fr (Nilo STOLTE)
Newsgroups: comp.lang.postscript
Subject: POSTSCRIPT TEXT FORMATTER: Msg to whom have copied it
Date: 17 Nov 92 18:03:33 GMT
Organization: IRIT-UPS, Toulouse FRANCE

Dear users of the PostScript text formatter:

  If you use this program and would like to receive new versions of it, or if
you has made a change that could benefit the other interested people in it,
please send me a mail to stolte@irit.fr, ok? For now this list is constituted
by the following addresses:

  AUBXG@ASUACAD.BITNET
  jgm@cs.brown.edu
  jm@aristote.univ-paris8.fr
  luc@kriek.cs.mcgill.ca

  Thank you very much

Nilo.
Newsgroups: comp.lang.postscript
From: jos@bull.nl (Jos Vos)
Subject: Examples from Real World PostScript book wanted
Organization: Bull, P.O. Box 22859, NL-1100 DJ Amsterdam, The Netherlands
Date: Mon, 16 Nov 1992 10:43:19 GMT

Does anyone have the examples listed in the book "Real World PostScript"
written by Stephen Roth available for FTP-ing (you may also send them to
me by mail).

Please MAIL responses to me.
Thanks.

-- 
--    Jos Vos <jos@bull.nl>   (UUCP: ...!{uunet,mcsun,sun4nl}!nlbull!jos)
--    Bull Nederland NV, Product Support Unix, Amsterdam, The Netherlands
From: brown@vidiot.UUCP (Vidiot)
Newsgroups: comp.lang.postscript
Subject: Re: Text formatters turn PostScript upside down -- why?
Date: 22 Nov 92 06:27:41 GMT
Reply-To: brown@vidiot.UUCP (Vidiot)
Organization: Vidiot's Hangout

In article <4010@ecicrl.ocunix.on.ca> clewis@ferret.ocunix.on.ca (Chris Lewis) writes:
<
<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.

Interesting point.  Obviously it is easier to just change the spot on the paper
right before it is printed, than it is to flip everything over.

But here is an interesting thought.  When I was supporting both Adobe
TranScript's psroff and groff, I kept the origin in the upper-left corner
when I included my own EPS files.  If I would have used your Psroff, wouldn't
the default location be the lower-left corner?  If so, that would mean my code
to position EPS file would be really different that what I used for psroff.

I have to admit that there was separate code to include PostScript files into
my final output because psroff and groff do it differently.  But, the math to
position the output was the same.

If I would have moved the origin back to the lower left corner, then it would
have been the same for all three versions.  I'm not sure why kept the location
in the upper-left corner.  If I remember, I was thinking about A4 paper output.
But, many moons later has proven that the starting position doesn't matter.

This isn't to say that your leaving the origin in the lower-left corner is
wrong, quite the contrary.  My leaving the origin in the upper-left corner
isn't exactly right.  It has actually come to haunt me a little bit.

James is the only person that can answer why an upper-left origin was used,
instead of a lower-left origin.

-- 
      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
From: lilleyc@cs.man.ac.uk (Chris Lilley)
Newsgroups: comp.lang.postscript
Subject: Re: object oriented editing from eps
Date: 17 Nov 92 05:08:46 GMT
Organization: Dept Computer Science, University of Manchester, U.K.


In article <Bxnsy1.G62@ux1.cso.uiuc.edu>, hudson@ux1.cso.uiuc.edu (John Hudson) writes:

>) Is there any application (commercial or not) for any common 
>) computer (Unix, Mac, PC) that will allow object oriented editing
>) of graphics in an eps format file?

Island Draw (on unix boxes, either Motif or OpenLook) can import
Postscript and give you an editable structured object. From any old
postscript, it would seem. It read in stuff from Corel, OK that could
be easy with all those %Object comments. But it read in some hand
coded stuff I wrote and you could edit it with the mouse. Wierd. I was
impressed. 

--
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
---------------------------------------------------------------------------
Newsgroups: comp.lang.postscript
From: ab@nova.cc.purdue.edu (Allen B)
Subject: Re: How to do refresh screen in postscript
Organization: Purdue University
Date: Fri, 20 Nov 1992 15:42:46 GMT

In article <1eh651INN16g@euler.Warren.MENTORG.COM> sharma@Warren.MENTORG.COM  
(Sharma Kunapalli) writes:
> Hi All,
> 	I have recently started to learn postscript.
> What I want to be able to do is...
> ...in a sense is animation. Is this at all possible
> using postscript? (I am more interested in the pause, 
> delete and refresh features)

Yes, but it depends somewhat on your environment.  I've
written files like that and the old Preview on the NeXT
would display them the way I wanted, but most would cache
all the stuff up and wouldn't display it in real-time.

You can make a "flip book" by making each frame a page and
putting in the proper DSC for each.  Then you can flip it on
the screen with a previewer.

Usually, you'd want to do the display part in PostScript
and the timing and frame advancement in another way.  What
environment is this to run in?

---
save /- 1 string def[331 64 779242 46 396 46 871217102 46 14782 10]{dup
99 lt{- 0 3 -1 roll put -}{32 =string cvrs}ifelse print} forall restore
From: carlip@oucsace.cs.ohiou.edu (Walter C3arlip)
Newsgroups: comp.lang.postscript
Subject: Postscript Font Scaling & Reduction
Date: 18 Nov 92 04:55:14 GMT
Distribution: na
Organization: Ohio University Mathematics


I have a technical question to ask about Postscript Font Scaling and its
relation to font design.  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.

Now, when one uses postscript fonts, one has outline descriptions of the
font.  Is it possible to determine what point size the font was designed
for?  When one prints the font at a larger size, is the font scaled 
linearly or is postscript smart enough to 'redesign' the font for the
larger size? 

Let me put this an another context.  Suppose one wants to produce 
a journal using a 300dpi printer.  If one uses a 24pt design, and
then uses photo reduction to 12pt, can one effectively get 600dpi
resolution (I'd expect this to work if the fonts are scaled linearly),
or will the reduced copy look like type designed for 24pt and
then shrunk (so that the type does not match its design size)?

I'm looking for the straight dope here, as I have already gotten 2 opposite
answers to this from people I'd expect to know. 

Thanks!

--Walter



-- 
_____________________________________________________________________________
Walter C3arlip				    **** carlip@ace.cs.ohiou.edu ****
(the "3" is silent)			
_____________________________________________________________________________
Newsgroups: comp.lang.postscript
From: ab@nova.cc.purdue.edu (Allen B)
Subject: Re: Postscript Font Scaling & Reduction
Organization: Purdue University
Distribution: na
Date: Fri, 20 Nov 1992 15:21:41 GMT

In article <1992Nov20.020424.5847@adobe.com> mmwang@adobe.com (Michael Wang)  
writes:
> As the point size gets smaller than this optimum size, reading
> comprehension begins to suffer because it becomes more difficult to
> discern individual words and letters. Conversely, as the point size
> gets larger, reading speed suffers since instead of reading groups of
> words at a time, you start to focus on individual words or letters.

I get what you're saying and it makes a lot of sense.  I'm
just wondering how the optimum size is related to size
(or, I guess it would be better to say "extent") and
resolution.

If the extent of a letter is too small, it's unreadable no
matter what the resolution is because you hit the wall.  If
the number of pixels in a character is too small, you can't
read it either.

Let's not worry about resolution for the moment.  We can
avoid that by assuming we're talking about billboards or
very high resolution printer output.  The extent of a
character on a billboard might be the same as that on a page
at the expected viewing distance for both.  Imagine it's
not foggy out or anything like that. :-)

OK, now I think know about what extent is difficult for me
to read because it's too small.  I also think I see where it
gets too big.  

> To compensate for these problems, type designers in the past created
> slightly different designs for different point sizes. At smaller
> sizes, generally the x-height was enlarged, contrast between strokes
> decreased, width of the various letters increased slightly and the
> letterspacing was looser. At larger sizes, the opposite was done. The
> effect of all these changes was to try and make those sizes more
> readable.

Those all work for me, but it really looks like you're just
avoiding the bad sizes.  Actually, that's probably the
best solution. :-)

In Type 1 fonts, all the hinting is aimed at resolution
limits and it seems to work OK.  What type of hinting
mechanism would help optical scaling?  It'd be based on
actual size (or extent if we know it), right?

I suppose if you had a function that gave xheight as a
(nonlinear) function of pointsize and another for
letterspacing (sidebearing?), that'd be a good start.

Instead of a function, maybe you could just describe the
nonlinear regions somehow.  There ought to be a big linear
region in the middle and then a tapering off at both ends,
right? 

---
save /- 1 string def[331 64 779242 46 396 46 871217102 46 14782 10]{dup
99 lt{- 0 3 -1 roll put -}{32 =string cvrs}ifelse print} forall restore
Newsgroups: comp.lang.postscript
From: goldman@orac.cray.com (Matthew D. Goldman)
Subject: Re: Conference name placards
Keywords: placards
Organization: Cray Research, Inc.
Date: 19 Nov 92 11:02:58 CST

In article <BxxIt6.3KI@news.cso.uiuc.edu> mkiteam@osiris.cso.uiuc.edu (Ed Japel) writes:
>Hi!  I have been trying to write a postscript program to print
>a persons name on one long edge of a paper, and again along
>the opposite edge, rotated so that when the paper is folded in the middle (lengthwise, the name will be readable from either side.  This should
>not be as difficult as I am trying to make it, I have a bad case
>of brain-block.   Thanks for any help!
> 
>Michael Moe
>mkiteam@osiris.cso.uiuc.edu
>

%!
/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  % orient new zero location.
                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

That should do it.

Matt


-- 
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: bradlee@cg-atla.UUCP (Rob Bradlee)
Newsgroups: comp.lang.postscript
Subject: Any Applications producing significant amounts of Level 2 PS?
Keywords: Level2 PostScript
Date: 17 Nov 92 18:27:37 GMT
Distribution: comp
Organization: Agfa Compugraphic Division, Wilmington, Mass. USA


I'd be interested in hearing which, if any, applications are producing
Level 2 code.  Details on what parts of the language they are
exercising would also be interesting.  I'd be glad to post
a summary to the net if I gather enough information.  (Perhaps
this will be a FAQ?)

				Rob
-- 
Rob Bradlee  w:(508)-658-5600 X5153 
Agfa Corporation.                      ...!{decvax}!cg-atla!bradlee
200 Ballardvale St.                        bradlee@cg-atla.agfa.com
Wilmington, Mass. 01887
From: friedl@mtndew.Tustin.CA.US (Stephen Friedl)
Newsgroups: comp.lang.postscript
Subject: Re: HP 300XL Postscript BUG!!
Date: 21 Nov 92 21:48:30 GMT
Organization: Steve's Personal machine / Tustin, CA

Mark Hilliard writes:
> 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 support a commercial PostScript interpreter and know firsthand
that just because something doesn't print is not necessarily
evidence that the printer is broken.  I have seen many examples
of things that "worked" on other interpreters but "break" on
ours, and after investigation found that it worked by accident.

Perhaps it is truly a bug, but you need to make sure that the
output is not dependent on undocumented features (especially
before making a big noise).

     Stephen

-- 
Stephen J Friedl | Software Consultant | Tustin, CA |     +1 714 544-6561
3b2-kind-of-guy  | I speak for me ONLY |   KA8CMY   | uunet!mtndew!friedl
 
Attorneys are paranoid because they assume everybody else is dishonest too
From: clewis@ferret.ocunix.on.ca (Chris Lewis)
Newsgroups: comp.lang.postscript
Subject: Re: Is there interest in comp.sources.postscript?
Date: 23 Nov 92 02:16:38 GMT
Organization: Elegant Communications Inc., Ottawa, Canada

In article <1992Nov22.225042.27892@dsd.es.com> rthomson@dsd.es.com (Rich Thomson) writes:
>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.

Forgive me for pointing this out, but, while there is a convention for
".d" groups in some areas, there isn't one in comp.sources.  There is
only one ".d" group, "comp.sources.d" - there isn't a comp.sources.unix.d
or comp.sources.misc.d etc.  We'd be breaking completely
new ground by making a comp.sources.postscript.d.  And I don't believe
there'd ever be enough demand for it.

The comp.sources.postscript moderator could insert Followup-to:
redirections to existing comp.sources.d or comp.lang.postscript.
Preferably the former.

It's not as if c.s.d is overflowing with postings.  This
would separate source posting bug reports and patches.  Ie:
one would want patches to comp.sources.postscript postings to be
in comp.sources.bugs where the existing archivers can snag them.
-- 
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
From: jgm@cs.brown.edu (Jonathan Monsarrat)
Subject: PostScript Programmers -- FAQ help? (was Re: Stack Under/Over flows)
Organization: Brown University Department of Computer Science
Date: Thu, 19 Nov 1992 17:52:25 GMT

This is a good excuse for me to ask for help with the PostScript FAQ,
especially programming it.

> Is the a FAQ on gerenal PostScript troubleshooting??

No, but that would be nice. 

PostScript programmers, would you send me helpful FAQ information that
new programmers could use? Also, any kind of information or
suggestions for changes/corrections would be appreciated. The FAQ is
available by anonymous ftp to
wilma.cs.brown.edu:pub/comp.lang.postscript in ASCII, LaTeX, DVI, and
PostScript formats.

> Also, I would be intersted in finding out some general trouble shooting
> ideas on these Stack U/O flows...

If they are your own PostScript programs, try prepending a special
error handler file. Most PostScript ftp sites will have them. (or
I can email you behandler.ps)

If you are trying to debug a machine generated PostScript output --
then you have more courage than I do!! Generally that takes a serious
PostScript hacker because machine generated PostScript is generally
"compressed" i.e. unreadable. I find it unpleasant to disect such
stuff whenever I have to.

It would probably be easier, if this error is used by QuarkXpress,
to just use some other program (or ask the company that sells it for help).

> I deal with the Mac side of life going to HiRes imagesetters... Most of
> the common apps... PageMaker, Illustrator, FreeHand, QuarkXpress, ect.

There are some very knowledgeable and friendly people in comp.sys.mac.apps.
Elliotte Harold has a very good FAQ for that group, which contains
some PostScript information. You can get it from
"pit-manager.mit.edu" in the directory "pub/usenet/comp.sys.mac.apps/"
as the file "Macintosh_software_frequently_asked_questions_(FAQ)".

-Jon
%! Jon Monsarrat   jgm@cs.brown.edu   Brown University %! Obfuscated PostScript
0 0 moveto 15 setlinewidth(qlllll-??LHHL??llH?hH7t,7olCAHH@)1 setlinejoin{dup
10 mul rotate 80 lt{50 0 rlineto}{50 0 rmoveto}ifelse}forall stroke showpage
Newsgroups: comp.lang.postscript
From: ygor@aplexus.jhuapl.edu (Daniel E. White  (F2C))
Subject: Re: Is there interest in comp.sources.postscript?
Organization: Johns Hopkins U. Applied Physics Lab
Date: Wed, 18 Nov 1992 13:32:13 GMT

In article <92322.133941AUBXG@ASUACAD.BITNET>, Ben Goren <AUBXG@ASUACAD.BITNET> writes:
|> I thought I had either sent a note to somebody on this thread, but
|> checking my notebooks, it seems not....
|> 
|> Anyway, I would like to see a comp.sources.postscript, moderated.
|> I pretty much agree with the arguments posted so far in favor of
|> a moderated c.s.p, so I won't rehash them.
|> 
|> b&

  Sure.  I'd like to see one, too.  Probably moderated.

-- 
------------------------------------------------------------------------
                                                               Dan White
------------------------------------------------------------------------
"Sometimes  I  think  the  surest  sign  that  intelligent  life exists
 elsewhere  in the universe is that none of it has tried to contact us."
                                                  Calvin (Bill Waterson)
From: lilleyc@cs.man.ac.uk (Chris Lilley)
Newsgroups: comp.lang.postscript
Subject: Re: Is there interest in comp.sources.postscript?
Date: 12 Nov 92 21:50:17 GMT
Organization: Dept Computer Science, University of Manchester, U.K.

In article <1992Nov7.141220.4309@kosman.uucp> kevin@kosman.uucp (Kevin
O'Gorman) writes:

> [...] Would people want a PS source group for PS ideas, or for
>pretty pictures?  

Both, but more for ideas.

>Is there enough interest to get the few hundred votes it
>takes for a new group to come even close?

Time will tell - probably

>If so, I think it would be good precisely because PS source is in some ways
>enherently different from other sources.  It tends to have a kernel of
>generally-useful ideas and a huge amount of what's really data.  This may
>annoy folks in other sources groups.  We're sort of used to it.

Well yes. But posting code fragments, routines, that sort of thing
should I think be encouraged.

It would be particularly useful - and form a valuable learning
resource - if the sources group was archived somewhere, and even
indexed. Any offers for a site? or is that premature...

>Anybody who reads this, if you want to make it happen, we need to know you're
>interested.

OK, I did.

--
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
---------------------------------------------------------------------------
Newsgroups: comp.lang.postscript