[tex-live] Warning of xelatex

Ulrike Fischer news3 at nililand.de
Tue Oct 6 12:41:31 CEST 2009

Am Tue, 6 Oct 2009 18:22:02 +0800 schrieb Steven Woody:

>>> Hi,
>>> I am running xelatex on cygwin against some of my old tex articles
>>> that are UTF-8 encoding and written in Chinese.   In the past, when I
>>> was using texlive 2008 windows version, there is no such warnings.
>>> The warning lines are as below:
>>> ------------
>>> Package hyperref Warning: Rerun to get /PageLabels entry.
>>> [1] [2] [3] (./tt.aux)
>>> ** WARNING ** Invalid char in fontmap line: f
>>> ** WARNING ** Invalid map record in fontmap line 3077 from pdftex.map.
>>> ** WARNING ** -- Ignore the current input buffer: labm3583 SFBM3583 "T2AEncoding
>>>  ReEncodeFont" <cm-super-t2a.enc <sfbm3583.pft frummt <frummt.pfb
>>>  )
>> The map entry looks a bit curious
>> "labm3583" to "sfbm3883.pft" is from a cm-super map which ends with
>> sfbm3583.pfb (and not pft).
>> and the "frummt < frummt.pfb" looks as if it has creeped in from
>> another map but it is missing the first "frummt".
>> My guess is that the "t" at the end of pft is in reality the end of
>> the missing "frummt".
>> So probably something did go wrong with updmap(-sys). You could try
>> to run updmap(-sys) with the option verbose to see if it use some
>> faulty maps or if there are other messages.
>> Make sure to run the correct updmap(-sys)!
> I think I only get one updmap executable.  And, running of the updmap
> (not the -sys version) will give me an error:

I meant you should run either updmap or updmap-sys what-ever you are
doing normally (mixing both leds in general to chaos).

> updmap: Scanning for MixedMap entries:
> updmap: using map file `/usr/local/texlive/2009/texmf-dist/fonts/map/dvips/allru
> nes/allrunes.map'
> !!! ERROR! The map file `arabtex.map' has not been found at all.
> Any clue?
> I am about to do some fix as the updmap suggested: run a updmap
> --syncwiththrees.  I am not sure what will be the result, and I am
> also afraid I will be covering something.

First: don't be afraid. The worst that can happen is that you get a
second set of map files or a faulty updmap.cfg. Both can be
corrected quite easily manually. 

Second: Yes try the --syncwithtrees. If this doesn't help check at
first if the pdftex.map with the faulty entry is actually the one
written by updmap (which should be by your log in

Then check the updmap.cfg mentioned in the log and try if the
problem disappears if you remove the map entries for arabtex.map

Ulrike Fischer 

More information about the tex-live mailing list