From: Steffen Wolfrum <context@st.estfiles.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: subject kills bookmarks?
Date: Mon, 16 Aug 2010 22:23:59 +0200 [thread overview]
Message-ID: <740F71E2-7EA4-403D-A154-DBC990A27D2A@st.estfiles.de> (raw)
In-Reply-To: <4C697E33.1090602@wxs.nl>
Am 16.08.2010 um 20:06 schrieb Hans Hagen:
> On 15-8-2010 7:05, Steffen Wolfrum wrote:
>> Hi,
>>
>> Why does subject kill bookmarks when used as first entry?
>> See attached example.
>>
>> (I am not sure whether I misunderstood the structural logic that's used for bookmarks.)
>
> Well, they assume some structure indeed and start from a parent that has a higher order.
>
> Normally one will have more structure (introductions or whatever) and never start with a dangling subject.
>
> In a toc this goes unnoticed as there is no tree visualized there.
That touches an interesting question: "Who sets structure?"
Easily I can think you hundreds of books where the author set "Preface", "Forword", "List of Abbreviations" and "List of Content" in a subordinate style. When the main text starts, this style is the same that is used for the second (or third) sectioning level. The same shows up in TOC: if these entries are listed in TOC, they are visually structured (by indentation and font) explicitly as the second (sometimes third) sectioning level.
As far as I have understood Hans' answer, the logic for bookmarks (or structured, tagged PDF in general?) works differently: even though the "design" of these sections (ie. section *headings*!) by the author is intended to be subordinated, nevertheless these section should be structured in a parent/child way: the first section mentioned is meant to be the highest level:
Would this map and represent the structure that the author was thinking of?
(Thank God it is not me who invented the structure of books and thus has to bear the blame ... and thank goodness we have Hans who manages to transform even the weirdest inputs and specs!)
Steffen
___________________________________________________________________________________
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:[~2010-08-16 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-15 17:05 Steffen Wolfrum
2010-08-16 18:06 ` Hans Hagen
2010-08-16 20:23 ` Steffen Wolfrum [this message]
2010-08-16 21:15 ` Hans Hagen
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=740F71E2-7EA4-403D-A154-DBC990A27D2A@st.estfiles.de \
--to=context@st.estfiles.de \
--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).