From: Aditya Mahajan <adityam@umich.edu>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
'Taco Hoekwater' <taco@elvenkind.com>
Subject: Re: MnSymbol in ConText
Date: Mon, 7 Mar 2011 18:57:41 -0500 (EST) [thread overview]
Message-ID: <alpine.LNX.2.01.1103071857000.8535@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <4D7568ED.1070307@wxs.nl>
On Tue, 8 Mar 2011, Hans Hagen wrote:
> On 7-3-2011 7:32, Aditya Mahajan wrote:
>> On Mon, 7 Mar 2011, Steffen Wolfrum wrote:
>>
>>>
>>> Am 07.03.2011 um 17:31 schrieb C.:
>>>
>>>>
>>>>> sure, if you cook up the definition for the virtualization (if the
>>>> encoding is
>>>>> default tex it's no big deal, otherwise some extra tables are
>>>>> needed) ...
>>>>
>>>> Since I don't even know how to check the encoding of a font - let alone
>>>> creating/changing it - I must pass on this one.
>>>> Can someone with more background on the subject have a look?
>>>
>>> Same for me ... but it would be nice to learn these things!
>>> Can someone explain what is needed and how to start?
>>
>> I must confess that I no longer understand how the math virtual fonts
>> work are implemented. I understood how things worked a year ago (see the
>> tugboat article for details), but I have not been able to keep up with
>> all the internal rearrangements.
>
> Don't worry, it didn't really change that much. The most important change is
> that font specific definitions moved to the lfg files
Ah... that is why I could not search for them :)
Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-03-07 23:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 0:26 C.
2011-02-19 0:57 ` Arthur Reutenauer
2011-02-19 9:30 ` Mojca Miklavec
2011-02-20 19:30 ` Florian Wobbe
2011-02-20 19:38 ` Khaled Hosny
2011-02-20 20:01 ` Florian Wobbe
2011-02-21 8:05 ` Taco Hoekwater
2011-02-23 10:59 ` C.
2011-02-23 11:37 ` Wolfgang Schuster
2011-02-23 14:04 ` C.
2011-03-07 16:51 ` Mojca Miklavec
2011-03-05 13:58 ` Steffen Wolfrum
2011-03-05 21:41 ` Hans Hagen
2011-03-07 16:31 ` C.
2011-03-07 16:44 ` Steffen Wolfrum
2011-03-07 18:32 ` Aditya Mahajan
2011-03-07 23:23 ` Hans Hagen
2011-03-07 23:57 ` Aditya Mahajan [this message]
2011-03-07 17:20 ` Wolfgang Schuster
2011-03-07 18:41 ` Florian Wobbe
2011-03-07 21:21 ` C.
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=alpine.LNX.2.01.1103071857000.8535@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.nl \
--cc=taco@elvenkind.com \
/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).