From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug in mkiv math mode: missing \longrightarrow
Date: Sun, 07 Jun 2009 12:56:03 +0200 [thread overview]
Message-ID: <4A2B9CC3.2000302@wxs.nl> (raw)
In-Reply-To: <684A6FC2-1CDF-48E6-B14D-B72BD4B718A5@gmail.com>
Otared Kavian wrote:
>
> On 5 juin 09, at 14:38, Aditya Mahajan wrote:
>
>> On Fri, 5 Jun 2009, Otared Kavian wrote:
>>> […]
>>> In mkiv nothing appears for \longrightarrow, although the typesetting
>>> goes through.
>>
>> Currently, \longrightarrow (and few other composed symbols) only work
>> with unicode fonts (cambria and asana math). We need to figure out a
>> clean way to deal with composed symbols in mkiv.
>>
>> Aditya
>
> Thanks Aditya, I understand.
> Should I gather such bugs in a file and submit it later, without
> cluttering the mailing list with each of them?
that would help
also, it would be nice to have a collection of test files (the same for
structure)
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2009-06-07 10:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 8:08 Otared Kavian
2009-06-05 12:38 ` Aditya Mahajan
2009-06-05 17:51 ` Otared Kavian
2009-06-07 10:56 ` Hans Hagen [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=4A2B9CC3.2000302@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).