From: Corin Royal Drummond <corin@studiochango.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Opposite Blocks or Spread Based Layouts
Date: Mon, 16 Mar 2009 16:56:14 -0600 [thread overview]
Message-ID: <49BED90E.2070704@studiochango.com> (raw)
In-Reply-To: <0FF2D0C3-97B4-4F53-A15E-B91818801E2F@gmail.com>
Wolfgang Schuster wrote:
>
> Am 16.03.2009 um 14:17 schrieb Corin Royal Drummond:
>
>> Still wondering what's up with opposite blocks though, if any one
>> knows. \startopposite \setupoppositeplacing et al.
>
> I think the can be called broken and Hans hadn't needed them
> in the past so no one noticed it. In this case it shoudn't be
> a problem to replace the current definition with something
> working, tell use what do you need to do this.
>
> Wolfgang
Ah, I see. No one ever used it, so opposite float placements died a
lonely death from malnutrition. Seems like a lovely concept for laying
out photo books with text, but I can route around. Thanks for the heads
up, Wolfgang.
Corin
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2009-03-16 22:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 6:00 Corin Royal Drummond
2009-03-16 7:37 ` Wolfgang Schuster
2009-03-16 13:17 ` Corin Royal Drummond
2009-03-16 14:33 ` Wolfgang Schuster
2009-03-16 22:56 ` Corin Royal Drummond [this message]
2009-03-16 12:29 ` Corin Royal Drummond
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=49BED90E.2070704@studiochango.com \
--to=corin@studiochango.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).