HDTenEightyP/NetNews huggingface dataset:
From: lilleyc@cs.man.ac.uk (Chris Lilley)
Newsgroups: comp.lang.postscript
Subject: Re: Is there interest in comp.sources.postscript?
Date: 17 Nov 92 05:03:33 GMT
Organization: Dept Computer Science, University of Manchester, U.K.

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

>In article <4424@vidiot.UUCP>
>	brown@vidiot.UUCP (Vidiot) writes:

>>For starters, I'd stick with the following groups:
>>
>>	comp.sources.postscript
>
>This sounds fine.
>
>>	comp.sources.postscript.d
>
>I'm really confused why this group is needed.  Why can't the
>discussion take place in this newsgroup?  Whenever talking about
>proposing groups on usenet, always ask youself this question:
>
>    Will an existing group serve the need?
>
>For me, the need for a place to discuss postscript programming and
>postscript programming techniques is served by comp.lang.postscript.

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.

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. This facilitates automatic archiving of the
sources group., without it being padded out by non-source items. This
is freindly to the disk space of the site(s) archiving it, and
freindly to the patience of people lookin back at the archives for
that little gem of a routine that was posted 5 years ago...

>The need for a group explicitly for posting postscript source isn't
>directly served by c.l.p it seems.  This is even more the case when
>you consider the fact that you probably would like to have the sources
>group moderated.

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.

--
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: Postscript Font Scaling & Reduction
Date: 22 Nov 92 06:08:49 GMT
Distribution: na
Organization: Elegant Communications Inc., Ottawa, Canada

In article <zisk-191192103957@macne006.boston.us.adobe.com> zisk@adobe.com (Stephen Zisk) writes:
|In response to what Chris Lewis and Walter C3arlip wrote, and amplifying
|what Jim Delahunt said, I want to add my $.02. As a caveat, let me say
|I am not a type designer or expert, just an interested amateur.

|    1.) The "design center" for scaling Type 1 fonts (except, of course,
|        for *some* Multiple Master typefaces), is linear scaling at all
|        point sizes.

|    2.) Hints are used to overcome the limitations of low-resolution
|        digital printers. They primarily prevent various kinds of uneven
|        "color" and illegible characters. They do not have substantial
|        effect at large point sizes and high resolutions.

Oops, I realize now where I went wrong which led to me saying that linear
scaling doesn't work that well.  My code scales *bitmaps* (not outlines),
and given the that the base fonts are fairly small pointsizes (10),
they've been "hinted" already.  Ie: linearly scaling a hinted bitmap may not
look all that great.
-- 
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: ath@linkoping.trab.se (Anders Thulin)
Newsgroups: comp.lang.postscript
Subject: Re: Text formatters turn PostScript upside down -- why?
Date: 16 Nov 92 07:22:12 GMT
Organization: Telia Research AB, Teknikringen 2B, S-583 30 Linkoping, Sweden

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?

Upside down? In relation to what?

I suspect you're thinking of the different coordinate origins used:

* DVI files have a origin in the upper left corner of the page, Y
  coordinates going down the page.

* PS has a default origin in the lower left corner, Y coordinates going
  up the page.

>Just to be mean?

To be mean to what - a PostScript interpreter?

To keep things simple.  DVI coordinate origin cannot be changed, but
the PS origin and direction of coordinate axes can. So it's simpler to
remap the PS coordinate system - no need to perform all that tedious
coordinate conversion if PS can do it 'automatically'.

-- 
Anders Thulin       ath@linkoping.trab.se 	013-23 55 32
Telia Research AB, Teknikringen 2B, S-583 30 Linkoping, Sweden
From: bkph@wheat-chex.ai.mit.edu (Berthold K.P. Horn)
Newsgroups: comp.lang.postscript
Subject: Re: Postscript Font Scaling & Reduction
Date: 19 Nov 1992 13:42:28 GMT
Organization: MIT Artificial Intelligence Lab
Distribution: na
NNTP-Posting-Host: wheat-chex.ai.mit.edu
In-reply-to: carlip@oucsace.cs.ohiou.edu's message of 18 Nov 92 04:55:14 GMT


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

   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. 

Type 1 fonts are scaled linearly. So printing at 20pt and scaling 50%
essentially gives you the same shapes you would get if you had printed the
font at 10pt (modulo rasterization effects).

Most Type 1 fonts appear to have a design size of 10pt, 
although it is usually not specified.

Some Type 1 font families come with different fonts for different design
sizes.  For example the Computer Modern fonts in Type 1 form include cmr5,
cmr6, cmr7, cmr8, cmr9, cmr10, cmr12, and cmr17, where the numeric suffix
indicates the design point size.

