From: Hans Hagen <pragma@wxs.nl>
To: Sanjoy Mahajan <sanjoy@MIT.EDU>, ntg-context@ntg.nl
Subject: Re: internal mptopdf converter skips some glyphs in labels
Date: Thu, 05 Jun 2014 10:04:06 +0200 [thread overview]
Message-ID: <53902476.3080803@wxs.nl> (raw)
In-Reply-To: <878upccd6h.fsf@approx.mit.edu>
On 6/5/2014 4:17 AM, Sanjoy Mahajan wrote:
> Hans Hagen <pragma@wxs.nl> writes:
>
>>> This is with Context 2013.05.28 00:36 MKIV (TL2013 on Debian).
>>
>> the beta works ok .. are there any messages with respect to missing
>> fonts or map files?
>
> FYI, with recent betas (2014.05.17 from a context standalone or
> 2014.05.21 from Debian TL2014), I still find the problem with the
> internal mptopdf converter dropping glyphs. I work around it in the
> Makefile (convert using mptopdf externally). However, in case it is
> worth tracking down, here is the original report with the minimal
> example.
you see the message:
LuaTeX warning (file cmr10): Font cmr10 at 3000 not found
so you need to load a map file that matches the used fonts:
\loadmapfile[mkiv-base]
> ==================
>
> The internal mptopdf converter in MkIV omits some glyphs in the labels.
> Here's a minimal example (test.tex):
>
> \starttext
>
> \externalfigure[testfig.1][frame=on]
> \blank
> \externalfigure[testfig-1.pdf][frame=on]
>
> \stoptext
>
> And testfig.1 is produced by testfig.mp
>
> beginfig(1)
> label(btex $\Omega$ etex, (0,0));
> currentpicture := currentpicture scaled 5;
> endfig;
> end
>
> Here's testfig.1 to save a step in debugging:
>
> %!PS
> %%BoundingBox: -18 -18 18 18
> %%HiResBoundingBox: -17.98805 -17.0195 17.98798 17.0195
> %%Creator: MetaPost 1.803
> %%CreationDate: 2013.08.09:1612
> %%Pages: 1
> %*Font: cmr10 49.81323 9.96265 0a:8
> %%BeginProlog
> %%EndProlog
> %%Page: 1 1
> 0 0 0 setrgbcolor
> -17.98805 -17.0195 moveto
> (\012) cmr10 49.81323 fshow
> showpage
> %%EOF
>
> Then do:
>
> mptopdf testfig.1
> context test.tex
> xpdf test.pdf
>
> The first framed box, using the internal mps->pdf conversion, is empty.
> The second framed go, using the pdf file produced by mptopdf, correctly
> contains \Omega.
>
> ==================
>
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2014-06-05 8:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 20:26 Sanjoy Mahajan
2013-08-09 20:41 ` Aditya Mahajan
2013-08-09 23:50 ` Sanjoy Mahajan
2013-08-10 0:09 ` Aditya Mahajan
2013-08-09 21:50 ` Hans Hagen
2013-08-09 23:45 ` Sanjoy Mahajan
2014-06-05 2:17 ` Sanjoy Mahajan
2014-06-05 8:04 ` Hans Hagen [this message]
2014-06-05 19:37 ` Sanjoy Mahajan
2014-06-05 20:25 ` Hans Hagen
2014-06-05 21:27 ` Sanjoy Mahajan
2014-06-05 23:19 ` Hans Hagen
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=53902476.3080803@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=sanjoy@MIT.EDU \
/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 NNTP newsgroup(s).