From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Rik Kabel <context@rik.users.panix.com>
Subject: Re: Confusing level change message, why?
Date: Sun, 17 Jun 2018 16:25:17 +0200 [thread overview]
Message-ID: <346d3730-bcea-a4ce-27d3-2e333c63a894@xs4all.nl> (raw)
In-Reply-To: <c6678898-0747-404d-336b-d3221b1750e0@rik.users.panix.com>
On 6/17/2018 2:48 PM, Rik Kabel wrote:
> On 6/17/2018 04:35, Pablo Rodriguez wrote:
>> On 06/15/2018 11:03 PM, Rik Kabel wrote:
>>> The example below is taken from the wiki article "Titles
>>> <http://wiki.contextgarden.net/Titles>," with pdf bookmark apparatus
>>> prepended and a second chapter added to the bodymatter.
>>>
>>> In the log, this produces the lines:
>>>
>>> backend > bookmarks > confusing level change at level 3
>>> around '1 body'
>>> backend > bookmarks > confusing level change at level 3
>>> around 'A appendix'
>>> backend > bookmarks > confusing level change at level 3
>>> around 'back'
>>>
>>> That is, one message for each *matter change.
>>>
>>> What is the meaning of the message, and how can it be removed (short of
>>> disabling pdf bookmarks)?
>> Hi Rik,
>>
>> if you disable bookmarks (by commenting
>> "\setupinteraction[state=start]"), you won’t get the message.
>>
>> But I wonder what is the problem besides the log message. From your
>> sample, I get a PDF document with all the expected content.
>>
>> What I am missing from your explanation? Or why are these log messages
>> so relevant if you get the intended output?
>>
>> Pablo
>
> Indeed, Pablo, there is no visible defect in the document.
>
> I wonder if the message should cause concern because I do not know if
> there is some other issue that it reflects, perhaps something that is
> not visible in the viewed document, but that might impede PDF standards
> compliance.
>
> If there is no fault or typesetting problem indicated by the message, I
> wonder why it is reported.
>
> Again, if there is no problem, I can add it to my log filtering
> routines, but I want to see it if there is something I should do to
> eliminate it.
it's just part of the check .. if you use for instance \section{foo}
instead of \startsecction there is some guesswork
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 / 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
___________________________________________________________________________________
prev parent reply other threads:[~2018-06-17 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 21:03 Rik Kabel
2018-06-17 8:35 ` Pablo Rodriguez
2018-06-17 12:48 ` Rik Kabel
2018-06-17 14:25 ` Hans Hagen [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=346d3730-bcea-a4ce-27d3-2e333c63a894@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=context@rik.users.panix.com \
--cc=ntg-context@ntg.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).