From: Musa Furber via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Musa Furber <musafurber@gmail.com>
Subject: Re: Confusing interaction between \writetolist and bookmarks (bug?)
Date: Mon, 22 Nov 2021 02:44:24 -0800 [thread overview]
Message-ID: <CAEfWR-mSbh_1CcZEwEtRtgi9JDzhcfiWBOSfAFZHRTHS30DB7A@mail.gmail.com> (raw)
In-Reply-To: <9d246c8a-93d4-1577-06c4-bd2be1a68356@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1906 bytes --]
On 22 November 2021 at 18:28:44, Hans Hagen via ntg-context (
ntg-context@ntg.nl) wrote:
On 11/22/2021 10:49 AM, musa furber via ntg-context wrote:
> I am relatively new to ConTeXt and have encountered something that does
> not work as I expected it to based on various documentation and examples.
>
> My book design requires the front matter to contain an abridged table of
> contents just for chapters, and a detailed table of contents in the back
> matter.
>
> Everything worked fine -- including the PDF bookmarks and table of
> contents -- until I started using \writetolist to manually inject
> additional sections and subsections into their respective lists. The
> manually injected entries do show up (as I expected), but their
> corresponding PDF bookmarks get repeated (not what I expected).
you can probably best use
\startsection[title={...},list={...},bookmark={...}]
...
\stopsection
I do not think that is an option for me.
The book is bilingual, with Arabic and English. There are places where I
want the chapter, section, and subsection titles to be bilingual as well,
with English on the left and Arabic on the right. I accomplish this using
the following…
\defineparagraphs[BilingualTitle][n=3,before={\blank[2*line]},after=,]
\setupparagraphs[BilingualTitle][1][width=.4\textwidth]
\setupparagraphs[BilingualTitle][2][width=.12\textwidth]
\setupparagraphs[BilingualTitle][3][width=.4\textwidth]
\define[2]\BilingualChapter
{\expanded{\writetolist[chapter]{}{#1}}
\startBilingualTitle
\noindentation\setlatin{}\tfd\setupinterlinespace\feature[+][smallcaps]\word{#1}\feature[<]
\nextBilingualTitle
\hfill\nextBilingualTitle
\noindentation\setarabic{}\tfd\setupinterlinespace{#2}
\stopBilingualTitle
}
…with variants for section, subsection, and subsection.
Regards,
Musa
[-- Attachment #1.2: Type: text/html, Size: 3072 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-11-22 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 9:49 musa furber via ntg-context
2021-11-22 10:28 ` Hans Hagen via ntg-context
2021-11-22 10:44 ` Musa Furber via ntg-context [this message]
2021-11-22 23:42 ` musa furber 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=CAEfWR-mSbh_1CcZEwEtRtgi9JDzhcfiWBOSfAFZHRTHS30DB7A@mail.gmail.com \
--to=ntg-context@ntg.nl \
--cc=musafurber@gmail.com \
/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).