ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Adam Lindsay" <atl@comp.lancs.ac.uk>
Subject: Re: Sidebars and versals Oh my!
Date: Mon, 27 Dec 2004 11:33:57 +0000	[thread overview]
Message-ID: <20041227113358.13693@news.comp.lancs.ac.uk> (raw)
In-Reply-To: <41CF2028.6050100@wxs.nl>

h h extern said this at Sun, 26 Dec 2004 21:33:44 +0100:

>> Context already has mechanisms for flowing or wrapping text around a
>graphic. 
>> How well the wraparound feature works when more than one short
paragraph is 
>> involved I have not tested yet.  
>
>the mp based background mechanism can handle that: see plus-rul.tex
>
>(there is also another mechanism available which permits rather nasty
>variants 
>but i still had no time to document it, so it's currently a hidden feature)

plus-rul is interesting, but I'm 98% certain that when John talks about
sidebars, he means what you call intermezzos. My interpretation, using
the things I do know (or figured out this morning):

\setupfloat [intermezzo] 
   [leftmargindistance=-\outercombitotal,
    rightmargindistance=-\outercombitotal,
    default=outer]
\setupcaption[intermezzo][location=none]
\starttext
\showframe
\input ward
\placeintermezzo{}{\framedtext[width=7cm]{\tfx\input dawkins }}
\dorecurse{3}{\input knuth \par}
\stoptext

What I don't know, however, is: 1) how to force a width on flowed text
within a float without resorting to the internal \framedtext, or 2) how
to use this with \splitfloat, which is what I suspect people who think
about sidebars (intermezzo texts) are going to be worried about in a
batch-based system. 
-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Adam T. Lindsay, Computing Dept.     atl@comp.lancs.ac.uk
 Lancaster University, InfoLab21        +44(0)1524/510.514
 Lancaster, LA1 4WA, UK             Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2004-12-27 11:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-24 16:15 John Culleton
2004-12-26 20:33 ` h h extern
2004-12-27 11:33   ` Adam Lindsay [this message]
2004-12-27 15:10     ` John Culleton
2004-12-27 17:08       ` Adam Lindsay
2004-12-27 17:42     ` John Culleton
2004-12-27 19:15       ` if I only had a frame (was: Re: Sidebars and versals Oh my!) Adam Lindsay
2004-12-27 19:24         ` if I only had a frame Hans Hagen
2004-12-27 19:40           ` Adam Lindsay
2004-12-27 19:46             ` Hans Hagen
2004-12-27 19:25         ` Hans Hagen
2004-12-27 19:29       ` Sidebars and versals Oh my! Hans Hagen
2004-12-27 20:29         ` John Culleton
2004-12-27 20:56           ` Adam Lindsay
2004-12-27 21:19             ` Hans Hagen
2004-12-27 21:31               ` Adam Lindsay
2004-12-29 22:05   ` Tobias Hilbricht
2004-12-30  9:32     ` Hans Hagen
2005-01-03  9:22       ` Tobias Hilbricht
2005-01-03 10:06         ` Hans Hagen
2005-01-03 10:39           ` Tobias Hilbricht
2005-01-03 12:32             ` Hans Hagen
2005-01-03 13:54               ` Tobias Hilbricht

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=20041227113358.13693@news.comp.lancs.ac.uk \
    --to=atl@comp.lancs.ac.uk \
    --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).