Thank you for replying.

> Now that I've looked at this more closely, I'm not sure your suggestion is the right thing to do.  I don't see anything like it in a native TeX Live installation.  Please send me a complete, detailed recipe for reproducing your problem so that I can investigate further.

I see and agree:

The file usr/share/texmf-dist/dvipdfmx/dvipdfmx.cfg is the same as it
was in the previous package, and we didn't need such modifications.
So, maybe something wrong... or not...


Anyway, how to reproduce the situation:

echo '\documentclass{jsarticle}\begin{document}\char\euc"A4A2\end{document}'| platex -jobname test; dvipdfmx test

And we'll get:

> This is e-pTeX, Version 3.14159265-p3.7-160201-2.6 (utf8.euc) (TeX Live 2016/Cygwin) (preloaded format=platex)
>  restricted \write18 enabled.
> **entering extended mode
> pLaTeX2e <2016/11/29> (based on LaTeX2e <2017/01/01> patch level 3)
> Babel <3.9r> and hyphenation patterns for 83 language(s) loaded.
> (/usr/share/texmf-dist/tex/platex/jsclasses/jsarticle.cls
> Document Class: jsarticle 2017/03/05 okumura, texjporg
> (/usr/share/texmf-dist/tex/platex/jsclasses/jslogo.sty))
> No file test.aux.
> [1] (./test.aux)
> Output written on test.dvi (1 page, 256 bytes).
> Transcript written on test.log.
> test -> test.pdf
> [1
> kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 0+555/600 --dpi 555 rml
> mktexpk: don't know how to create bitmap font for rml.
> mktexpk: perhaps rml 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 "rml".
> dvipdfmx:warning: >> There are no valid font mapping entry for this font.
> dvipdfmx:warning: >> Font file name "rml" was assumed but failed to locate that font.
> dvipdfmx:fatal: Cannot proceed without .vf or "physical" font for PDF output...
> 
> Output file removed.

But we'd expect a result like attached test.pdf:
a japanese hiragana character 'a' in a page.

--
Lemures Lemniscati


==
Subject: Re: Please enable cid-x.map in dvipdfmx.cfg when installing texlive-langjapanese
Date: Sun, 7 May 2017 20:29:20 -0400
From: Ken Brown <kbrown@cornell.edu>

> On 5/7/2017 9:37 AM, Ken Brown wrote:
> > On 5/6/2017 8:17 PM, Lemures Lemniscati wrote:
> >> Hi!
> >>
> >> I've just updated with the latest packages texlive-*-20170412-1,
> >>
> >> Thank you for maintaining and updating TeX Live for cygwin.
> >>
> >> When we use dvipdfmx with Japanese fonts, we might encounter warnings/fatal:
> >>
> >>> dvipdfmx:warning: Could not locate a virtual/physical font for TFM "gbm".
> >>> dvipdfmx:warning: >> There are no valid font mapping entry for this font.
> >>> dvipdfmx:warning: >> Font file name "gbm" was assumed but failed to locate >>> that font.
> >>> dvipdfmx:fatal: Cannot proceed without .vf or "physical" font for PDF output...
> >>
> >> To avoid them, we'd need this change:
> >>
> >> --- /usr/share/texmf-dist/dvipdfmx/dvipdfmx.cfg    2017-05-07
> >> 08:00:30.790411600 +0900
> >> +++ /usr/share/texmf-dist/dvipdfmx/dvipdfmx.cfg    2017-05-05 >> 06:03:31.000000000 +0900
> >> @@ -215,7 +215,7 @@
> >>  %f psfonts.map
> >>
> >>  %% Put additional fontmap files here (usually for Type0 fonts)
> >> -%f  cid-x.map
> >> +f  cid-x.map
> >>
> >>  % the following file is generated by updmap(-sys) from the
> >>  % KanjiMap entries in the updmap.cfg file.
> >>
> >> But the file 'usr/share/texmf-dist/dvipdfmx/dvipdfmx.cfg' is packaged in
> >> texlive-collection-basic-20170412-1.tar.xz
> >>
> >>
> >> So please put some codes like this into
> >> 'etc/postinstall/texlive-collection-langjapanese.sh'
> >> if it doesn't cause unwanted effects.
> >>
> >>
> >> cp /usr/share/texmf-dist/dvipdfmx/dvipdfmx.cfg \
> >>    /usr/share/texmf-dist/dvipdfmx/dvipdfmx.cfg.orig
> >> sed -e 's/^\%f  cid-x\.map/f  cid-x\.map/' \
> >>    /usr/share/texmf-dist/dvipdfmx/dvipdfmx.cfg.orig \
> >>  > /usr/share/texmf-dist/dvipdfmx/dvipdfmx.cfg
> >>
> >>
> >> And we might need a preremove script for reverting the change...
> > > Thanks for the report.  I'll fix this for the next release.
> 
> Now that I've looked at this more closely, I'm not sure your suggestion is the right thing to do.  I don't see anything like it in a native TeX Live installation.  Please send me a complete, detailed recipe for reproducing your problem so that I can investigate further.
> 
> Ken
> 
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple