ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Willi Egger <w.egger@boede.nl>
To: thomas.floeren@boschung.com,
	mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \getscaledglyph
Date: Thu, 20 Jan 2011 16:37:11 +0100	[thread overview]
Message-ID: <63348924-2CD0-4AD4-977E-25CCF7A4212F@boede.nl> (raw)
In-Reply-To: <003101cbb876$df30a530$9d91ef90$@floeren@boschung.com>

Hi Thomas,

I had to do some work with regard to this issue recently.

What was mentioned on this list, is, that \fontchar is a command which will stay.

\setupbodyfont[Myfont,rm,12pt]
\definesymbol[Q.alt]  [\fontchar{Q.alt}]
\def\Qa{\symbol[Q.alt]}

The easiest way to get a stable environment is to use the char-names from the font. You can extract a table with all char-names with 

\usemodule[fnt-10]
\setupbodyfont[Myfont,rm,12pt]
\starttext
	\ShowCompleteFont{Myfont.otf}{10pt}{1} % fontname, size,columns
	% \ShowAllGlyphs   {Myfont}{48pt}{4} % fontname, size,columns  
\stoptext

Kind regards

Willi
On 20 Jan 2011, at 08:51, Thomas Floeren wrote:

> Hi,
> 
> I did a rather huge update step from my working context 2010.09.29 to the actual beta. I noted that \getscaledglyph doesn’t work anymore. 
> 
> I use it a lot for symbol insertions like this:
> 
> \definefontsynonym [ArialU] [name:ArialUnicodeMS]
> \definesymbol [Diameter] [\getscaledglyph{1.5}{ArialU}{\char"2300}]
> \def\Diam{\symbol[Diameter]}
> 
> \starttext
> hello \Diam\ goodbye
> \stoptext
> 
> 
> ( \getglyph seems to work as usual: \definesymbol [Diameter] [\tfb\getglyph{ArialU}{\char"2300}] )
> 
> Should I better change my definitions or is it just a bug?
> 
> 
> 
> Thank you
> & Greetings
> Thomas
> 
> 
> MTXrun | current version: 2011.01.18 19:34
> This is LuaTeX, Version beta-0.65.0-2010121316
> 
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

___________________________________________________________________________________
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:[~2011-01-20 15:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <003101cbb876$df30a530$9d91ef90$@floeren@boschung.com>
2011-01-20 15:37 ` Willi Egger [this message]
2011-01-20 22:25   ` \getscaledglyph Thomas Floeren
2011-01-21  8:50     ` \getscaledglyph Hans Hagen
2011-01-21 11:24       ` \getscaledglyph Thomas Floeren
2011-01-20  7:51 \getscaledglyph Thomas Floeren

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=63348924-2CD0-4AD4-977E-25CCF7A4212F@boede.nl \
    --to=w.egger@boede.nl \
    --cc=ntg-context@ntg.nl \
    --cc=thomas.floeren@boschung.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).