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>
Cc: Herbert Voss <Herbert.Voss@FU-Berlin.DE>
Subject: Re: space in \longrightarrow in lucida (mkiv)
Date: Sat, 04 Dec 2010 09:41:04 +0100	[thread overview]
Message-ID: <4CF9FEA0.9080809@wxs.nl> (raw)
In-Reply-To: <4CF8F4E3.9070207@FU-Berlin.DE>

On 3-12-2010 2:47, Herbert Voss wrote:
> Am 03.12.2010 12:21, schrieb Mojca Miklavec:
>>> IIRC, the original definitions are from plain.tex and amstex.tex.
>>
>> plain.tex says:
>>      \def\joinrel{\mathrel{\mkern-3mu}}
>>
>> So I guess that \joinrel indeed needs to be defined on per-font basis
>> instead of being hardcoded into definitions.
>
> the macro \loadfontgoodies in font-gds.mkiv should be extended
> to something like
>
> \def\loadfontgoodies[#1]%
>    {\ctxlua{fonts.goodies.get("#1")}%
>     \InputIfExists #1.tex%
>    }
>
> which already load a lucida-math.ldf (lua code)
> and then an optional lucida-math.tex (tex code)
>
> don't know how ConTeXt can handle the \InputIfExists
> The file lucida-math.tex in /context/fonts/
> gets all font specific redefinitions, in this case
>
> \def\joinrel{\mkern-4mu}
> \def\longrightarrow{\relbar\joinrel\rightarrow}
> \def\longleftarrow{\leftarrow\joinrel\relbar}
> ....
>
> sich files are then possible for all other fonts

in mkii we had math vectors and one could have many different vectors 
active at the same time (so, lucida alongside lm and others); in mkiv we 
assume unicode math

I can probably make something for mkiv but the question is: is it worth 
the trouble and complication. Eventually all these math fonts will be 
open type anyway.

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2010-12-04  8:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30 16:54 Mojca Miklavec
2010-11-30 17:23 ` Herbert Voss
2010-11-30 18:16   ` Hans Hagen
2010-12-03 10:42     ` Mojca Miklavec
2010-12-03 10:47       ` Mojca Miklavec
     [not found]         ` <AANLkTi=bKYMwYi=aX06mC92LuNeHXnjLkmzgm2T58D1A@mail.gmail.com>
     [not found]           ` <alpine.LNX.2.01.1012030617310.22938@ybpnyubfg.ybpnyqbznva>
     [not found]             ` <AANLkTikVXeEeS=fPqn6M31bHHNuqjJF=+wEMnyQEJjhp@mail.gmail.com>
2010-12-03 13:47               ` Herbert Voss
2010-12-04  8:41                 ` Hans Hagen [this message]
2010-12-04 18:38                 ` Hans Hagen
2010-12-05 11:16                   ` Mojca Miklavec

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=4CF9FEA0.9080809@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=Herbert.Voss@FU-Berlin.DE \
    --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).