From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: issues with bookmarks
Date: Mon, 27 Jul 2015 19:34:42 +0200 [thread overview]
Message-ID: <55B66BB2.6010204@wxs.nl> (raw)
In-Reply-To: <55B63C7C.8000304@gmx.es>
On 7/27/2015 4:13 PM, Pablo Rodriguez wrote:
> On 07/27/2015 02:47 PM, Hans Hagen wrote:
>> On 7/26/2015 8:01 PM, Pablo Rodriguez wrote:
>>> Hans,
>>>
>>> sorry for the long message, but I’m afraid that bookmarks have some issues.
>>>
>>> 1. When specifying sectionblocks, bookmarks for parts don’t contain
>>> chapters as child elements:
>>>
>>> \setupinteraction[state=start]
>>> \placebookmarks[part, chapter][part, chapter]
>>> \setuphead[part][placehead=yes]
>>> \starttext
>>> \startfrontmatter
>>> \chapter{Foreword}
>>> \chapter{Introduction}
>>> \stopfrontmatter
>>> \startbodymatter
>>> \part{First Part}
>>> \chapter{First Chapter}
>>> \chapter{Second Chapter}
>>> \part{Second Part}
>>> \chapter{Third Chapter}
>>> \chapter{Fourth Chapter}
>>> \stopbodymatter
>>> \stoptext
>>
>> In SumatraPDF (which i use mostly) and Acrobat I see
>>
>> Foreword
>> Introduction
>> 1 First Part
>> 1.1 First Chapter
>> 1.2 Second Chapter
>> 2 Second Part
>> 2.1 Third Chapter
>> 2.2 Fourth Chapter
>>
>> I remember a thread about bugged viewers so maybe your viewer is not ok.
>
> Hans,
>
> evince shows the same output. But the bookmarks are wrong in all viewers.
>
> I’m afraid that issue 1 shows uncontained bookmarks. The first and
> second code samples from #1 are wrong and the third code sample from #1
> is right.
>
> Issue 2 misplaced bookmarks and issue 3 shows wrong indented bookmarks.
>
> Sorry but I’m afraid that the issues may be bugs.
Hm, the bookmarks themselves are okay but you mean the collapsing of
them. That is a side effect of lack of parts in the preceding block. I
have a fix for that but of course I don't know it there are other side
effects. There is only so much one can do with such structures.
The other issue, the copyright one, is a result of putting something
outside the blocks and as we default to frontpart you effectively end up
with a mixed block structure in the lists
bodypart .. frontpart .. bodypart
\starttext
\setsectionblock[frontpart]
\hiddentitle{[Copyright1]}
fixes this. Anyway, I tried to make that kind of automatic now but it's
a real ugly hack (one of these things a reader of the code will wonder
about why it's there and also one of things i will forget about after a
while).
I'll make a beta later. Not much testing at my end.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2015-07-27 17:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-26 18:01 Pablo Rodriguez
2015-07-26 21:58 ` Alan BRASLAU
2015-07-27 12:39 ` Hans Hagen
2015-07-27 12:47 ` Hans Hagen
2015-07-27 14:13 ` Pablo Rodriguez
2015-07-27 17:34 ` Hans Hagen [this message]
2015-07-27 18:21 ` Pablo Rodriguez
2015-07-27 13:26 ` juh
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=55B66BB2.6010204@wxs.nl \
--to=pragma@wxs.nl \
--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).