Mime-Version: |
1.0 (Apple Message framework v482) |
Sender: |
|
Date: |
Mon, 17 Mar 2003 14:21:11 -0500 |
Reply-To: |
|
Subject: |
|
From: |
|
Content-Transfer-Encoding: |
7bit |
In-Reply-To: |
|
Organization: |
|
Content-Type: |
text/plain; charset=US-ASCII; format=flowed |
Parts/Attachments: |
|
|
Javier Bezos said:
> Then, let's imagine the following: a GUI (Perl/Tk, Python/Tkinter,
> Java/Swing... what you like) which will allow to draw the areas
> in the page and define their meanings -- page dependent and "flowing".
> Unfortunately, flow text areas must have the same width (well, if these
> areas contain only text one could devise a way to change the width
> by measuring the remaining space and then applying \parshape if
> necessary). While still limited (no text wrapping figures), it would
> make *a lot* easier to design more fancier layouts.
As an examplar of this, wasn't there a recent post of a technique to
use a drawing program (xfig?) to draw shapes which could then be
processed to create the tex code for a \parshape
Hmm, doing a Google(TM) search for this yields a reference for
`fig2sty' (said to be buggy)
but nothing else---could've sworn it was in relation to using TeX to
typeset a CD (the label itself, not a jewelcase insert or booklet),
but I'm not finding it....
and Peter Wilson said:
> I must admit that I never thought that there would be a requirement
> to relocate headers/footers on long/short page pairs.
I can't imagine there would be---I was thinking about
footnotes---obviously I'm not thinking clearly today.
Sorry.
Will go back to lurking and learning.
William
--
William Adams, publishing specialist
voice - 717-731-6707 | Fax - 717-731-6708
www.atlis.com
|
|
|