From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: setupheads separator and stopper
Date: Fri, 24 Apr 2015 14:25:28 +0200 [thread overview]
Message-ID: <B867F402-A2B2-44D2-9212-B57EF0C83BC6@gmail.com> (raw)
In-Reply-To: <freemail.20150424140742.61295.1@fmxmldata05.freemail.hu>
> Am 24.04.2015 um 14:07 schrieb Csikos Bela <bcsikos425@freemail.hu>:
>
> Wolfgang Schuster írta:
>
>>> 1. The "section" part of the words sectionstarter and sectionstopper above is just
>>> a general term for any heading type and does not correspond to the heading type.
>>> Is this correct? (That is, there are no chapterstarter=, subsectionstarter= etc. options).
>>
>> No, it’s part of the key name and you have to use „sectionstopper” also for \part, \chapter etc.
>
> I see.
>
>>> 2. The command you commented, \setupreferencestructureprefix, what does it supposed to do? It did not do anything for me, eg:
>>> \setupreferencestructureprefix[default][prefixstarter={\symbol[diamond]},prefixstopper={\symbol[none]}]
>>
>> It comes the starter and stopper from the reference number in the text, compare the result from
>> \in with and without the \setupreferencestructureprefix setting.
>
> I compared the output of \in with commented and non-commented
> \setupreferencestructureprefix line. It does not make any difference, the two
> outputs are the same.
Without the the \setupreferencestructureprefix line you get
Reference to chapter (1) and section (1.1).
and with the line
Reference to chapter 1 and section 1.1.
>> \setupheads is only a synonym for \setuphead.
>
> OK. I also tried to change the separator to dash but I couldn't.
> I tried with \setuphead[separator=-] and with \setuphead[sectionseparator=-]
> but they didn't work. How can I change that?
You have to create a list of the separators with \defineseparatorset which can
then be applied with the sectionseparatorset key.
\defineseparatorset[mysectionseparator][x,y,z][?]
\setuphead[sectionseparatorset=mysectionseparator]
\setuphead[part] [placehead=yes,page=no]
\setuphead[chapter][page=no]
\starttext
\part{Part}
\chapter{Chapter}
\section{Section}
\subsection{Subsection}
\subsubsection{Subsubsection}
\subsubsubsection{Subsubsubsection}
\stoptext
Wolfgang
___________________________________________________________________________________
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-04-24 12:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 14:34 Csikos Bela
2015-04-23 23:01 ` Wolfgang Schuster
2015-04-24 9:19 ` Csikos Bela
2015-04-24 9:46 ` Wolfgang Schuster
2015-04-24 12:07 ` Csikos Bela
2015-04-24 12:25 ` Wolfgang Schuster [this message]
2015-04-24 12:56 ` Csikos Bela
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=B867F402-A2B2-44D2-9212-B57EF0C83BC6@gmail.com \
--to=schuster.wolfgang@gmail.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).