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>, Pablo Rodriguez <oinos@gmx.es>
Subject: Re: tweaked font options in \definedfontfeature?
Date: Sat, 1 Jan 2022 19:18:52 +0100 [thread overview]
Message-ID: <86477fd8-dde2-9621-e35a-c3cc24838034@xs4all.nl> (raw)
In-Reply-To: <a10afdb4-cb7f-719f-ce81-2ff6488266fd@gmx.es>
On 1/1/2022 6:05 PM, Pablo Rodriguez via ntg-context wrote:
> I wonder whether it would be possible to add the options for tweaked
> fonts (or at least, xscale and yscale) to \definefontfeature.
>
> I think this might ease the use of scaled fonts (at least, in some
> documents).
these two are unrelated to font feature so that won't happen .. the
whole idea is to *not* scale the font and delay that
the three scales are realtime scales and absolute values
\starttext
{test {\glyphxscale\numexpr 2*\glyphxscale\relax} test}
\fontspecdef\MyFont \font xscale 500 yscale 2000 % currentfont
{\MyFont test}
\stoptext
when you enable compact fonts we you actually use these fontspecs (a
font spec is internally comparable to a so called glue spec which is why
it's called that way: internally stored in some wierd kind of node ..
maybe \fontscalespec is better so i might change it when i can't think
of anything to add to it -- i'm still considering adding some of the
other realtime glyph properties)
i suppose that at some point we can add a more high level command (or
integrate it better in style definitions which all depends on usage
patterns
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
___________________________________________________________________________________
prev parent reply other threads:[~2022-01-01 18:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-01 17:05 Pablo Rodriguez via ntg-context
2022-01-01 18:18 ` Hans Hagen via ntg-context [this message]
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=86477fd8-dde2-9621-e35a-c3cc24838034@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.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).