So you certainly can have different designs for different point sizes, 
although you pay a price in terms of font downloading.

MultipleMaster fonts provide for continuous variation of some parameters,
although this is usually used for weight variation and condensed/expand
rather than design size.

Berthold K.P. Horn
Cambridge, Massachusetts, USA
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.lang.postscript
Subject: Re: How to print a large ps file?
Date: 16 Nov 92 20:50:29 GMT
Reply-To: carl@SOL1.GPS.CALTECH.EDU
Organization: HST Wide Field/Planetary Camera
NNTP-Posting-Host: sol1.gps.caltech.edu

In article <2605@irit.irit.fr>, stolte@irit.irit.fr (Nilo STOLTE) writes:
=>Do you mean to say that you think it's reasonable for someone in a computer
=>science program not to know the difference between the computer on which he's
=>generating the file, the machine that will be spooling the file, and the
=>machine that will actually be printing the file?  If so, then CS is in even
=>worse shape than I thought.
=
=  I really prefer to use programs/languages that are not machine dependent:
=C, PostScript, Latex, ... This inventions about EPS is that turned PostScript
=machine dependent (or worse, program dependent), and also the new commands. There
=should be a standard in EPS also. Certainly the stuff you write about is about 
=computers, but to say that CS is in bad shape just because there are some
=people that don't care about portability is quite too much. In adittion if you
=don't like CS that much you can always quit the area, leaving place to really interested people. I would recomend you to change to Unix since VAX/VMS is
=perhaps turning you a little bit closed-minded.  So be carefull not to offend
=people without any good reason... 

Perhaps you should read the thread through again from the beginning.  It had
absolutely *NOTHING* to do with portability.  Some idiot posted to the group
saying "I've got a PostScript file that's too big for my printer."  Now, it
later developed that the printer had absolutely nothing to do with it.  In
point of fact, the local machine was complaining that the file exceeded limits
on file size for its spool directory.  Now, if someone in a CS program is
incapable of tracking down a problem like that at least to the point of
figuring out which machine is complaining, CS is in sad shape.

--------------------------------------------------------------------------------
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.
Newsgroups: comp.lang.postscript
From: paul@sci.ccny.cuny.edu (Paul Chen)
Subject: Help !!! Postscript in lps20!
Organization: City College of New York - Science Computing Facility
Date: Mon, 16 Nov 1992 16:17:07 GMT


Some of PS files ( not all of them) can not be printed in our DEC
lps20 printer, nut these PS files can be printed in QMS and HP 
laser printer without any problems. The system didn't give us
any error messages, may be we need more fonts? Most of PS files
can be printed in lps20, only some of 'specail or complicated'
PS files have problems to print.
Any suggestions? How can I find out how may fonts do we have?
Do we need to update our lps20 PS software?

Any help will be appreciated.

Paul

-- 
Paul Chen, System Manager                CC   CC  N   N  Y   Y   
Science Computer Facility,J302          C    C    N N N    Y      
City College of CUNY                     CC   CC  N   N    Y    -SCIENCE
New York, NY 10031                    	Internet: paul@sci.ccny.cuny.edu
From: zeno@phylo.genetics.washington.edu (Sean Lamont)
Newsgroups: comp.lang.postscript
Subject: Re: Finding out the real page counter.
Date: 17 Nov 92 08:59:12 GMT
Article-I.D.: u.1992Nov17.085912.5254
Organization: University of Washington, Seattle

In article <2600@irit.irit.fr> stolte@irit.irit.fr (Nilo STOLTE) writes:
>Hi antoon!
>You say:
>...
>>>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...

this is assuming that the document follows proper DSC. Consider the following

%!PS
/Helvetica findfont 20 scalefont setfont
100 100 moveto (spam) show
showpage

This has no instances of %Page in the document, and yet it will print on
99% of the valid postscript devices out there.





-- 
Sean T. Lamont                           |   "Don't oppress me, It's
zeno@genetics.washington.edu             |    'computer of color!' "
lamont@abstractsoft.com                  |_______________________________
Abstract Software                                                         
Newsgroups: comp.lang.postscript
From: henry@trilithon.mpk.ca.us (Henry McGilton)
Subject: Re: WANTED:tutorial manual or books info
Keywords: PostScript, Level Two, Tutorial
Organization: Trilithon Software
Date: Thu, 19 Nov 1992 20:34:15 GMT

