Ralf Stubner <ralf.stubner@web.de> wrote:
> The teTeX packages ship 10tetex-base.cfg and 20tetex-extra.cfg while,
> eg, lmodern ships 10lmodern.cfg. I have seen that you have meanwhile
> implemented a variable priority with 10 being the default.
The reasons lmodern uses 10 are:
1) 10lmodern.cfg sorts after 00updmap.cfg (and doesn't cause any
problem I am aware of).
2) This is what was recommended in update-updmap(8) and
/usr/share/doc/tetex-bin/README.Debian.gz before I got involved in
this stuff. You can see that in sarge's files.
> Before discussing a suitable default value, I think I have to ask a
> (maybe stupid) question first: What is the use of these priorities? Or,
^^^^^^^^^^^^^
Not at all!
> in other words, to what extend does the order in updmap.cfg matter.
> There is an interesting comment about this in the TeX policy:
>
> <footnote>
> Note that in <file>texmf.cnf</file>, as well as in the
> sequence of multiple <file>texmf.cnf</file> files that are
> read, earlier entries override later ones.
> <!-- Check what happens in fmtutil.cnf and updmap.cnf -->
> </footnote>
>
> So let's see, to what extend order is relevant in updmap.cfg. With
I think updmap.cfg and .cnf files in teTeX have completely different
syntaxes, and trying to infer things from what you read on the latter
won't help you understand the former...
> respect to configuration values (LW35, dvipsPreferOutline, ...) I find
> in updmap:
>
> # cfgval(variable)
> # read variable ($1) from config file, first match wins
>
> Here order is important. Configuration values are in 00updmap.cfg,
> which will normally come first. This is fine.
Good that you found that in the code.
> Overall, I see no reason for specifying a priority for files in
> /etc/texmf/updmap.d, as long as they only install further mapfiles. So I
> would suggest $priority="" as default. But I might be missing something.
I'm not sure I understand your '$priority=""'. If it means "let
dh_installtexfonts choose the default recommended in the Debian TeX
Policy (that should be added once clearly decided!)", perfect (unless an
option to override the priority is provided). If it means "install
/etc/texmf/updmap.d/lmodern.cfg" by default (for instance), I don't
agree. All font map files should have the same two-digits number
prepended IMHO, unless we discover that some of them need an exception.
This will make things tidy in /etc/texmf/updmap.d/ and the resulting
order in updmap.cfg should be obvious by simply running ls in
/etc/texmf/updmap.d/ (unless using a strange LC_COLLATE, but who would?
update-updmap uses LC_COLLATE=C and sort, to make sure things behave as
expected).
[ With what I suggest, dh_installtexfonts won't have to deal with the
priority at all, anyway, but this is still worth discussing so that
everyone knows why $WHATEVER ends up in the TeX Policy. ]
OK, so which number should be used? Given that update-updmap(8) and
/usr/share/doc/tetex-bin/README.Debian.gz have been giving 10 as an
example for a long time, I'd say this should be the recommended value in
the TeX Policy, unless there is a good reason to use something else
(such as "not enough space between 00 and 10"). Otherwise, the package
maintainers who had done their homework well will have to transition
their conffiles to some other name. Pffff! :)
> Concerning 'Map' vs 'MixedMap'. Since I don't have sid in my
> sources.list, I still have cm-super version 0.3.3-6 installed. There
> 50cm-super.cfg contains only:
>
> Map cm-super-t1.map
>
> IMO it would be better to use MixedMap, since Metafont versions are
> available and the local admin might want to use them. In addition, there
> are several mapfiles missing. Something like
>
> MixedMap cm-super-t1.map
> MixedMap cm-super-ts1.map
> MixedMap cm-super-t2a.map
> MixedMap cm-super-t2b.map
> MixedMap cm-super-t2c.map
> MixedMap cm-super-x2.map
>
> might be better.
That is exactly what I had the last time cm-super was in my sid chroot
(locally installed, way before the debian package).
--
Florent