From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Steffen Wolfrum <context@st.estfiles.de>
Subject: Re: subject kills bookmarks?
Date: Mon, 16 Aug 2010 23:15:18 +0200 [thread overview]
Message-ID: <4C69AA66.2090405@wxs.nl> (raw)
In-Reply-To: <740F71E2-7EA4-403D-A154-DBC990A27D2A@st.estfiles.de>
> 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?
In a typeset toc it's often quite clear as visual clues are used
(indentation, font, vertical spacing, either of not a pagenumber)
I have made some quite complex structured docs (tens of different heads
at the same level). This goes ok as long as one is in control, but in
automated flows with input that can have some components not being
present and then also typeset one can have interesting confusing
situations. In such cases fonts/spacing in a toc depend on an analysis
of the structure (runtime).
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
___________________________________________________________________________________
prev parent reply other threads:[~2010-08-16 21:15 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
2010-08-16 21:15 ` 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=4C69AA66.2090405@wxs.nl \
--to=pragma@wxs.nl \
--cc=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).