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 07:41:38 +0000 [thread overview]
Message-ID: <06EA008D-492D-46C9-88F7-12713CE4DBDA@uva.nl> (raw)
In-Reply-To: <57FA9E08.6020106@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1689 bytes --]
Here is the example. \setupcaptions has no effect, however \setupfloatcaption does (assuming of course I didn't make a silly mistake ;-). Thus it is no problem to get the effect desired, but possibly \setupcaptions should be deprecated, or perhaps reimplemented to calling \setupfloatcaption. I could have missed the change, but I guess a lot of other people might have missed it too. In that case we could spare them the trouble of finding out what happened.
Hans van der Meer
\starttext
\setupcaptions[prefixconnector=-]
\startplacefigure[title=\tex{setupcaptions[prefixconnector=-]}]
\externalfigure[test.jpg][scale=300]
\stopplacefigure
\setupfloatcaption[suffix=-]
\startplacefigure[title=\tex{setupfloatcaption[suffix=-]}]
\externalfigure[test.jpg][scale=300]
\stopplacefigure
\stoptext
On 09 Oct 2016, at 21:44, Wolfgang Schuster <schuster.wolfgang@gmail.com<mailto:schuster.wolfgang@gmail.com>> wrote:
Meer, Hans van der<mailto:H.vanderMeer@uva.nl>
9. Oktober 2016 um 14:36
Is this still valid? Using \setupcaptions[prefixconnector=-] doesn't seem to make a difference for \startplacefigure.
Do you have a example?
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: 4801 bytes --]
[-- Attachment #2: tester.pdf --]
[-- Type: application/pdf, Size: 31515 bytes --]
[-- Attachment #3: 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
___________________________________________________________________________________
next prev parent reply other threads:[~2016-10-10 7:41 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 [this message]
2016-10-10 8:39 ` Wolfgang Schuster
2016-10-10 8:40 ` Wolfgang Schuster
2016-10-10 10:29 ` Meer, Hans van der
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=06EA008D-492D-46C9-88F7-12713CE4DBDA@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).