From: Adam Lindsay <atl@comp.lancs.ac.uk>
Subject: Re: \bar missing in euler
Date: Tue, 11 Jul 2006 13:51:25 +0100 [thread overview]
Message-ID: <44B39ECD.1040707@comp.lancs.ac.uk> (raw)
In-Reply-To: <44B3629A.1070107@wxs.nl>
Hans Hagen wrote:
> Aditya Mahajan wrote:
>> I do not know what is the equivalent of 'operators' family in context.
>> Any idea how to pull them out of the text fonts?
>>
> if this is only euler, we may use something
I believe this is euler only. The other math fonts I have dug into have
been "complete."
> euler:ec
Makes sense. I'll look at the new definitions you just sent.
On the "user" side, what do you imagine it would look like:
\definetypeface [e] [mm] [math] [euler] [euler] [encoding=ec]
or
\definetypeface [e] [mm] [math] [euler] [euler] [encoding=euler:ec]
or
\starttypescript [math,boldmath] [euler] [ec] # with the first one
\usemathcollection[euler:ec]
\stoptypescript
?
> otherwise we end up with all other math encodings being messed up
Yes, and that's the last thing I'd want to happen because of euler support.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Adam T. Lindsay, Computing Dept. atl@comp.lancs.ac.uk
Lancaster University, InfoLab21 +44(0)1524/510.514
Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2006-07-11 12:51 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
2006-07-11 8:32 ` Hans Hagen
2006-07-11 8:34 ` Hans Hagen
2006-07-11 12:51 ` Adam Lindsay [this message]
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=44B39ECD.1040707@comp.lancs.ac.uk \
--to=atl@comp.lancs.ac.uk \
--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).