From: Rik Kabel via ntg-context <ntg-context@ntg.nl>
To: Hans Hagen <j.hagen@xs4all.nl>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Rik Kabel <ConTeXt@rik.users.panix.com>
Subject: Re: New error "page order problem in tree at page"
Date: Thu, 5 Aug 2021 23:26:06 -0400 [thread overview]
Message-ID: <3d90d67e-6baf-40de-bf75-6a0f296227fd@rik.users.panix.com> (raw)
In-Reply-To: <abef2c89-1a7c-1e65-8092-14d8f596044a@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2116 bytes --]
On 8/5/2021 18:04, Hans Hagen wrote:
> On 8/4/2021 9:26 PM, Rik Kabel via ntg-context wrote:
>> With today's LMTX release I see the warning:
>>
>> backend > tags > beware: page order problem in tree at
>> page 1
>>
>> This appears to be recently introduced to the code.
>>
>> Should it be a concern? If so, where should I look to remedy it?
>
> mwe ...
>
Here it is:
\setuptagging [state=start]
\starttext
The problem involves tagging.
\stoptext
This produces, in relevant part:
system >
system > ConTeXt ver: 2021.08.06 01:21 LMTX fmt:
2021.8.5 int: english/english
system >
system > 'cont-new.mkxl' loaded
open source > level 1, order 1, name
'C:/ConTeXt_LMTX/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > beware: some patches loaded from cont-new.mkiv
close source > level 1, order 1, name
'C:/ConTeXt_LMTX/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > files > jobname 'G:/order', input 'G:/order.tex',
result 'G:/order'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source > level 1, order 2, name
'G:/Projects/Quotations/ConTeXt version/development/order.tex'
fonts > preloading latin modern fonts (second stage)
fonts > 'fallback modern-designsize rm 12pt' is loaded
*backend > tags > beware: page order problem in tree at page 1*
backend > xmp > using file
'C:/ConTeXt_LMTX/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml'
pages > flushing realpage 1, userpage 1, subpage 1
close source > level 1, order 2, name 'G:/order.tex'
system > start used files
system > text: order
system > stop used files
system > start used files
--
Rik
[-- Attachment #1.2: Type: text/html, Size: 3255 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2021-08-06 3:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 19:26 Rik Kabel via ntg-context
2021-08-05 22:04 ` Hans Hagen via ntg-context
2021-08-06 3:26 ` Rik Kabel via ntg-context [this message]
2021-08-07 8:46 ` Hans Hagen 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=3d90d67e-6baf-40de-bf75-6a0f296227fd@rik.users.panix.com \
--to=ntg-context@ntg.nl \
--cc=ConTeXt@rik.users.panix.com \
--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).