From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Font switch \x does not work
Date: Wed, 13 May 2009 18:20:58 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.00.0905131820210.6207@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <alpine.LNX.2.00.0905131810240.6207@ybpnyubfg.ybpnyqbznva>
On Wed, 13 May 2009, Aditya Mahajan wrote:
> On Thu, 14 May 2009, Vyatcheslav Yatskovsky wrote:
>
>> Hello,
>>
>> Font switching described in sec.5.3 of the manual, does not work in mkiv.
>>
>> {\x some text }
>>
>> ! Undefined control sequence.
>> l.48 {\x
>> some text }
>> ?
>> ! Emergency stop.
>
> This has been removed from mkiv. There was a discussion about it a few weeks
> back which concluded with a suggestion that we should have a compatibility
> module for mkiv. I guess we should start filling in m-mkii.mkiv.
>
> Hans, here is a version that takes care of \x, etc.
which should be surrounded by \unprotect and \protect.
Aditya
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2009-05-13 22:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.771.1242244554.3589.ntg-context@ntg.nl>
2009-05-13 19:59 ` fonts --list --info Vyatcheslav Yatskovsky
2009-05-13 21:18 ` Font switch \x does not work Vyatcheslav Yatskovsky
2009-05-13 21:24 ` Hans Hagen
2009-05-13 22:14 ` Aditya Mahajan
2009-05-13 22:20 ` Aditya Mahajan [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=alpine.LNX.2.00.0905131820210.6207@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--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).