From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \lgroup in mkIV
Date: Sat, 8 Jan 2011 14:59:35 -0500 (EST) [thread overview]
Message-ID: <alpine.LNX.2.01.1101081452510.30494@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <20110108193509.GB4122@khaled-laptop>
On Sat, 8 Jan 2011, Khaled Hosny wrote:
> On Sat, Jan 08, 2011 at 12:52:38PM -0500, Aditya Mahajan wrote:
>> On Sat, 8 Jan 2011, Daniel Schopper wrote:
>>
>>> Hi,
>>> are the delimiters \lgroup and \rgroup supported in MkIV?
>>> This
>>>
>>> \starttext
>>> $$\bigg\lgroup\dots\bigg\rgroup$$
>>> \stoptext
>>>
>>> is ok in MkII (ConTeXt ver: 2011.01.06) but when compiled with
>>> MkIV (ConTeXt ver: 2010.07.30 11:35 and ver: 2010.07.30 11:35) the
>>> delimiters are not shown. (By the way, the same holds true for
>>> \rmoustache and \lmoustache.)
>>
>>> Am I missing something?
>>
>> No. The math mappings of virtual fonts are incomplete. The symbols
>> should work correctly with unicode math fonts like cambria, asana,
>> and xits. But, it appears that lgroup and rgroup are missing from
>> xits (Khaled?)
>
> There are, but context is looking for the wring character; it is looking
> for U+3014 (which I think is a CJK bracket and does not look like
> \lgroup either) while it should be looking for U+27EE (whose Unicode
> annotation precisely says "lgroup"):
Hmm ... 27EE does not exist: http://unicode.org/charts/PDF/U32-27C0.pdf
I believe that I used 3014 based on
http://www-sop.inria.fr/apics/tralics/doc-l.html#cmd-lgroup
What source do you use for the symbols?
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-01-08 19:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-08 15:09 Daniel Schopper
2011-01-08 17:52 ` Aditya Mahajan
2011-01-08 19:35 ` Khaled Hosny
2011-01-08 19:47 ` Khaled Hosny
2011-01-08 19:59 ` Aditya Mahajan [this message]
2011-01-08 20:08 ` Arthur Reutenauer
2011-01-09 0:45 ` Aditya Mahajan
2011-01-08 20:25 ` Khaled Hosny
2011-01-08 23:30 ` Aditya Mahajan
2011-01-09 1:13 ` Arthur Reutenauer
2011-01-09 18:44 ` Khaled Hosny
2011-01-09 18:59 ` Aditya Mahajan
2011-01-09 19:58 ` Khaled Hosny
2011-01-09 19:58 ` Mojca Miklavec
2011-01-09 21:15 ` Hans Hagen
2011-01-09 21:14 ` Hans Hagen
2011-01-08 20:29 ` Arthur Reutenauer
2011-01-09 18:48 ` Khaled Hosny
2011-01-09 3:24 ` Aditya Mahajan
2011-01-10 18:28 ` Khaled Hosny
2011-01-10 23:43 ` Daniel Schopper
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.1101081452510.30494@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).