Bug#263410: map files
Hilmar Preusse <hille42@web.de> wrote:
>> > Can you give an example and/or an explanation on what to do with
>> > the map files?
Excuse me, I didn't point out clearly enough how ignorant I am - so I
had to find out myself in the dvips manual: If a line looks like
pmnr8r Minion <<Minion.pfb
instead of
pmnr8r Minion <Minion.pfb
then the font will be put into the file completely. This can be achieved
on an all-or-none basis with the -j0 switch to dvips, and probably
similarly for pdftex/dvipdfm, but on a per-font-basis it can only be
changed in the map files, it seems.
>> Hilmar, would you please take the time and elaborate on this? I hit
>> this question again while working on the current teTeX beta, and I
>> would be glad if we could decide on this soon.
>>
> For this point you could downgrade this bug to wishlist. I can't
> imagine any reason, why one would like to include the whole font into
> an PS/PDF file. However, the fact that this is configurable in the
> map file makes me think that map file are config files and hence
> should sit in /etc.
On the one hand, I am not completely convinced - for many man files in a
TEXMF tree one can imagine some circumstances where changing it to
effect a "local customization" is "needed". Are we going to put
hyphenation patterns below /etc, or color.pro or t1enc.def?
On the other hand, there are historical reasons to treat map files as
configuration files.
So if we put them under /etc/texmf, I must say I object to putting them
below /etc/texmf/dvips. They are also configuration files for pdftex and
other dvi-to-something drivers. And after all, updmap in tetex-2.96
spits out lots of errors with the old setup, because the map files are
now no longer located in $TEXMF/dvips/$fontname/, but in
$TEXMF/fonts/map/{dvips,...}/$fontname. If we keep them in
/etc/texmf/dvips, we need to create symlinks from the TEXMF directories
to the actual files there. But then, also $TEXMF/dvips/config is a
symlink to /etc/texmf/dvips because of files in there, and then updmap
complains about "Obsolete Map file found in ..." and exits with an
error.
Suggestion: If we put map files below /etc/, then they should go into
/etc/texmf/maps, or something like that.
Fr'I still don't know...'ank
--
Frank Küster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie
Reply to: