T.R | Title | User | Personal Name | Date | Lines |
---|
473.1 | Not any more | WRONGO::PARMENTER | Venusian or Venerean? | Fri Jun 05 1987 15:38 | 6 |
| DVI used to stand for "device independent" and it still would if
our supported devices all used the same fonts. But they don't,
so you are bumping up against vestigial nomenclature.
David Parmenter
|
473.2 | Are they ever independent? | TOKLAS::FELDMAN | PDS, our next success | Fri Jun 05 1987 16:07 | 15 |
| Are there any cases where a single DVI_XXX file can be used for
more than one destination, merely by running DOCUMENT/NOTAG/NOTEXT?
(Ignore the case where a final result file can run on more than
one printer, such as LN03 files on LPS40's.)
For that matter, I'll settle for any cases where I can get away
with not having to run the TAG phase to get a different destination?
My motivation is a) I'm running on a VAXstation; and b) I have to
distribute documents to a review board, some of whom insist on
machine-readable, while others prefer hardcopy postscript, while
still others might prefer postscript but only have LN03's. I'm
forced to run Document multiple times, which gets to be frustrating.
Gary
|
473.3 | | CLOSET::ADLER | | Fri Jun 05 1987 16:24 | 7 |
| You can always get away with not rerunning the TAG phase to get a different
destination (provided you /KEEP the .TEX file). However, the only time you
can get away with not rerunning /TEXT is if you have a .DVI_LINE file and
want to generate output for TERMINAL, MAIL, and LINE destinations; that's
because those are the only three destinations that share the same fonts.
--Brian
|
473.4 | must use same doctype | CLOSET::ANKLAM | | Mon Jun 08 1987 10:07 | 14 |
|
To clarify .3 a big: You can always rerun using /NOTAG, provided:
1. You specified /KEEP to keep the .TEX file from the original
run
2. You use the same document type when you process the file.
In other words, the following may cause errors in the text formatter:
$ DOCUMENT myfile REPORT LN03/KEEP=TEX
$ DOCUMENT/NOTAG myfile LETTER POSTSCRIPT
-pa
|
473.5 | it's device-independent, but not device-universal | VAXUUM::DEVRIES | Those are features, not bugs | Mon Jun 08 1987 13:51 | 14 |
| And to pick up on the less significant point: the DVI file is still
"device independent" in its syntax; it does not speak the specific
formatting language of any known device.
It is possible to write a device converter that can map the fonts
used in the document to other fonts available, say, on the workstation.
Some previewers and <prototype> online-documentation book readers
have been known to work this way.
But for high-quality output, you must format the document using
the real font metrics of the target device -- and we've built VAX
DOCUMENT for high-quality output.
Mark
|