ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: two issues with variable fonts
Date: Sun, 4 Dec 2022 11:53:36 +0100	[thread overview]
Message-ID: <6f245ce7-c492-e36a-3b46-8d308643bd5d@xs4all.nl> (raw)
In-Reply-To: <0a42f0f4-8d84-53cf-5388-56afdae75884@gmx.es>

On 12/3/2022 10:29 AM, Pablo Rodriguez via ntg-context wrote:
> On 12/3/22 01:01, Hans Hagen via ntg-context wrote:
>> On 12/2/2022 8:17 PM, Hans Hagen via ntg-context wrote:
>>
>>>> Also in the last instances (at least, pages 19 to 25), kerning or
>>>> interletter spacing clearly needs to be improved.
>>> no clue (ok, a little)
>> sort of fixed but no upload yet (probably next week)
> 
> Many thanks for all your fixes, Hans.
> 
> BTW, using https://github.com/googlefonts/amstelvar/tree/main/fonts with
> the following source:
> 
>    \usemodule[fonts-variable]
>    \starttext
>      \showfontvariations[font=file:Amstelvar-Roman.ttf]
>      \showfontvariations[font=file:Amstelvar-Italic.ttf]
>    \stoptext
> 
> Font is missing in instances from pages 4, 8-11 (regular font) and 21-23
> (italic font).
> 
> Glyphs seem wrong on pages 12-13 (regular font) and interletter spacing
> is clearly not right in the instance from pages 24-25.
> 
> I don’t know whether this has already been fixed with your improvements
> yesterday.
the fact that some were not processed relates to a 'fix' of a while back 
... also keep in mind that the variable font code was written long ago 
when there were only a handful of experimental (and often somewhat 
buggy) fonts around showing off the new tricks .. since then there has 
not been much interest in variables fonts from the perspective of tex

assuming that i can motivate myself (read: the fonts look nice) i can 
probably sort out all the side effects

i'll check if we can deal with tags instead of names as not all fonts 
have nice names for the axis defined (which might be why one ends up 
with all these predefined instances)

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 / 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-12-04 10:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 18:06 Pablo Rodriguez via ntg-context
2022-12-02 19:17 ` Hans Hagen via ntg-context
2022-12-03  0:01   ` Hans Hagen via ntg-context
2022-12-03  9:29     ` Pablo Rodriguez via ntg-context
2022-12-04 10:53       ` Hans Hagen via ntg-context [this message]
2022-12-04 17:17         ` Pablo Rodriguez via ntg-context
2022-12-04 21:16         ` Henning Hraban Ramm via ntg-context
2022-12-06 18:56           ` Pablo Rodriguez via ntg-context
2022-12-06 20:07             ` Henning Hraban Ramm via ntg-context
2022-12-09 16:44               ` Pablo Rodriguez via ntg-context
2022-12-06 17:47         ` Pablo Rodriguez via ntg-context

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=6f245ce7-c492-e36a-3b46-8d308643bd5d@xs4all.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@xs4all.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).