On Mon, Jun 04, 2007 at 10:45:40PM +0200, Jean-Marc Lasgouttes wrote:
> >>>>> "Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes:
>
> Herbert> these are _all_ config files and not printer files.
>
> Herbert> dvips -P<config>
>
> Herbert> eg dvips -Pcmz <file>
>
> In the old days, it was not about brand new fonts, but rather metafont
> modes. Typical case, besides the known problem of DPI setting:
> write-white and write-black printers can produce fonts that are too
> thin/thick. This is well documented in the modes.mf file.
I also question the assertion that the -P option is not for printer
settings. This is an excerpt from the dvips man page:
-P printername
Sets up the output for the appropriate printer. This
is implemented by reading in config.printername , which
can then set the output pipe (as in, !lpr -Pprintername
as well as the font paths and any other config.ps
defaults for that printer only. Note that config.ps is
read before config.printername In addition, another
file called ~/.dvipsrc is searched for immediately
after config.ps; this file is intended for user
defaults. If no -P command is given, the environment
variable PRINTER is checked. If that variable exists,
and a corresponding configuration file exists, that
configuration file is read in.
> I am not sure however that this is still relevant with 600+ dpi
> printers. And of course, metafont is getting less and less used.
Not all TeX fonts are available in vector format, so I would say
that this is still relevant if you have two or more printers with
different resolutions.
--
Enrico
