From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Ampersand in Metapost
Date: Fri, 14 May 2010 15:32:30 +0200 [thread overview]
Message-ID: <4BED50EE.2030808@wxs.nl> (raw)
In-Reply-To: <alpine.LNX.2.00.1005132106200.16359@ybpnyubfg.ybpnyqbznva>
On 14-5-2010 3:07, Aditya Mahajan wrote:
>> 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?
>
> You can also try \noexpand\letterampersand
The problem is that some definitions, likt \& and \# expand to letters
which is needed when used in mp itself. That also means that resetting
them to their normal meaning is not possible as textext is handled in mp
and then already an \& has become a &.
As & is rather common, I added it to \nonknuthmode, so you can say:
\nonknuthmode
\starttext
\startMPcode
draw textext("Underscores, Superscripts & Ampersands" & "?") ;
\stopMPcode
\stoptext
Aditya: I also changed the definition of \_ in math ... it now looks
better when used in script(scripts) .. see \fakeunderscore.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-05-14 13:32 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
2010-05-14 13:32 ` Hans Hagen [this message]
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=4BED50EE.2030808@wxs.nl \
--to=pragma@wxs.nl \
--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).