From: Aditya Mahajan <adityam@umich.edu>
Subject: Re: \bar missing in euler
Date: Thu, 6 Jul 2006 11:53:43 -0400 (EDT) [thread overview]
Message-ID: <Pine.WNT.4.63.0607061146160.2660@nqvgln> (raw)
In-Reply-To: <44AD2DBB.2080908@comp.lancs.ac.uk>
On Thu, 6 Jul 2006, Adam Lindsay wrote:
> Aditya Mahajan wrote:
>
>> gives just "a". I do not get any bar over "a".
>
> Yup. You seem to be the first to have noticed (or complained), as well.
>
>> This is how eulervm.sty defines these characters for T1 encoding.
>> ...
>
> That's the key, though, it apparently pulls in the text accents as well,
> and changes the math definitions depending on the text encoding. That
> seems rather opposite to how ConTeXt *should* work.
>
>> I do not know what is the equivalent of 'operators' family in context.
>> Any idea how to pull them out of the text fonts?
>
> Let's open this up to Hans and Taco: any idea? Much of the finer points
> of \definemathsymbol et al are voodoo to me.
>
> The fourth/sixth arguments of \definemathsymbol insist on a (hex) number
> to be in that slot. Anything else (like \textmacron) is a no-go.
>
> So right now, Euler is limited by the math mechanisms/the encoding of
> the font. I can imagine two "solutions" of differing hack-ish natures:
>
> 1) Allow further expansion in \definemathsymbol:
> \definemathsymbol [breve] [accent] [tf] [\textbreve]
>
> 2) Do a hack following LaTeX's imperfect lead:
> \definemathsymbol [breve] [accent] [tf] ["15] % for texnansi
> % or
> \definemathsymbol [breve] [accent] [tf] ["08] % for ec
> etc.
I have no knowledge of how Context's font stuff works. The first
definition looks better to me, as one would not need to worry about
the encoding while defining symbols (one needs to worry about the
encoding while defining \textbreve etc, anyway). Though the second
does have the advantage that it works right away, so there is no need
to change the definition of \definemathsymbol.
Right now I will use
\definemathsymbol [bar] [accent] [tf] ["09]
which seems to work with my present setup.
Thank you.
Aditya
next prev parent reply other threads:[~2006-07-06 15:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 13:54 Aditya Mahajan
2006-07-06 15:35 ` Adam Lindsay
2006-07-06 15:53 ` Aditya Mahajan [this message]
2006-07-11 8:32 ` Hans Hagen
2006-07-11 8:34 ` Hans Hagen
2006-07-11 12:51 ` Adam Lindsay
2006-07-11 13:03 ` Hans Hagen
2006-07-21 21:59 ` Aditya Mahajan
2006-09-12 22:34 ` Aditya Mahajan
2006-09-13 0:00 ` Hans Hagen
2006-09-13 1:32 ` Aditya Mahajan
2006-09-14 19:59 ` Hans Hagen
2006-09-15 6:40 ` Taco Hoekwater
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=Pine.WNT.4.63.0607061146160.2660@nqvgln \
--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).