ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \setupcaptions question
Date: Thu, 12 Feb 2015 22:18:51 +0100	[thread overview]
Message-ID: <2E250ECA-1D8C-4A21-AF01-A98009C5AECB@gmail.com> (raw)
In-Reply-To: <op.xtyds0dyp7eajd@marco.fz-rossendorf.de>

Hi Joerg,

I think you are right when refering to a figure, the number stopper should not appear in the text.
It seems to me that using something like

	\setupcaption[figure][stopper={.}]

used to work in mkii and mkiv, but while it works in mkii, I just tried it with mkiv and found that it does not work as expected anymore.
So it is a bug introduced recently.
Probably Hans should be informed about it.

Best regards: OK

> On 12 Feb 2015, at 17:37, j. van den hoff <veedeehjay@googlemail.com> wrote:
> 
> 
> I want to use `numberstopper' for figure caption customization like so:
> 
> \setupcaptions[numberstopper={:}]
> 
> this works fine for the caption itself (i.e. I get, e.g. "Figure 1:
> caption text") _but_
> references to the figure via a defined label such as [fig:example]
> in the body text do include the numberstopper, too, which is highly
> undesirable in my view, since, e.g.,
> 
> "... see Figure 1: for an example. ..."
> 
> should rather read
> 
> "... see Figure 1 for an example. ..."
> 
> i.e. the numberstopper should be omitted (at least optionally) when
> referencing.
> 
> question: how can this be achieved?
> 
> 
> thx/j
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

___________________________________________________________________________________
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:[~2015-02-12 21:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-12 16:37 j. van den hoff
2015-02-12 21:18 ` Otared Kavian [this message]
2015-02-12 21:41   ` j. van den hoff
2015-02-12 21:31 ` Wolfgang Schuster
2015-02-12 21:56   ` Otared Kavian
2015-02-12 22:14     ` j. van den hoff
2015-02-13  3:54       ` Wolfgang Schuster
2015-02-13  7:53         ` j. van den hoff
2015-03-10 12:06           ` Wolfgang Schuster
  -- strict thread matches above, loose matches on Subject: below --
2015-02-12 16:21 joerg van den hoff

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=2E250ECA-1D8C-4A21-AF01-A98009C5AECB@gmail.com \
    --to=otared@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).