From: "Wolfgang Schuster" <schuster.wolfgang@googlemail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: symbols in luatex?
Date: Mon, 7 Jan 2008 17:18:03 +0100 [thread overview]
Message-ID: <115224fb0801070818q4311e846t48ceac0cd7994cc3@mail.gmail.com> (raw)
In-Reply-To: <4781397E.4030203@wxs.nl>
On Jan 6, 2008 9:26 PM, Hans Hagen <pragma@wxs.nl> wrote:
> Wolfgang Schuster wrote:
>
> > Do you really a contextname for every adobename in the list?
>
> no, in mkiv we can have use adobe names as well
>
> > I would be enough for me access the glyphs by name, I don't a macro for
> > every character but the list for adobenames should be filled with the
> > information from glyphlist.txt.
> >
> > http://www.adobe.com/devnet/opentype/archives/glyph.html
>
> taht's what char-def is for
>
> >> Hans, should contextnames.txt be deleted now? So that only one list
> >> will be kept up to date.
>
> well, we can keep it for a while for sentimental reasons
>
> >> 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.
> >
> > I know XeTeX offers this method but method for XeTeX and LuaTeX would
> > be better, it could be used as replacement for \symbol a many
> > cases, untill you have the requestet glyph in your font but a fallback
> > mode would be nice in this situation.
>
> maybe a big fallback virtual font covering all of unicode ...
With Arial Unicode as fallback ;-)
Wolfgang
___________________________________________________________________________________
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-07 16:18 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
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 [this message]
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=115224fb0801070818q4311e846t48ceac0cd7994cc3@mail.gmail.com \
--to=schuster.wolfgang@googlemail.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).