diff options
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/faq-dvi.tex')
-rw-r--r-- | Master/texmf-dist/doc/generic/FAQ-en/faq-dvi.tex | 42 |
1 files changed, 24 insertions, 18 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-dvi.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-dvi.tex index 030a0452b1d..8df28bb2915 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-dvi.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-dvi.tex @@ -45,18 +45,20 @@ for any (then) imaginable kind of printer, but the steam seems rather to have gone out of the market for production of drivers for printer-specific formats. There are several reasons for this, but the primary one is that few formats offer the flexibility available -through \PS{}, and \ProgName{ghostscript} is \emph{so} good, and -has \emph{such} a wide range of printer drivers (perhaps this is where -the \acro{DVI} output driver writers have all gone?). - -The general advice, then, is to \Qref*{generate \PS{}}{Q-dvips}, and -to process that with \ProgName{ghostscript} set to generate the format -for the printer you actually have. If you are using a Unix system of -some sort, it's generally quite easy to insert \ProgName{ghostscript} -into the print spooling process. -\begin{ctanrefs} -\item[ghostscript]Browse \CTANref{ghostscript} -\end{ctanrefs} +through \PS{}, and with +\href{http://www.ghostscript.com/}{\ProgName{ghostscript}} (and its +huge range of printer drivers) there is now little demand for new +printer driver development. + +Thus, it is reasonable to \Qref*{generate \PS{}}{Q-dvips}, and +use \href{http://www.ghostscript.com/}{\ProgName{ghostscript}} to send +the resulting \PS{} output to the printer you actually have. + +(If you are using a Unix system of some sort, it's generally quite +easy to insert +\href{http://www.ghostscript.com/}{\ProgName{ghostscript}} into the +print spooling process, which makes printing \emph{really} simple.) +\LastEdit{2013-05-29} \Question[Q-previewers]{\acro{DVI} previewers} @@ -81,7 +83,9 @@ Alternatives to previewing include \Qref[question]{converting to \acro{ASCII}}{Q-toascii}) and using a conventional text viewer to look at that, \item generating a \PS{} version of your document and viewing it - with a \ProgName{Ghostscript}-based previewer (see + with a + \href{http://www.ghostscript.com/}{\ProgName{ghostscript}}-based + previewer (see \Qref[question]{previewing \PS{} files}{Q-PSpreview}), and \item generating \acro{PDF} output, and viewing that with \ProgName{Acrobat} \ProgName{Reader} or one of the substitutes for that. @@ -89,6 +93,7 @@ Alternatives to previewing include \begin{ctanrefs} \item[xdvi]\CTANref{xdvi} \end{ctanrefs} +\LastEdit{2013-04-11} \Question[Q-dvi-bmp]{Generating bitmaps from \acro{DVI}} @@ -115,11 +120,12 @@ PowerPoint, or to support the enhanced-\ProgName{emacs} setup called \Qref*{\ProgName{preview}-\ProgName{latex}}{Q-WYGexpts}. In the past, the commonest way of generating bitmaps was to generate a -\PS{} file of the \acro{DVI} and then use \ProgName{ghostscript} to +\PS{} file of the \acro{DVI} and then use +\href{http://www.ghostscript.com/}{\ProgName{ghostscript}} to produce the required bitmap format (possibly by way of \acro{PNM} format or something similar). This is an undesirable procedure (it is -very slow, and requires two or three steps) but it has served for a -long time. +tedious, involving requires two or three steps that run slowly) but it +served for a long time. \AllTeX{} users may now take advantage of two bitmap `drivers'. The longer-established, \ProgName{dvi2bitmap}, will generate \acro{XBM} and @@ -128,7 +134,7 @@ now obsolescent, but has finally been relieved of the patent protection of the \acro{LZW} compression it uses), and also the modern (\acro{ISO}-standardised) \acro{PNG} format. -Dvipng started out as a PNG renderer; from version 1.2 it can also +\ProgName{Dvipng} started out as a PNG renderer; from version 1.2 it can also render to the GIF format. It is designed for speed, in environments that generate large numbers of \acro{PNG} files: the \File{README} mentions \ProgName{preview}-\ProgName{latex}, \ProgName{LyX}, and a few @@ -139,4 +145,4 @@ for speed. \item[dvi2bitmap]\CTANref{dvi2bitmap} \item[dvipng]\CTANref{dvipng} \end{ctanrefs} - +\LastEdit{2013-04-19} |