From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: (RSFS) font installation
Date: Tue, 22 Mar 2011 17:55:23 +0100 [thread overview]
Message-ID: <4D88D47B.7010702@elvenkind.com> (raw)
In-Reply-To: <AANLkTikbT7iFJN38X2sX0Y3JwXKF7W_ceOUpPygqJ6dJ@mail.gmail.com>
Hi,
On 03/22/2011 05:08 PM, mathew wrote:
> {\getnamedglyphdirect{dingbats}{0x272a}}
this won't do anything unless the glyph's *name* in the font is
actually 0x272a, which is unlikely (in my version of the ghostscript
font, the name of ✪ is "a37").
> Or here's the character directly: ✪
This does not work for two reasons: First, you have defined a typeface
dingbats, but have not switched to it. There is no font switch in the
line you used, so you are still in the normal latin modern font.
The second, and more important, reason why this does not work,
is because the ghostscript fonts have odd names for the dingbat
glyphs, and context has no way of knowing that they are actually
supposed to be in unicode encoding. So, you need a way to find
the glyph's name.
A (hopefully) working recipe follows.
First, run this file:
\usemodule[fnt-10]
\starttext
\ShowCompleteFont{name:dingbats}{10pt}{1}
\stoptext
that should give you five or six pages of output in columns:
<used encoding>, <actual glyph>, <glyph id>, <glyph name>, <aliases>
Look at the output, then use the <actual glyph> to find the <glyph
name> for ✪ (as I said, for me that is "a37"). Having found the name,
you can get the glyph with this bit of code:
\getnamedglyphdirect{name:dingbats}{a37} % for me
Best wishes,
Taco
___________________________________________________________________________________
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-22 16:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 14:00 Stefan Müller
2011-03-16 15:58 ` mathew
2011-03-17 9:05 ` Stefan Müller
2011-03-17 12:40 ` Ulrike Fischer
2011-03-17 13:41 ` Stefan Müller
2011-03-17 16:12 ` Otared Kavian
2011-03-17 16:53 ` Stefan Müller
2011-03-17 15:04 ` mathew
2011-03-17 16:53 ` Stefan Müller
2011-03-18 2:42 ` mathew
2011-03-18 3:27 ` Khaled Hosny
2011-03-18 10:04 ` Hans Hagen
2011-03-18 14:40 ` mathew
2011-03-18 14:51 ` Hans Hagen
2011-03-18 16:01 ` mathew
2011-03-18 18:30 ` Hans Hagen
[not found] ` <AANLkTinWPdN-H6TPNato9PG7Fh0PzvfS0PkHXehzbt6J@mail.gmail.com>
2011-03-22 16:08 ` mathew
2011-03-22 16:55 ` Taco Hoekwater [this message]
2011-03-18 11:26 ` Stefan Müller
2011-03-18 11:39 ` Hans Hagen
2011-03-18 14:47 ` Stefan Müller
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=4D88D47B.7010702@elvenkind.com \
--to=taco@elvenkind.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).