From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: ConTeXt users <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: issue with variable font
Date: Sun, 23 Oct 2022 15:14:41 +0200 [thread overview]
Message-ID: <86271302-491c-2aba-27f9-154dbabc9430@gmx.es> (raw)
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
Dear list,
I have the following sample (using current latest from 22022.10.22 11:23):
\definefontfeature
[book]
[axis={weight=700}]
\definefontfamily[mainface][rm]
[Commissioner][features={default, book}]
\setupbodyfont[mainface, 25pt]
\starttext
\startTEXpage[offset=1ex, align=center]
EFT ΕΘΞ
\blank[quarterline]
\dontleavehmode
\externalfigure[commissioner][width=.25\textwidth]
\stopTEXpage
\stoptext
The external figure is the output from Inkscape 1.1.2. I attach the
generated PDF document from the source above.
The variable font from Commissioner can be downloaded from
https://github.com/kosbarts/Commissioner/releases/download/1.000/Commissioner_1.000.zip.
ConTeXt seems to misread the font strokes (paths [or whatever the right
name might be]), since Inkscape has no problems with it.
Could anyone be so kind to confirm the issue?
Many thanks for your help,
Pablo
[-- Attachment #2: a.pdf --]
[-- Type: application/pdf, Size: 8061 bytes --]
[-- Attachment #3: Type: text/plain, Size: 496 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
reply other threads:[~2022-10-23 13:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=86271302-491c-2aba-27f9-154dbabc9430@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).