auctex
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [AUCTeX] strange behaviour of dvipdfmx and xdvipdfmx in Emacs


From: 军其 胡
Subject: Re: [AUCTeX] strange behaviour of dvipdfmx and xdvipdfmx in Emacs
Date: Sun, 11 Jun 2017 17:17:27 +0800

Thank you, Keita.

> I tried the example above on TeXLive 2017 of FreeBSD, with a symbolic
> link rose1.eps -> /usr/local/share/ghostscript/9.16/examples/tiger.eps.
> However, dvipdfmx complains as:
> ---------------------------------------------------------------------
> sam1.dvi -> sam1.pdf
> [1
> kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 gbk51
> mktexpk: don't know how to create bitmap font for gbk51.
> mktexpk: perhaps gbk51 is missing from the map file.
> kpathsea: Appending font creation commands to missfont.log.
> 
> dvipdfmx:warning: Could not locate a virtual/physical font for TFM "gbk51".
> dvipdfmx:warning: >> There are no valid font mapping entry for this font.
> dvipdfmx:warning: >> Font file name "gbk51" was assumed but failed to locate 
> that font.
> dvipdfmx:fatal: Cannot proceed without .vf or "physical" font for PDF 
> output...
> 
> Output file removed.
> ----------------------------------------------------------------------
> even on terminal.  It seems that my system lacks the necessary font.
> (Perhaps masOS has the relavant font by default?)

You are right. sam1.tex could work if some configurations on ttf2pk, font maps 
for CJK fonts, etc, should be set up. You could just try the second example by 
using XeLaTeX.

> 
> So I can tell only very slightly about this topic, but I guess that the
> culprit on your side is the error message
>> Unable to read environment locale:exit now.
> 
> This message appears also on your log of the second example like this:
>> [1] (./sam2.aux)Unable to read environment locale:exit now.
> 
> Thus my current guess is that these issues are related to locale.  Maybe
> emacs fails to tell dvipdfmx the information about the current locale?
> I know nothing about how macOS treats locale, but anyway, iTerm.app and
> emacs treat locale differently and that leads to the problems you
> described, I think.
> 
>> I can't figure out what happened. The configurations of Emacs is preserved 
>> during the upgrading process of MacTeX.
> 
>> Any suggestion?
> 
> I recommend to contact people with deeper knowledge about treatment of
> locale in emacs on macOS and show the logs to them.

Maybe, you are also right. Let me try it by google firstly.


---
Best regards,

Jun-Qi Hu

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail


reply via email to

[Prev in Thread] Current Thread [Next in Thread]