From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \activatespacehandler
Date: Fri, 10 Jun 2011 13:01:40 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.01.1106101259390.12373@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <alpine.LNX.2.01.1106101238110.12373@ybpnyubfg.ybpnyqbznva>
On Fri, 10 Jun 2011, Aditya Mahajan wrote:
> Hi,
>
> \activatespacehandler{on} does not work in MkIV. I guess that this is because
> \controlspace does not give the right glyph in MkIV, possibly because, in
> opentype fonts, \char 32 is the same as regular space.
>
> Any idea how to fix this? Is there a unicode character for visible space. A
> discussion on the xetex mailing list suggests
> http://www.tug.org/pipermail/xetex/2006-February/003095.html 0x2423, but that
> looks very different from \tt\char 32.
Actually, the relavant code is in enco-ini.mkiv. So the fix is to set
\def\controlspace{\fastcontrolspace}
in char-act.mkiv, or use \fastcontrolspace in spac-hor.mkiv
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2011-06-10 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 16:49 \activatespacehandler Aditya Mahajan
2011-06-10 17:01 ` Aditya Mahajan [this message]
2011-06-10 17:03 ` \activatespacehandler Khaled Hosny
2011-06-10 17:23 ` \activatespacehandler Arthur Reutenauer
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.01.1106101259390.12373@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).