Ralf Stubner <[EMAIL PROTECTED]> wrote:
>>> dvipdfm allready links against libpaper.
>>
>> Err, right. We probably should disable "texconfig dvidpdfm paper",
>> then.
>
> ACK
Hm, no. Actually things are more complicated, and I'm not sure whether
this is a good idea: dvipdfm reads both the libpaper setting and the
setting in its config file, and the config file overrides the system
setting. In other words, with the default tetex-bin install with
% Set default paper size here
p a4
in /usr/share/texmf-tetex/dvipdfm/config/config, the libpaper setting
has no effect, it's a4 all the time. Just for reference, here's the
code from dvipdfm.c:
{
rect paper_size = get_paper_size (systempapername (), 0);
if (paper_size.width != 0) {
paper_width = paper_size.width;
paper_height = paper_size.height;
}
}
/* Process config file, if any */
/* yes, in Debian there are two: config and an additional fontmaps file */
read_config_file("config");
read_config_file("fontmaps");
do_args (argc, argv);
and read_config_file has this comment:
/* Build up an argument list as if it were passed on the command
line */
>>> For dvips I currently see no
>>> possibility to have one configuration file specify another one, that
>>> should also be read.
>>
>> Will it read multiple config files, e.g. in TEXMFSYSVAR and
>> TEXMFSYSCONFIG/TEXMFDIST?
>
> I don't now, but I would be surprised if it does.
Debian has patched dvipdfm to read two config files: config and
fontmaps. I guess this is now unnecessary and predates updmap support
for dvipdfm. But we could add a papersize file instead.
Regards, Frank
--
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
