ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: Zhichu Chen <zhichu.chen@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Hans Hagen <pragma@wxs.nl>
Subject: Re: Math in MKIV - HOWTO
Date: Tue, 2 Mar 2010 16:56:06 +0100	[thread overview]
Message-ID: <6faad9f01003020756o7689c85fif309687352214f17@mail.gmail.com> (raw)
In-Reply-To: <769ba7781003020741k5d8104e2tf71f3b9aa70b67d1@mail.gmail.com>

On Tue, Mar 2, 2010 at 16:41, Zhichu Chen wrote:
> On Tue, Mar 2, 2010 at 11:23 PM, Mojca Miklavec wrote:
>
>> It's not about messing things up, but about missing "mathname=" in
>> char-def.lua for all the unicode entries for special glyphs. If those
>> glyphs worked in MKII from the very beginning, they won't work before
>> one adds several entries to
>>
>> But of course they should work flawlessly when they are entered as
>> unicode characters. They only fail to work when one enters
>> \zrangeantirestriction for example.
>
> I'm sorry, this is just my comment from the unicode chart. I'm pretty sure
> that won't work. I download the chart, compare the symbols in the tables
> one by one without even knowing the meanings. Is there like a table of
> macros of all symbols?

a) Take a look at lucidabr.sty (inside lucidabr.zip from CTAN). That's
the source for names of glyphs used in LaTeX for Lucida.

b) The Comprehensive LaTeX Symbol List
c) \showmathcharacters in MKII
d) any other font with extensive glyph repertoaire

Mojca

PS: F3 looks very similar to 226D, but it's not exactly that. And
there are plenty of other such characters.
___________________________________________________________________________________
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-03-02 15:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-22 23:02 Math in MKIV - HOWTO (was: Lucida Fonts with MKIV) Mojca Miklavec
2010-02-24  3:15 ` Zhichu Chen
2010-02-24  9:01   ` Math in MKIV - HOWTO Hans Hagen
2010-02-24 10:24     ` Hans Hagen
2010-02-24 11:55       ` Zhichu Chen
2010-02-24 12:24         ` Hans Hagen
     [not found]           ` <6faad9f01002240427l7da7a675r4ec6805f6f7455ba@mail.gmail.com>
2010-03-01 16:26             ` Zhichu Chen
2010-03-01 17:07               ` Zhichu Chen
2010-03-02 10:45               ` Hans Hagen
2010-03-02 11:25                 ` Zhichu Chen
2010-03-02 11:34                   ` Hans Hagen
2010-03-02 13:49                 ` Mojca Miklavec
2010-03-02 14:28                   ` Hans Hagen
2010-03-02 15:23                     ` Mojca Miklavec
2010-03-02 15:41                       ` Zhichu Chen
2010-03-02 15:56                         ` Mojca Miklavec [this message]
     [not found] <mailman.510.1267129043.26807.ntg-context@ntg.nl>
2010-02-25 23:39 ` Vyatcheslav Yatskovsky

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=6faad9f01003020756o7689c85fif309687352214f17@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.nl \
    --cc=zhichu.chen@gmail.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).