From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: embolden font in LMTX
Date: Thu, 16 Jul 2020 10:36:56 +0200 [thread overview]
Message-ID: <c154a404-061d-068d-23f0-07b6c7ca3510@xs4all.nl> (raw)
In-Reply-To: <4a45650a-b1d5-b82e-737c-217473316300@gmx.es>
On 7/15/2020 5:03 PM, Pablo Rodriguez wrote:
> Dear list,
>
> I have the following sample:
>
> \definefontfamily
> [mainface]
> [rm]
> [TeX Gyre Pagella]
> [it={style:regular, features:{default, slanted}},
> bi={style:regular, features:{default, boldened, slanted}},
> bf={style:regular, features:{default, boldened}}]
>
> \setupbodyfont[mainface]
>
> \starttext
> \input{zapf}\\
> {\it \input{zapf}}\\
> {\bf \input{zapf}}\\
> {\bi \input{zapf}}\\
> \stoptext
>
> I’m afraid that LMTX (current latest 2020.07.13 23:53) cannot deal with
> the boldened feature. MkIV (from 2020.01.30 14:13) works just fine.
>
> Am I missing something or have I hit a bug?
I have a fix. This kind of trickery is complicated by the fact that mkiv
and lmtx follow a bit different route and that there is still mkiv code
around that does the lmtx backend stuff (mkiv also had a lua pdf backend
but it was dropped at some point because it made no sense to keep it).
Features like these effects often are the result of playing around (as i
always want something weirdly new to present at e.g. a BT or CTX meeting
or just because it rains outside and I have a stack of new cd's to
listen to). For sure they can be made better if there is demand.
The same is true for variables fonts, emoji etc ... all these were
supported as soon as the fonts showed up providing them, but it's hard
to predict if any of that is actually used or useful.
Anyway, you seem to use most trickery so ... fix in next upload (but I
really do need to strip away old code some day).
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:[~2020-07-16 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 15:03 Pablo Rodriguez
2020-07-16 8:36 ` Hans Hagen [this message]
2020-07-17 15:48 ` Pablo Rodriguez
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=c154a404-061d-068d-23f0-07b6c7ca3510@xs4all.nl \
--to=j.hagen@xs4all.nl \
--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).