From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: Number in a circle
Date: Thu, 30 May 2024 17:26:58 +0200 [thread overview]
Message-ID: <187a4fb5-a85d-4218-80b9-9d1ddb127030@fiee.net> (raw)
In-Reply-To: <5c0af9f7290aa5879b50300c8d10eab9351c73e9.camel@thevertigo.com>
Am 28.05.24 um 23:49 schrieb Kip Warner:
> On Tue, 2024-05-28 at 08:17 +0200, Henning Hraban Ramm wrote:
>> Am 27.05.24 um 19:20 schrieb Kip Warner:
>> You could just define a fallback font, like:
>>
>> \definefontfallback[SymbolFB]
>> [file:symbola.otf]
>> [0x00300-0x003FF,0x02100-0x02800,0x1F000-0x20000] % look up the
>> right
>> Unicode ranges!
>> [check=no,force=no]
>>
>> \definetypeface [myfonts] [rm] [serif] [times] [default]
>> [fallbacks=SymbolFB]
>>
>> And then copy the character from a symbol table, no need for a macro.
>
> Hmm, that's a great idea. But I can't seem to get a minimal to work
> with https://context-on-web.eu:
>
> \definefontfallback[SymbolFB]
> [file:symbola.otf]
> [0x00300-0x003FF,0x02100-0x02800,0x1F000-0x20000] % look up the
> right
> Unicode ranges!
> [check=no,force=no]
>
> \definetypeface [myfonts] [rm] [serif] [times] [default]
> [fallbacks=SymbolFB]
>
> \starttext
> \utfchar{0x02460}
> \stoptext
>
> The above just prints the vanilla character '1'. That might be because
> the online editor doesn't have access to the font. So I tried compiling
> the above locally with the Symbola.otf file in the same directory and
> same problem.
>
My example wasn’t complete, and so is yours. You just define that
typeface but never use it.
Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2024-05-30 15:29 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 4:14 [NTG-context] " Kip Warner
2024-05-27 5:09 ` [NTG-context] " Ryszard Kubiak
2024-05-27 17:20 ` Kip Warner
2024-05-28 6:17 ` Henning Hraban Ramm
2024-05-28 21:49 ` Kip Warner
2024-05-30 15:26 ` Henning Hraban Ramm [this message]
2024-05-30 21:18 ` Kip Warner
2024-05-27 9:43 ` seyal zavira
2024-05-27 17:23 ` Kip Warner
2024-05-27 17:44 ` Wolfgang Schuster
2024-05-28 4:29 ` Kip Warner
2024-05-28 15:38 ` Wolfgang Schuster
2024-05-28 22:02 ` Kip Warner
2024-05-29 4:52 ` Kip Warner
2024-05-27 14:51 ` Wolfgang Schuster
2024-05-27 17:10 ` Kip Warner
2024-05-27 17:28 ` Wolfgang Schuster
2024-05-27 17:33 ` Kip Warner
2024-05-27 18:15 ` vm via ntg-context
2024-05-28 21:37 ` Kip Warner
2024-05-28 15:47 ` Pablo Rodriguez via ntg-context
2024-05-28 15:50 ` Pablo Rodriguez via ntg-context
2024-05-28 21:50 ` Kip Warner
2024-05-30 15:22 ` Henning Hraban Ramm
2024-05-30 16:18 ` Kip Warner
2024-05-30 16:26 ` Thomas A. Schmitz
2024-05-30 17:25 ` Kip Warner
2024-05-30 20:19 ` Henning Hraban Ramm
2024-05-30 22:20 ` Bruce Horrocks
2024-05-30 23:05 ` Kip Warner
2024-06-01 0:48 ` Bruce Horrocks
2024-06-04 17:19 ` Bruce Horrocks
2024-06-04 18:00 ` Kip Warner
2024-06-04 20:44 ` Bruce Horrocks
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=187a4fb5-a85d-4218-80b9-9d1ddb127030@fiee.net \
--to=texml@fiee.net \
--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).