From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: "Li Yanrui (李延瑞) via ntg-context" <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: Bug in tabulate
Date: Tue, 21 Mar 2023 09:02:28 +0100 [thread overview]
Message-ID: <db3b928f-e7db-5abd-cea8-5c7b292553f5@freedom.nl> (raw)
In-Reply-To: <CAFLdaXpfqbDi6f=J+b2wtEUzqAuyhxzDOqA1aT6jgV6_-qVTpA@mail.gmail.com>
On 3/21/2023 7:20 AM, Li Yanrui (李延瑞) via ntg-context wrote:
> Hi,
>
> Please see the following example:
>
> \startTEXpage[offset=5mm]
> \starttabulate[|c|c|c|]
> \VL 1 \VL 2 \VL 3\VL\NR
> \stoptabulate
> \blank
> \starttabulate[|c|c|c|]
> \NC 1 \NC 2 \NC 3\NR
> \stoptabulate
> \stopTEXpage
>
> In its result, there is a rule in the left side of the second tabulate.
> The result is attached. My lmtx version is 2023.03.20 17:07.
in tabl-tbl.mkxl you can patch this
\def\tabl_tabulate_vrule_reset_step % undefined or relax
{\gletcsname\??tabulatevrule0\endcsname\undefined
\gletcsname\??tabulatevrule\the\fastloopindex\endcsname\undefined}
after that remake the format,
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
___________________________________________________________________________________
prev parent reply other threads:[~2023-03-21 8:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 6:20 Li Yanrui (李延瑞) via ntg-context
2023-03-21 8:02 ` 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=db3b928f-e7db-5abd-cea8-5c7b292553f5@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).