From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Problem with colored font
Date: Sat, 7 Aug 2021 15:14:33 +0200 [thread overview]
Message-ID: <de100f62-e93c-dbcb-850a-da43c962a08a@xs4all.nl> (raw)
In-Reply-To: <CAK9ODgSZsSQSvka0HP8kqGwO52hKD+3BX3_a1_rhTygVbuBaOQ@mail.gmail.com>
On 8/7/2021 1:09 PM, Marcus Vinicius Mesquita via ntg-context wrote:
> Dear list,
>
> I'm trying to use the BabelStone Flags font, with colored flags of many
> countries,available freely under the SIL Open Font License 1.1 at:
> https://babelstone.co.uk/Fonts/Download/BabelStoneFlagsDual.ttf
> <https://babelstone.co.uk/Fonts/Download/BabelStoneFlagsDual.ttf>
>
> In the MWE below, there is a spurious “at” in the first time that the
> definition of the symbol for the Brazilian flag is used, but no problem
> when the definition for the flag of Portugal is used or even when the
> symbol for the Brazilian flag is used a second time. How to correct this
> behavior?
>
> MWE:
>
> \definefontfeature[colored][colr=yes]
> \definefontsynonym[flags][file:BabelStoneFlagsDual.ttf*colored at 7pt]
> \definesymbol[BR][\getglyphdirect{flags}{\char"F0023}]
> \definesymbol[PT][\getglyphdirect{flags}{\char"F00A1}]
>
> \starttext
>
> Brasil \symbol[BR]
>
> Portugal \symbol[PT]
>
> Brasil \symbol[BR]
>
> \stoptext
the fontsize is automatic so the "at .." interferes
here is an alternative (call by name):
\definesymbol[BR][{\getnamedglyphdirect{flags}{br}}]
\definesymbol[PT][{\getnamedglyphdirect{flags}{pt}}]
now, because you want it smaller i'll add this
\definesymbol[BR][{\getnamedglyphdirectscaled{.7}{flags}{br}}]
\definesymbol[PT][{\getnamedglyphdirectscaled{.7}{flags}{pt}}]
in the next upload
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2021-08-07 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 11:09 Marcus Vinicius Mesquita via ntg-context
2021-08-07 13:14 ` Hans Hagen via ntg-context [this message]
2021-08-07 13:23 ` Marcus Vinicius Mesquita via ntg-context
2021-08-07 21:49 ` Marcus Vinicius Mesquita via ntg-context
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=de100f62-e93c-dbcb-850a-da43c962a08a@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.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).