home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!agate!doc.ic.ac.uk!uknet!mucs!lucs!daves
- From: daves@csc.liv.ac.uk (Dave Shield)
- Newsgroups: comp.soft-sys.andrew
- Subject: Tables containing rasters
- Message-ID: <C0HtF9.4nz@compsci.liverpool.ac.uk>
- Date: 7 Jan 93 16:49:57 GMT
- Sender: news@compsci.liverpool.ac.uk (News Eater)
- Organization: Computer Science, Liverpool University
- Lines: 29
- Nntp-Posting-Host: irw.csc.liv.ac.uk
-
-
- We have been experiencing problems with printing tables where
- one of the cells contains a raster image (or any other inset
- that produces PostScript output directly).
- Rather than printing the raster, the final document appears
- with the _text_ of the PostScript instead.
-
- What appears to be happening is that table uses a troff
- diversion to hold the body of each row, to ensure that page
- breaks can occur when required. This means that the troff is
- processed twice - once for the diversion, and again when the
- macro is executed.
- The PostScript is protected by a single level of transparency,
- which is stripped off during the diversion. Hence, when the macro
- is executed, the PostScript is no longer passed through unchanged,
- and gets printed like everything else.
-
- This is all using DITroff. Groff does what you would expect
- (even though it technically shouldn't).
-
- Any ideas? (Other than 'use groff'!)
-
- Dave
- -------------------------------------------------------------------------------
- Dave Shield Janet: D.T.Shield@uk.ac.liverpool.compsci
- Dept. of Computer Science, I'net: D.T.Shield@compsci.liverpool.ac.uk
- Liverpool University, "I _order_ you to help!
- PO Box 147, You're a machine and you must do
- Liverpool, L69 3BX what you're told." T. Pratchett, _Diggers_
-