From: Cecil Westerhof <cldwesterhof@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Smileys
Date: Thu, 18 Aug 2011 10:53:00 +0200 [thread overview]
Message-ID: <CAG-LmmBobTfT+rDf+weZZ+g3hxT6Ebzve_6HfwMNJgfWs7YGqQ@mail.gmail.com> (raw)
In-Reply-To: <D25064D4-A5E8-48BA-A376-1D2FD1310C51@googlemail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1085 bytes --]
2011/8/18 Wolfgang Schuster <schuster.wolfgang@googlemail.com>
> It’s “wingdings” with a “g” in the name!
> \definefontsynonym[Wingdings][file:wingdings]
>
> \def\WingdingsSymbol{\getglyphdirect{Wingdings}}
>
> \definesymbol[smiley:1][\WingdingsSymbol{74}]
> \definesymbol[smiley:2][\WingdingsSymbol{75}]
> \definesymbol[smiley:3][\WingdingsSymbol{76}]
>
> \starttext
> \symbol[smiley:1] \symbol[smiley:2] \symbol[smiley:3]
> \stoptext
>
It is still the same. I know used context instead of my script. (Normally I
compile with a script, because I do not like all the output. When there is
an error I show the last part of the output.) I saw:
fonts > defining > font with asked name 'wingdings' is not
found using lookup 'file'
fonts > defining > unknown font wingdings, loading aborted
fonts > defining > unable to define wingdings as
\**currentsymbolfont**
So properly I need to install the font.
Would it not be better to have at least the option that not finding a font
is an error?
--
Cecil Westerhof
[-- Attachment #1.2: Type: text/html, Size: 1531 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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-08-18 8:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 19:46 Smileys Cecil Westerhof
2011-08-16 20:23 ` Smileys Henning Hraban Ramm
2011-08-16 20:55 ` Smileys Cecil Westerhof
2011-08-16 21:21 ` Smileys Wolfgang Schuster
2011-08-17 7:12 ` Smileys Patrick Gundlach
2011-08-17 7:49 ` Smileys Cecil Westerhof
2011-08-17 8:09 ` Smileys luigi scarso
2011-08-17 6:21 ` Smileys Henning Hraban Ramm
2011-08-17 11:14 ` Smileys Mojca Miklavec
2011-08-17 11:25 ` Smileys Wolfgang Schuster
2011-08-17 11:26 ` Smileys Cecil Westerhof
2011-08-17 12:27 ` Smileys Mojca Miklavec
2011-08-17 14:02 ` Smileys Jaroslav Hajtmar
2011-08-17 14:20 ` Smileys Cecil Westerhof
2011-08-17 21:57 ` Smileys Wolfgang Schuster
2011-08-18 7:40 ` Smileys Cecil Westerhof
2011-08-18 8:01 ` Smileys Wolfgang Schuster
2011-08-18 8:53 ` Cecil Westerhof [this message]
2011-08-18 20:19 ` Smileys Jaroslav Hajtmar
2011-08-18 20:53 ` Smileys Wolfgang Schuster
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=CAG-LmmBobTfT+rDf+weZZ+g3hxT6Ebzve_6HfwMNJgfWs7YGqQ@mail.gmail.com \
--to=cldwesterhof@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).