In article <1992Nov18.165111.23054@eng.ufl.edu> zzang@stat.ufl.edu (zzang)  
writes:
    *  Hello,
    *  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.

	........  Henry
Newsgroups: comp.lang.postscript
From: delahunt@adobe.com (Jim DeLaHunt)
Subject: Re: Postscript Font Scaling & Reduction
Summary: Hints are based on pixel height, not point size.
Organization: Adobe Systems Incorporated
Distribution: na
Date: Thu, 19 Nov 1992 17:48:00 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.

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.

>Chris Lewis; clewis@ferret.ocunix.on.ca; Phone: Canada 613 832-0541

	--Jim DeLaHunt, Developer Support, Adobe Systems Incorporated	
delahunt@mv.us.adobe.com  ...!{apple,decwrl}!adobe!delahunt    +1-415-962-3790
Newsgroups: comp.lang.postscript
From: Seokmin Ahn <smahn@vx.cis.umn.edu>
Subject: HELP: Looking for a Calligraphy like font
X-Xxmessage-Id: <A732850C3702C368@me51-3-104.me.umn.edu>
X-Xxdate: Fri, 20 Nov 92 12:05:32 GMT
Organization: University of Minnesota
X-Useragent: Nuntius v1.1.1d11
Date: Fri, 20 Nov 1992 18:03:22 GMT

Hi netters,

Would someone tell me a font name, which is similar to calligraphic
style font?

Thank you.
From: shri@unreal.cs.umass.edu (H.Shrikumar)
Newsgroups: comp.lang.postscript
Subject: Wanted s/w Simple Postscript Typesetting for Slides ...??
Date: 15 Nov 92 07:56:59 GMT
Reply-To: shri@unreal.cs.umass.edu (H.Shrikumar)
Organization: UMass, Amherst MA + Temporal Sys & Computer Networks Bombay India

Hi,

    I have written a small shell script that takes in lines of text and
outputs very generic postscript that will generate transparencies
suitable for a overhead projector. Nothing fancy, but it works. (One
header file selects a large font and setgray, prints the header and
footer procedure with logo, and prints the lines, end with showpage).

   ***************
   *   I wonder if there does not already exist a small and functional
   * postscript generating program that can be used to typeset simple
   * documents, or transparencies.  MS-DOS based please.
   ***************

  PLease E-mail shri@legato.cs.umass.edu ...as I am not a subscriber here.

Many thanx in advance for all pointers ...

-- shrikumar ( shri@legato.cs.umass.edu, shri@iucaa.ernet.in )

PS: I already have PC TeX, with dvips drivers .. but they are too
large, dont fit in my palmtop PC. A simple wordprocessor with
rudimentary PostScript support will do be ideal, but I am open to
all suggestions and pointers.
Organization: Arizona State University
Date: Tuesday, 17 Nov 1992 13:39:41 MST
From: Ben Goren <AUBXG@ASUACAD.BITNET>
Newsgroups: comp.lang.postscript
Subject: Re: Is there interest in comp.sources.postscript?
 <1992Nov10.231730.8716@cs.brown.edu> <4424@vidiot.UUCP>
 <3986@ecicrl.ocunix.on.ca>

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&
From: xcpslf@oryx.com (stephen l favor)
Subject: Postscript conformance checker
Organization: Oryx Energy Co., Dallas, Texas.
Date: Mon, 23 Nov 1992 21:04:19 GMT

Has anyone seen a program that tests for Postscript conformance.  I
have several programs that sometimes put out postscript code that
doesn't quite cut it, and I'd like something with which to check them
before I send them to the printer.

email please.

Thanks
Newsgroups: comp.lang.postscript
From: dave@maven.b29.ingr.com (Dave Bradford)
Subject: Lev 2 Image Dictionary Question
Reply-To: dave@maven.b29.ingr.com (Dave Bradford)
Organization: Intergraph Corporation, Huntsville, AL.
Date: Mon, 16 Nov 1992 23:12:18 GMT

I am trying to write a color raster level 2 PostScript driver
using run length encoding. My problem is that my data seems
to be interpreted as RGB, RGB, ... instead of:

RRRRRRRRRR
GGGGGGGGGG
BBBBBBBBBB

I figure that by separating the color components by scanline I
can get the most out of RLE encoding. I have been succesful
using the level 1 colorimage operator with true 3 (multiple
data source, 3 colors) but in the process of switching to 
level 2 and using the image dictionary and image filters I
have not had any luck.

Here is a sample of what I have tried (without compression):

initgraphics
/inch {72 mul} def
/width 300 def
/height 300 def
/finalwidth 1.00 inch def

