From: Marco <netuse@lavabit.com>
To: ntg-context@ntg.nl
Subject: Re: Ampersand in Metapost
Date: Fri, 14 May 2010 12:09:43 +0200 [thread overview]
Message-ID: <20100514120943.6a1395ce@vorbis> (raw)
In-Reply-To: <alpine.LNX.2.00.1005132106200.16359@ybpnyubfg.ybpnyqbznva>
> > - label(textext("\letterbackslash\letterampersand"),origin);
> > - label(textext("\letterbackslash\&"),origin);
> >
> > This is because the commands are interpreted with TeX before they
> > are written to mpgraph.mp. The \letterampersand or \& generates the
> > character & alone: you need to preceed it with backslash, so that
> > metapost finally knows what to do.
>
> So, should all the \letter... commands (basically anything generated
> from char-def.lua) be unexpandable?
What are the disadvantages of unexpandable commands? I'm not an expert.
Why is this not done by default if it works better?
> You can also try \noexpand\letterampersand
Produces compile error.
Marco
___________________________________________________________________________________
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:[~2010-05-14 10:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 19:18 Marco
2010-05-13 20:58 ` Hans Hagen
2010-05-13 21:40 ` Mojca Miklavec
2010-05-13 21:45 ` Marco
2010-05-13 22:37 ` Mojca Miklavec
2010-05-14 1:07 ` Aditya Mahajan
2010-05-14 10:09 ` Marco [this message]
2010-05-14 13:32 ` Hans Hagen
2010-05-14 10:06 ` Marco
2010-05-14 10:39 ` Hans Hagen
2010-05-14 10:44 ` Hans Hagen
2010-05-14 11:45 ` Marco
2010-05-14 12:17 ` Hans Hagen
2010-05-14 15:20 ` Mojca Miklavec
2010-05-14 19:34 ` Marco
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=20100514120943.6a1395ce@vorbis \
--to=netuse@lavabit.com \
--cc=ntg-context@ntg.nl \
/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).