ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Wolfgang Schuster" <schuster.wolfgang@googlemail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: how to reuse float numbers?
Date: Mon, 10 Sep 2007 07:43:18 +0200	[thread overview]
Message-ID: <115224fb0709092243o554bf402q14883600cfa1bca9@mail.gmail.com> (raw)
In-Reply-To: <5c5e660c0709070917we88591ch9335ff346e1b6acb@mail.gmail.com>

2007/9/7, William S. <loumzie@gmail.com>:
> On 9/7/07, William S. <loumzie@gmail.com> wrote:
> > The guidelines specify that captions for code which is longer than one page
> > or crosses page boundaries should be reprinted and the title changed to
> > (continued).
> >
> > example:
> >
> > Program Segment 1.1: Hello World
> >   #include <stdio.h>
> >   main() {
> >
> > ...on next page...
> >
> > Program Segment 1.1: (continued)
> >     printf("hello world!\n");
> >   }
> >
>
> Thanks to Wolfgang's help the splitting problem is solved. However,
> after the float is split, the captions get extra numbers (1.1.A,
> 1.1.B, etc).
>
> I tried to "solve" this by using \setupfloatsplitting[conversions=...]
> but even if I defined a conversion that prints nothing, the caption
> would look like "Program Segment 1.1." (the final separator is still
> printed).

Hi William,

use

\setupfloatsplitting[conversions=numbers]

and

\setupcaptions[way=bytext]

The 1.1 is the normal float numbering, the 1, b, ... are the numbers
of every part of the splitted float.

> I suppose a better way would be to override the command that makes the
> captions (\setupcaption[ProgramSegment][command=...]) so that it
> prints the real caption text in the first part, and "(continued)" in
> the next parts.
> However, I've searched the mailing list archive and I can't find an
> example on what to put inside the command.

This seems to be not supported but you can try to look into core-tsp.tex,
the module where float splitting is implemented.

> Can someone give me a clue as to what I should put inside the command
> or maybe someone will have a better idea (maybe using
> \setupfloatsplitting[inbetween=...])?
>
> I've attached a slightly modified version of Wolfgang's document (I
> added a conversion for the setupfloatsplitting).
>
> Thanks,
> William.

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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      reply	other threads:[~2007-09-10  5:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-07  7:15 William S.
2007-09-07 11:54 ` Wolfgang Schuster
2007-09-07 12:44   ` William S.
2007-09-07 13:29     ` Wolfgang Schuster
2007-09-07 14:15       ` William S.
2007-09-07 16:17 ` William S.
2007-09-10  5:43   ` Wolfgang Schuster [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=115224fb0709092243o554bf402q14883600cfa1bca9@mail.gmail.com \
    --to=schuster.wolfgang@googlemail.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).