ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Meer, Hans van der" <H.vanderMeer@uva.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: Re: MKIV caption separator, revisited
Date: Mon, 10 Oct 2016 10:29:49 +0000	[thread overview]
Message-ID: <EE85CA43-D9DD-47B7-884E-2FD51BBBF005@uva.nl> (raw)
In-Reply-To: <57FB5411.6070401@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1712 bytes --]

Thanks I did not know the correct designations for the various parts of the captionlabel: the prefixconnector and the numberstopper. It is clear now.
Hans van der Meer




On 10 Oct 2016, at 10:40, Wolfgang Schuster <schuster.wolfgang@gmail.com<mailto:schuster.wolfgang@gmail.com>> wrote:

Wolfgang Schuster<mailto:schuster.wolfgang@gmail.com>
10. Oktober 2016 um 10:39
prefixconnector is the separator between the section number (=prefix) and the float number (=figure number), the symbol at the end of the float number is called numberstopper. In your example you don’t have a section which can act as prefix number no did you change which prefixes should be shown (by default only chapters are used as prefix).

The suffix key you use (together with suffixconnector and suffixstopper) is used to show the number for subfigures, e.g. figure 3.a.
Here is a working example for the use of the prefixconnector key.

\starttext

\section{This is a section}

\setupcaptions[prefixsegments=section,prefixconnector=-]

\startplacefigure[title=\tex{setupcaptions[prefixconnector=-]}]
\externalfigure[dummy][width=.5\textwidth]
\stopplacefigure

\stoptext

Wolfgang
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl<mailto: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
___________________________________________________________________________________


[-- Attachment #1.2: Type: text/html, Size: 3791 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2016-10-10 10:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-22  0:57 Rik Kabel
2014-04-22  6:25 ` Wolfgang Schuster
2014-04-22 15:09   ` Rik Kabel
2016-10-09 12:36   ` Meer, Hans van der
2016-10-09 19:44     ` Wolfgang Schuster
2016-10-10  7:41       ` Meer, Hans van der
2016-10-10  8:39         ` Wolfgang Schuster
2016-10-10  8:40           ` Wolfgang Schuster
2016-10-10 10:29             ` Meer, Hans van der [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=EE85CA43-D9DD-47B7-884E-2FD51BBBF005@uva.nl \
    --to=h.vandermeer@uva.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).