From: Gerion Entrup <gerion.entrup@flump.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: Fwd: Re: x mark symbol and general symbol guide
Date: Tue, 09 Jan 2024 20:31:26 +0100 [thread overview]
Message-ID: <22175089.EfDdHjke4D@falbala> (raw)
In-Reply-To: <a969bb48-7e3b-f05c-2354-122376ac49b2@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2849 bytes --]
Am Dienstag, 9. Januar 2024, 18:31:10 CET schrieb Wolfgang Schuster:
> Gerion Entrup schrieb am 09.01.2024 um 16:21:
> > Hi,
> >
> > I have to come back to that topic, since it seems not to work.
> > The said source code produces just the text "times" and "check" for me
> > (see 1.pdf). I also tried:
> >
> > ```
> > \usesymbols[fontawesome]
> >
> > \starttext
> > \showsymbolset[fontawesome-solid]
> > \stoptext
> > ```
> > and get a list of symbols that do not belong to fontawesome (see 2.pdf).
> >
> > I also tried to find the symbol file directly in the context
> > distribution and found:
> > tex/texmf-context/tex/context/base/mkiv/symb-imp-fontawesome.mkiv
> >
> > However, most parts are commented out there, one of the few remaining
> > symbols is wheelchair. However, when using that, I just got the string
> > _378 (3.pdf). Source code:
> >
> > ```
> > \usesymbols[fontawesome]
> >
> > \startTEXpage[offset=1pt]
> > \symbol[fontawesome][wheelchair]
> > \stopTEXpage
> > ```
> >
> > Is there a problem with my installation?
> > Additional output:
> > ```
> > % mtxrun --script fonts --list --all --pattern='fontawesome'
> > identifier familyname fontname filename subfont instances
> >
> > fontawesome fontawesome fontawesome FontAwesome.otf
> > fontawesome6brands fontawesome6brands fontawesome6brandsregular /usr/share/fonts/fontawesome/Font Awesome 6 Brands-Regular-400.otf
> > fontawesome6brandsnormal fontawesome6brands fontawesome6brandsregular /usr/share/fonts/fontawesome/Font Awesome 6 Brands-Regular-400.otf
> > fontawesome6freenormal fontawesome6free fontawesome6freesolid /usr/share/fonts/fontawesome/Font Awesome 6 Free-Solid-900.otf
> > fontawesomenormal fontawesome fontawesome FontAwesome.otf
> > fontawesomeregular fontawesome fontawesome FontAwesome.otf
> > ```
>
> The symbols expect version 5 of fontawesome but you have version 6.
>
> I guess it's time to switch to the new version of the fonts which can be
> done by replacing 5 (file:fontawsome5...) with 6 (file:fontawsome6...)
> in the following lines in symb-imp-fontawesome.mkiv
>
> \definefontsynonym [FontAwesomeBrands]
> [file:fontawesome5brandsregular400.otf]
> \definefontsynonym [FontAwesomeRegular]
> [file:fontawesome5freeregular400.otf]
> \definefontsynonym [FontAwesomeSolid] [file:fontawesome5freesolid900.otf]
>
> Wolfgang
My system awesome font is version 6 but isn't the one bundled with
ConTeXt version 5 (FontAwesome.otf)? This one:
tex/texmf/fonts/data/fonticons/fontawesome/FontAwesome.otf: OpenType font data
I would assume that ConTeXt is using the bundled file by default.
Gerion
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
[-- Attachment #2: Type: text/plain, Size: 511 bytes --]
___________________________________________________________________________________
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-01-09 19:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 13:36 [NTG-context] " Gerion Entrup
2024-01-09 15:21 ` [NTG-context] " Gerion Entrup
2024-01-09 17:31 ` Wolfgang Schuster
2024-01-09 19:31 ` Gerion Entrup [this message]
2024-01-09 20:17 ` Hans Hagen
2024-01-11 14:56 ` Gerion Entrup
2024-01-18 12:25 ` Gerion Entrup
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=22175089.EfDdHjke4D@falbala \
--to=gerion.entrup@flump.de \
--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).