ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Max Chernoff via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: \setextrafontkerns can cause an infinite loop
Date: Thu, 30 Jun 2022 20:33:53 +0200	[thread overview]
Message-ID: <9b7d0054-bdba-5d23-9b09-969c0e86470b@freedom.nl> (raw)
In-Reply-To: <718d6053-69ea-6514-9203-97127bc6480b@telus.net>

On 6/30/2022 11:16 AM, Max Chernoff via ntg-context wrote:
> Sometimes using \setextrafontkerns can cause an infinite loop.
> 
> Example 1:
> 
>      \setextrafontkerns[max]
> 
>      \starttext
>          l\it l
>      \stoptext
> 
> Example 2:
> 
>      \setupbodyfont[libertinus]
> 
>      \setextrafontkerns[max]
> 
>      \starttext
>          x\ss x
>      \stoptext
> 
> Both of these examples cause ConTeXt to get stuck until it runs out of
> memory. This happens in both MkIV and MkXL.
> 
> This patch seems to fix the issue (although it may break other things...):
> 
> --- texmf-context/tex/context/base/mkiv/typo-fkr.old    2022-06-30 
> 03:05:17.702804200 -0600
> +++ texmf-context/tex/context/base/mkiv/typo-fkr.lua    2022-06-30 
> 03:05:22.286858200 -0600
> @@ -57,6 +57,7 @@
>                           end
>                           if kern ~= 0 then
>                               head, current = 
> insertbefore(head,current,new_kern(kern))
> +                            current = getnext(current)
>                           end
>                           lastdata = data
>                       else
> @@ -69,6 +70,7 @@
>                       local kern = getkernpair(lastdata,lastchar,char)
>                       if kern ~= 0 then
>                           head, current = 
> insertbefore(head,current,new_kern(kern))
> +                        current = getnext(current)
>                       end
>                   end
>                   lastchar = char
just

                             head = 
insertbefore(head,current,new_kern(kern))

will do

-----------------------------------------------------------------
                                           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
___________________________________________________________________________________

      reply	other threads:[~2022-06-30 18:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30  9:16 Max Chernoff via ntg-context
2022-06-30 18:33 ` 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=9b7d0054-bdba-5d23-9b09-969c0e86470b@freedom.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@freedom.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).