ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
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: Fri, 06 Jun 2014 01:19:36 +0200	[thread overview]
Message-ID: <5390FB08.2020602@wxs.nl> (raw)
In-Reply-To: <8738fjavy4.fsf@approx.mit.edu>

On 6/5/2014 11:27 PM, Sanjoy Mahajan wrote:
> Hans Hagen <pragma@wxs.nl> writes:
>
>> Alternatively, you can consider making your mp graphics like this:
>>
>> \startMPpage
>>     some code
>> \stopMPpage
>>
>> This will use the regular font system, gives access to everything
>> context as well, and makes it possible to opentype fonts. The resulting
>> (cropped) graphic can of course be included. One can also have more of
>> them:
>
> That's an improvement on what I am doing.  (Though I may be getting lots
> of ConTeXt and OpenType fonts, by using a preamble with
>
>    verbatimtex %&cont-en
>    ...
>    etex
>
> )

I must admit that I never use verbatimtex (nor btex/etex).

> Right now my figure source (blah.mpfig, say) is what would go in between
> begin/endfig.  The Makefile wraps it in begin/endfig, and includes a
> header.mp with all the definitions hopefully consistent with the main
> document's environment (terrible, I know), writes out blah.mp, which is
> run through metapost and mptopdf.

Including environments and styles is easier when you run the mp graphic 
as context file. Just \environment ... will do.

> The disadvantage of incorparating everything into the .tex may be the
> edit--compile cycle gets much longer for the figures, because you have
> to compile the whole document or component to see the revised figure.
> (My rule of thumb is that typing is about 10 times faster than
> handwriting, unless one has to do equations, in which case you lose a
> factor of 3; or if you have to make figures, in which case you lose the
> other factor of 3 (3^2=10), and maybe more.)

That is only true if you can produce content at high speed -) Otherwise 
the ratio typing - thinking - making up text etc is not that good.

Are you sure' it's 'much' longer? You can still put graphics in external 
files, or use \useMPgraphic etc ... Running mp in context (luatex) is 
pretty fast (esp when your viewer refreshes fast too). And when at some 
point you want to use the new lua extension in mp you can only run it 
that way.

Hans

-----------------------------------------------------------------
                                           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
___________________________________________________________________________________


      reply	other threads:[~2014-06-05 23:19 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
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 [this message]

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=5390FB08.2020602@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).