MMAC@vax.oxford.ac.uk (The_Edible_Dormouse) (07/12/90)
A couple of queries came up from my posting of the draft postscript file so
here is a little clarification:
{\scriptsize clarification}
:-)
But seriously...
1) Make it lighter: look for the line
.80 setgray
and reduce the number there (scale is 0 to 1, with 1 being as black as your
laserprinter can get, black which is TRULY gray in my case, alas)
2) How to use it for more than one page: put
\special{draft.ps}
in a footer. I was using fancyheadings.sty and
\lfoot{\special{draft.ps}}
which seemd to work fine. To change the position on the page (I guess it
doesn't sit right on American 11"x9" paper) then change the line
80 100 moveto
as appropriate. It is moving from the place where the file is included, ie
bottom left if used in \lfoot so increasing the two values (x and y) moves it
across and up.
3) Other wps: well, the principal is that this draws the picture and you need
to persuade your wp to include it on every page. I guess that most wps offer
footers or headers and so it should be transprotable so long as your printer
speaks fluent postscript.
4) Underlay rather than overlay: this probably depends on which your printer
prints first. In fact making the word lighter will make it look like it
underlays the text I would think.
5) Anything following a % mark inthe file is a comment of course, just like in
TeX and LaTeX
Hope this is clearer now.
Edi
===============================================================================
MMAC@UK.AC.OX.VAX (Janet) = The opinions expressed above are
MMAC%VAX.OX.AC.UK@UKACRL.BITNET (Bitnet) = not necessarily those of any person
MMAC%VAX.OXFORD.AC.UK@NSS.CS.UCL.AC.UK = living, dead, undead or the subject
(Internet) = of a Schrodinger's cat experiment.
"Trust me I'm a Physicist !" = They may or may not be my own.
===============================================================================aglew@oberon.crhc.uiuc.edu (Andy Glew) (07/18/90)
I want to thank "The_Edible_Dormouse" [*] for his draft banner marking. I can also make some corrections (possibly due to printer differences) to his comments: >1) Make it lighter: look for the line >.80 setgray > >and reduce the number there (scale is 0 to 1, with 1 being as black as your >laserprinter can get, black which is TRULY gray in my case, alas) Using an Apple laserwriter, .00 is black. I am using .95, which is a very nice light gray. >2) How to use it for more than one page: put >\special{draft.ps} >in a footer. I was using fancyheadings.sty and >\lfoot{\special{draft.ps}} >which seemd to work fine. To change the position on the page (I guess it >doesn't sit right on American 11"x9" paper) then change the line > >80 100 moveto > >as appropriate. It is moving from the place where the file is included, ie >bottom left if used in \lfoot so increasing the two values (x and y) moves it >across and up. > >... > >4) Underlay rather than overlay: this probably depends on which your printer >prints first. In fact making the word lighter will make it look like it >underlays the text I would think. I guess the laserwriter prints the footer last, and overprints. I got underlay by moving the \special{draft-mark.ps} (note that I had to include the suffix in this TeX implementation) to a header rather than a footer. I changed the "80 100 moveto" to "80 -600 moveto", which, although not perfectly centered, is good enough for me. I'm using this in combination with fancyheadings and a munged version of drafthead.sty, so I get (1) date of printing, (2) a little box with the words draft at the top, in case I'm not on a postscript printer, and (3) the RCS $Header:$ string of my document, in various places in the header and footer. By the way, does anyone have a package that lets you organize the RCS strings of all your subdocuments in a useful way? Something like printing the RCS strings of all subdocuments visible on a page together in the header, along with a table of all the subdocument RCS strings in the history section? >I could quite get into this postscript lark --- much simpler than TeX :-) Yeah. It's a pity I don't have access to a text processor that accesses all the features of Postscript natively, rather than with the insulation that dvi provides. Flame-retardent: I don't mean programming in Postscript). [*] Have you ever met "der Mouse" from McGill? -- Andy Glew, aglew@uiuc.edu