summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/latex/graphics/grfguide.tex
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/latex/graphics/grfguide.tex')
-rw-r--r--Master/texmf-dist/doc/latex/graphics/grfguide.tex112
1 files changed, 53 insertions, 59 deletions
diff --git a/Master/texmf-dist/doc/latex/graphics/grfguide.tex b/Master/texmf-dist/doc/latex/graphics/grfguide.tex
index fc35793960b..193282900b9 100644
--- a/Master/texmf-dist/doc/latex/graphics/grfguide.tex
+++ b/Master/texmf-dist/doc/latex/graphics/grfguide.tex
@@ -11,12 +11,12 @@
\begin{filecontents*}{a.ps}
%!
%%BoundingBox:0 0 72 72
-100 100 moveto
+0 0 moveto
72 72 rlineto
72 neg 0 rlineto
72 72 neg rlineto
stroke
-100 100 moveto
+0 0 moveto
/Times-Roman findfont
72 scalefont
setfont
@@ -168,8 +168,8 @@ startxref
%% Just as an example, and to make sure, in case some
%% driver option has not declared a default rule for
%% .ps files:
-\DeclareGraphicsRule{.ps}{eps}{.ps}{}
-\DeclareGraphicsExtensions{.pdf,.ps}
+%\DeclareGraphicsRule{.ps}{eps}{.ps}{}
+%\DeclareGraphicsExtensions{.pdf,.ps}
%% Which means:
%% .ps files are (to be treated as) EncapsulatedPostScript
%% files. The .ps file is to be read for the BoundingBox.
@@ -190,7 +190,7 @@ startxref
\begin{document}
\title{Packages in the `graphics' bundle}
\author{D. P. Carlisle \and The \LaTeX3 Project}
-\date{2016/05/22}
+\date{2016/12/23}
\maketitle
@@ -210,69 +210,66 @@ even the internal method of accessing these extensions varies between
drivers. Consequently all these packages take options such as
`|dvips|' to specify which driver is being used.
-You should to set up a site default for these
-options, for the driver that you normally use. Suppose that you wish for
+Normally you should \emph{not} specify the driver option explicitly
+in the document, but allow it to be defaulted automatically.
+This allows the document to be portable between different systems.
+
+Your \TeX\ distribution should have included |graphics.cfg| and
+|color.cfg| configuration files to specify these defaults.
+Standard versions of the configuration files are maintained by the
+\LaTeX\ Project and distributed in the CTAN |graphics-cfg| collection.
+
+For special requirements you may edit a copy of these |cfg| files
+to set up a site default for these options. Suppose that you wish
the \package{color} package to always default to use specials for the
-PostScript driver, |dvipsone|. In that case create a file |color.cfg|
+PostScript driver, |dvisvgm|. In that case, create a file |color.cfg|
containing the line:\\
-|\ExecuteOptions{dvipsone}|\\
+|\ExecuteOptions{dvisvgm}|\\
Normally you will want an identical file |graphics.cfg| to set a similar
default for the graphics packages.
The following driver options are declared in the packages.
+The matching definition files (\emph{driver}|.def|)
+are now also maintained by the \LaTeX\ project,
+but distributed separately, in the CTAN |graphics-def| collection.
\begin{quote}\raggedright
- |dvips|, |xdvi|, |dvipdf|, |dvipdfm|, |dvipdfmx|, |pdftex|,
- |dvipsone|, |dviwindo|, |emtex|, |dviwin|, |pctexps|, |pctexwin|,
- |pctexhp|, |pctex32|, |truetex|, |tcidvi|, |vtex|, |oztex|,
- |textures|, |xetex|
+ |dvipdfmx|, |dvips|, |dvisvgm|, |luatex|, |pdftex|, |xetex|
\end{quote}
-Note that the \LaTeX\ Team does not maintain these drivers; we merely
-provide a way for a particular driver to work with the graphics
-packages.
-If you use a driver that is not in the list above you may add an option
-for that driver by putting the appropriate |\DeclareOption| line into
-|graphics.cfg| and |color.cfg|, before making it the default option
-with |\ExecuteOptions|, as described above.
-For example to add the option `|dvi2ps|' for the original Unix dvi to
-ps driver, and to make that the default, you just need configuration
-files looking like:
-\begin{verbatim}
-\DeclareOption{dvi2ps}{\def\Gin@driver{dvi2ps.def}}
-\ExecuteOptions{dvi2ps}
-\end{verbatim}
+The following two options are also supported, they do not correspond
+to separate definition files, but are essentially aliases for the
+|dvips| option (and |monochrome| in the case of |xdvi|).
+\begin{quote}\raggedright
+ |xdvi|, |oztex|
+\end{quote}
-There is a suitable |dvi2ps.def| file in the standard distribution.
-It is not enabled by default as it is not well tested as the driver is
-no longer available to me. The following driver files are similarly
-distributed but not enabled by default.
+The following set of options are supported by these packages
+with associated driver files extracted from the |drivers.dtx|
+documented source in this bundle. These are now, mainly of historic
+interest but the documented sources do contain some useful code
+and advice if you need to produce a new definition file for a new
+driver or \TeX\ system. |drivers.dtx| also contains documented
+sources for older driver files that are no longer extracted.
\begin{quote}\raggedright
- |dvi2ps|, |dvialw|, |dvilaser|, |dvitops|, |psprint|, |pubps|, |ln|
+ |dvipdf|, |dvipdfm|, |dviwin|, |dvipsone|,
+ |emtex|, |pctexps|, |pctexwin|, |pctexhp|, |pctex32|,
+ |truetex|, |tcidvi|, |vtex|
\end{quote}
-Most of these driver files are generated from the source file
-|drivers.dtx|. That file has the sources for other versions (for
-example older versions of dvips and textures) which are not generated
-by default.
-
-Different \TeX\ systems support different drivers and the drivers are
-usually maintained by the developers of the \TeX\ variants or
-post-processors. Hence they are always linked to some program and
-since the \TeX\ distributors decide which programs they support, it is
-up to them to make sure the necessary drivers are included with their
-distribution. The graphics bundle contains the installation file
-|graphics-drivers.ins| which can be used to extract drivers from
-|drivers.dtx| but we cannot guarantee that these are up to date. Not
-all of the aforementioned drivers are available in |drivers.dtx| (some
-like |pdftex| and |dvipdfm| can be found on CTAN).
-
-If you use a driver that is not covered by any of these possibilities,
-you may try to write a |.def| file by analogy with one of the existing
-ones, and then specify a suitable option in |graphics.cfg| and
-|color.cfg|, as for the above example of |dvi2ps|.
-
-\section{Colour}
+The final driver option is an alias for |dvipsone|.
+\begin{quote}\raggedright
+ |dviwindo|
+\end{quote}
+
+
+\section[Colour]{Colour\footnote{%
+The basic \package{color} package functionality described here
+will be enough for many uses, however a much extended version
+is available in the contributed \package{xcolor} package, distributed
+and maintained separately. All the color commands described here are
+also available if you specify \package{xcolor} in your document.}%
+}
The colour support is built around the idea of a system of
\emph{Colour Models}. The Colour models supported by a driver vary,
but typically include
@@ -796,11 +793,8 @@ the \LaTeXe\ primitive |\input@path|. A list of directories, each in a
|{}| group (even if there is only one in the list). For example:\\
|\graphicspath{{eps/}{tiff/}}|\\
would cause the system to look in the subdirectories |eps| and |tiff|
- of the current directory. This is unix syntax, on a Mac it would be:\\
- |\graphicspath{{:eps:}{:tiff:}}|\\
- Note the differing conventions, an initial |:| is needed on Macintosh
- systems to denote the current folder, whereas on unix an initial |/|
- would denote the top level `root' directory.
+ of the current directory. (All modern \TeX{} systems use |/|
+ as the directory separator, even on Windows.)
The default setting of this path is
|\input@path| that is: graphics files will be found wherever \TeX\