public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Please enable cid-x.map in dvipdfmx.cfg when installing texlive-langjapanese
Date: Sun, 07 May 2017 15:05:00 -0000	[thread overview]
Message-ID: <e95c012f-1c60-ad11-57b4-bd30008468dd@cornell.edu> (raw)
In-Reply-To: <20170507091726.C00B.50F79699@gmail.com>

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.

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

  reply	other threads:[~2017-05-07 13:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-06 10:26 [ANNOUNCEMENT] TeX Live 2016 collections Ken Brown
2017-05-07  0:17 ` Please enable cid-x.map in dvipdfmx.cfg when installing texlive-langjapanese Lemures Lemniscati
2017-05-07 15:05   ` Ken Brown [this message]
2017-05-08  5:42     ` Ken Brown
2017-05-08 14:23       ` Lemures Lemniscati via cygwin
2017-05-08 16:19         ` Ken Brown
2017-05-09  6:17           ` Lemures Lemniscati
2017-05-09 13:21             ` Lemures Lemniscati
2017-05-09 15:52               ` Ken Brown
2017-05-10 11:30                 ` Lemures Lemniscati
2017-05-07  3:47 ` [ANNOUNCEMENT] TeX Live 2016 collections Eliot Moss
2017-05-07  9:56   ` Eliot Moss

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e95c012f-1c60-ad11-57b4-bd30008468dd@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).