From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Differences for \Vert in mkii and mkiv
Date: Wed, 19 Jan 2011 11:44:58 -0500 (EST) [thread overview]
Message-ID: <alpine.LNX.2.01.1101191140100.31800@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <91C8082E-FAD3-4E24-B856-F7D3A45C7FE1@gmail.com>
On Tue, 18 Jan 2011, Otared Kavian wrote:
> Dear Aditya, dear Hans,
>
> I noticed a serious difference between what one gets for \left\Vert in mkii and in mkiv.
> Probably this is due to the fact that in mkiv the glyph for \Vert is constructed in a different manner, but as far as I know from what I see in the mathematical printed materials, the correct one, or the expected one, is the output from mkii.
I don't know why the glyphs are different. In MkIV, the virtual font is
mapping 0x2016 to 0xFF605, but I don't know how FF605 is created.
> Is there a way to redefine locally \Vert (or \|) so that in mkiv one gets the same output as with mkii?
Not locally. You could change math-vfu.lua to change the mapping, but I
don't completely understand how those work (with the virtual glyphs like
FF605)
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-01-19 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 15:04 Otared Kavian
2011-01-19 16:44 ` Aditya Mahajan [this message]
2011-02-02 9:12 ` Otared Kavian
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.1101191140100.31800@ybpnyubfg.ybpnyqbznva \
--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).