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@freedom.nl>
Subject: Re: node.setglue broken in LuaMetaTeX
Date: Mon, 7 Nov 2022 13:26:15 +0100	[thread overview]
Message-ID: <40f60abb-3d21-d56f-b912-31cb8d332f18@freedom.nl> (raw)
In-Reply-To: <77cd88b54c5385ccc3ace67cc565d5c6e1a62914.camel@telus.net>

On 11/7/2022 11:40 AM, Max Chernoff via ntg-context wrote:
> Hi Hans,
> 
> Using node.setglue in LuaMetaTeX sets all of the glue components to
> zero.
> 
> This example:
> 
>     \startluacode
>         local stretch_order = "stretch_order"
>         local shrink_order = "shrink_order"
>         if status.luatex_engine == "luametatex" then
>             stretch_order = "stretchorder"
>             shrink_order  ="shrinkorder"
>         end
>     
>         local glue = node.new "glue"
>         print(node.getglue(glue))
>         node.setglue(glue, 1, 2, 3, 4, 5)
>         print(node.getglue(glue))
>         glue.width = 1
>         glue.stretch = 2
>         glue.shrink = 3
>         glue[stretch_order] = 4
>         glue[shrink_order] = 5
>         print(node.getglue(glue))
>         node.setglue(glue, 1, 2, 3, 4, 5)
>         print(node.getglue(glue))
>     \stopluacode
> 
> produces this output in MkIV:
> 
>     0       0       0       0       0
>     1       2       3       4       5
>     1       2       3       4       5
>     1       2       3       4       5
>     
> but this output in MkXL:
> 
>     0       0       0       0       0
>     0       0       0       0       0
>     1       2       3       4       5
>     0       0       0       0       0
it is unrelated to luametatex in the sense that it doesn't have that 
setter, so we emulate it in node-cmp.lmt:

function node.setglue   (n,...) return setglue   (todirect(n),...) end

but even then you won't get the '5' as bad values are intercepted ... 
i'll also add some extra checks to those field setters

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-11-07 12:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 10:40 Max Chernoff via ntg-context
2022-11-07 12:26 ` 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=40f60abb-3d21-d56f-b912-31cb8d332f18@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).