From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: symbols in luatex?
Date: Sat, 5 Jan 2008 10:55:23 +0100 [thread overview]
Message-ID: <6faad9f00801050155u5f703672xe8a15b8fb570045a@mail.gmail.com> (raw)
In-Reply-To: <20080105100341.522b4d1d.schuster.wolfgang@googlemail.com>
On Jan 5, 2008 10:03 AM, Wolfgang Schuster wrote:
> On Fri, 04 Jan 2008 21:40:55 +0100
> Hans Hagen wrote:
>
> > Thomas A. Schmitz wrote:
> >
> > > {\bgroup\definedfont[name:TeXGyreHeros-Regular]\char"2329\egroup}
> >
> > ah so you know the number ...
> >
> > \getglyph{name:TeXGyreHeros-Regular}{\char"2329}
> >
> > should also work then
>
> Is it also possible to select glyphs with the "Adobe names", I saw you
> have a complete list char-def.lua and it would be nice to write
> \getnamedglyph{name:TeXGyreHeros-Regular}{angleleft} with the same
> result as above.
One thing that you can try is to add
contextname='angleleft'
to the corresponding entry in char-def.lua and then use
\getglyph{name:TeXGyreHeros-Regular}{\angleleft}
improvements for char-def.lua are welcome anyway.
Hans, should contextnames.txt be deleted now? So that only one list
will be kept up to date.
XeTeX offers \XeTeXglyphdindex{angleleft} (in LuaTeX you can achieve
the same with some coding), but I agree that some high-level macro to
access glyphs by name might be handy.
Mojca
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-01-05 9:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 11:26 Thomas A. Schmitz
2008-01-02 11:42 ` Hans Hagen
2008-01-02 13:04 ` Thomas A. Schmitz
2008-01-04 15:44 ` Thomas A. Schmitz
2008-01-04 16:15 ` Hans Hagen
2008-01-04 17:03 ` Thomas A. Schmitz
2008-01-04 17:39 ` Wolfgang Schuster
2008-01-04 20:30 ` Thomas A. Schmitz
2008-01-04 20:40 ` Hans Hagen
2008-01-04 21:17 ` Thomas A. Schmitz
2008-01-04 21:20 ` Hans Hagen
2008-01-04 22:17 ` Idris Samawi Hamid
2008-01-05 9:03 ` Wolfgang Schuster
2008-01-05 9:55 ` Mojca Miklavec [this message]
2008-01-06 9:15 ` Wolfgang Schuster
2008-01-06 10:32 ` Mojca Miklavec
2008-01-06 11:06 ` Wolfgang Schuster
2008-01-06 14:02 ` Mojca Miklavec
2008-01-06 20:26 ` Hans Hagen
2008-01-07 16:18 ` Wolfgang Schuster
2008-01-08 0:30 ` Mojca Miklavec
2008-01-08 0:49 ` luigi scarso
2008-01-08 8:21 ` Hans Hagen
2008-01-08 16:05 ` Wolfgang Schuster
2008-01-08 16:51 ` Idris Samawi Hamid
2008-01-05 9:00 ` Wolfgang Schuster
2008-01-05 11:14 ` Thomas A. Schmitz
2008-01-04 18:42 ` Hans Hagen
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=6faad9f00801050155u5f703672xe8a15b8fb570045a@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.com \
--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).