/DeviceRGB setcolorspace
18 18 translate
finalwidth finalwidth width div height mul scale
/rline currentfile /ASCIIHexDecode filter def
/gline currentfile /ASCIIHexDecode filter def
/bline currentfile /ASCIIHexDecode filter def

gsave
<<
/ImageType 1
/Width width /Height height
/MultipleDataSources true
/BitsPerComponent 8
/Decode [0 1 0 1 0 1]
/ImageMatrix [width 0 0 height neg 0 height]
/DataSource [rline gline bline]
>>
image
....... data not included ......

Any help is very much appreciated.
-- 
Dave Bradford	dave@maven.b29.ingr.com      (Internet)

Newsgroups: comp.lang.postscript
From: jgm@cs.brown.edu (Jonathan Monsarrat)
Subject:  Problems printing Encapusulated PostScript files
Organization: Brown University Department of Computer Science
Date: Thu, 19 Nov 1992 13:36:17 GMT

> The specific parts that get altered are these carat (^) symbols
> that appear over other math symbols.  In the laser printout, the
> carat symbols have been turned into larger V's with serifs.

I ran into this problem myself recently.

When you use LaTeX it creates fonts from bitmaps and includes them
in the PostScript file directly.

When you use MacDraw or something, if you include text in the picture
then it will generally NOT do this. Instead it will use a PostScript
font. So if you select "GaramondBoldItalic" it will put a reference
to that font in the EPSF file.

But, what if your printer doesn't happen to have "GaramondBoldItalic" font?

GhostScript still runs it properly because you probably have the font
on-line and it knows where to look.

Your printer is probably substituting a different font, which is nice
I guess instead of just crashing with an error like some printers do.

I suggest using MacDraw and changing the text in your diagram to
something really normal and standard like Times-Roman.

Let us know if it works! Maybe I'm wrong on all this.

-Jon
Newsgroups: comp.lang.postscript
From: cjmchale@dsg.cs.tcd.ie (Ciaran McHale)
Subject: EPS files inside procedures or loops
Organization: DSG, Dept. of Computer Science, Trinity College Dublin
Date: Wed, 18 Nov 1992 21:08:23 GMT


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).

Comments, anyone?


Ciaran.
-- 
---- Ciaran McHale (cjmchale@dsg.cs.tcd.ie)
\bi/ Department of Computer Science, Trinity College, Dublin 2, Ireland.
 \/  Telephone: +353-1-7021539 FAX: +353-1-6772204
Newsgroups: comp.lang.postscript
From: wrp@pslsrv1.gvl.unisys.com (Bill Pringle)
Subject: Re: Help !!! Postscript in lps20!
Organization: Paramax Systems, Ivyland, PA
Date: Tue, 17 Nov 1992 03:29:00 GMT

In article <1992Nov16.161707.6451@sci.ccny.cuny.edu> paul@sci.ccny.cuny.edu (Paul Chen) writes:
>
>Some of PS files ( not all of them) can not be printed in our DEC
>lps20 printer, nut these PS files can be printed in QMS and HP 
>laser printer without any problems. The system didn't give us
>any error messages, may be we need more fonts? Most of PS files
>can be printed in lps20, only some of 'specail or complicated'
>PS files have problems to print.
>Any suggestions? How can I find out how may fonts do we have?
>Do we need to update our lps20 PS software?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
You might be exceeding some limit.  Try sending ehandler.ps (available
from the adobe file server or many other places) in front of the file.
The printer should produce a page with some error message for you.
============================================================================
Bill Pringle                      Software Tools
Paramax Corporation               Voice: (215)443-7500 X4023
Internet: wrp@ivy.unisys.com      UUCP: ...!uunet!mimsy!widener!gvls1!wrp%ivy
From: les@chinet.chi.il.us (Leslie Mikesell)
Subject: Postscript compression
Organization: Chinet - Public Access UNIX
Date: Sat, 21 Nov 1992 22:35:58 GMT

Until I get some kind of network link between a sysVr4 machine or
a PC to the Ethertalk on a fiery controller of a Xerox color
copier/printer, the only way to get postcript printed is to
put a file on a 1.4M floppy PC disk which it will accept.  The
problem is that lots of things I'd like to print are larger than
1.4M.  I sort of recall seeing some discussion of code that would
compress postscript and include postscript code to do the expansion
in the printer.  Is this a possibility?  Speed isn't an issue if
it lets me print illustrations that otherwise couldn't be done at all.

Les Mikesell
  les@chinet.chi.il.us
Newsgroups: comp.lang.postscript