ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \rightarrow missing?
Date: Fri, 10 Apr 2009 09:19:44 +0200	[thread overview]
Message-ID: <49DEF310.5090708@wxs.nl> (raw)
In-Reply-To: <m2d4bls4pp.fsf@stanford.edu>

Jesse Alama wrote:
> I switched from MkIV to MkII today because of this gap in MkIV's math:
> I need to submit a dissertation that has \rightarrow's in it.  Let's
> hope that this issue is resolved soon.
> 
> Jesse
> 
> Alan BRASLAU <alan.braslau@cea.fr> writes:
> 
>> Indeed, it seems to be broken in mkiv
>> \rightarrow
>> \to
>> \leftarrow
>> ...
>>
>> However, \leftrightarrow works.
>>
>> So, currently, it is hard to typeset limits under mkiv!
>>
>> Alan
>>
>>
>> On Tuesday 31 March 2009 09:14:16 Hans Hagen wrote:
>>> Aditya Mahajan wrote:
>>>> On Mon, 30 Mar 2009, Jesse Alama wrote:
>>>>> It seems that \rightarrow is missing.  The command exists, in the sense
>>>>> that its use doesn't lead to an error, but it doesn't lead to anything
>>>>> in the output.  Minimal example:
>>>>>
>>>>> \starttext
>>>>> $\rightarrow$
>>>>> \stoptext
>>>> Hans,
>>>>
>>>> What does the new arrow function in math-vfu.lua supposed to do?
>>> it will be used instead of the macro based one (as luatex has native
>>> support for such extenders now) but i had to wait till you fixed all the
>>> other arrows that you added someplace

in math-vfu, patch:

--~     main.characters[unicode] = { horiz_variants = t }
     main.characters[unicode].horiz_variants = t

and

[0x02190] = 0x20, -- leftarrow
[0x02192] = 0x21, -- rightarrow
--~ [0xFE190] = 0x20, -- leftarrow
--~ [0xFE192] = 0x21, -- rightarrow

and remake the format

luatex has native support for extensible arrows and since lm lacks them 
we need to construct them

Hans

-----------------------------------------------------------------
                                           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
___________________________________________________________________________________


  reply	other threads:[~2009-04-10  7:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-30 20:51 Jesse Alama
2009-03-31  1:00 ` Aditya Mahajan
2009-03-31  7:14   ` Hans Hagen
2009-04-09 20:21     ` Alan BRASLAU
2009-04-09 22:22       ` Aditya Mahajan
2009-04-10  1:00       ` Jesse Alama
2009-04-10  7:19         ` Hans Hagen [this message]
2009-04-10  7:32           ` Alan BRASLAU
2009-04-10 13:48           ` Aditya Mahajan
2009-04-10 17:15         ` Mohamed Bana
2009-04-10 17:19           ` Aditya Mahajan

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=49DEF310.5090708@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).