Sign up ×
TeX - LaTeX Stack Exchange is a question and answer site for users of TeX, LaTeX, ConTeXt, and related typesetting systems. It's 100% free, no registration required.

When compiling this MWE with MiKTeX 2.9’s xelatex, I get the following warning:

** WARNING ** Couldn't open font map file "".

The compilation runs through, no problems, but it bugs me that I get this message every time. It seems to come from Windows and not from xelatex, because it doesn’t appear in the log file, only in the command line. Here is the full command line output:

C:\Users\doncherry\Documents\LaTeX>xelatex bar.tex
This is XeTeX, Version 3.1415926-2.5-0.9999.3 (MiKTeX 2.9)
entering extended mode
Babel  and hyphenation patterns for english, ancientgreek, french, germa
n, german-x-2013-05-26, greek, italian, latin, ngerman, ngerman-x-2013-05-26, r
ussian, spanish, swissgerman, ukenglish, usenglishmax, loaded.
("C:\Program Files (x86)\MiKTeX\2.9\tex\latex\base\article.cls"
Document Class: article 2007/10/19 v1.4h Standard LaTeX document class
("C:\Program Files (x86)\MiKTeX\2.9\tex\latex\base\size10.clo"))
(C:\Users\doncherry\Documents\LaTeX\bar.aux) [1]
(C:\Users\doncherry\Documents\LaTeX\bar.aux) )
** WARNING ** Couldn't open font map file "".

Output written on bar.pdf (1 page).
Transcript written on bar.log.

There are a few similar questions here, but none of them apply to this specific situation:

Is there any way I can get rid of this warning? (Not just silence it, but cure the cause)

share|improve this question
You need a (an empty, dummy map is quite ok) or you should change the dvipdfmx.cfg. – Ulrike Fischer Sep 16 '13 at 14:36
@UlrikeFischer Thanks! I should’ve checked the bugs first ... Feel free to add an answer! – doncherry Sep 16 '13 at 15:44

2 Answers 2

up vote 12 down vote accepted

You need a (an empty, dummy map is quite ok) or you should change the dvipdfmx.cfg.

share|improve this answer
Would you mind exlain in more details how I can change dvipdfmx.cfg? Or where should I create a – newbie Oct 7 '13 at 16:52
@newbie You can create an empty file "" in your editor and place it in your working directory. – Ramaprakasha Oct 9 '13 at 11:23
@Ramaprakasha Thanks! That works... but I would be even more awesome if I could understand why. – Shashank Sawant Sep 15 '14 at 3:42
This bug report explains you everything. – Ramaprakasha Sep 16 '14 at 10:11

Note: The file dvipdfmx.cfg shouldn't be edited directly due to Miktex updating will repaire the file, but do the followings instead.

  1. Open a Windows Command Line prompt and input initexmf --edit-config-file dvipdfmx, press Enter.
  2. Append this line to the end of the opened file.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.