ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Piotr Kopszak <kopszak@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: The ultimate (?) float problem
Date: Tue, 12 May 2009 11:22:45 +0200	[thread overview]
Message-ID: <d56d340e0905120222s78a22fedo586434178f0d994f@mail.gmail.com> (raw)

Dear all,

I am close to give up, but maybe there is a solution... I have a book
to typeset literally peppered with hundreds of little drawings which
are supposed to appear irregularly surrounded by text flowing around
them on all sides.
--------------------------------
|xxxxxxxxxxxxxxxxxxxxxx |
|xxxxx-----xxxxxxxxxxxxxx|
|xxxxx|     |xxxxxx----xxxx |
|xxxxx|__|xxxxxx|     |xxxx|
|xxxxxxxxxxxxxx |__|xxxx|
|xxxxxxxxxxxxxxxxxxxxxx|
--------------------------------

I naively imagine that should not be that hard to implement ;) Since
we already have overlays it's no problem to place images in arbitrary
places. It only remains to drill white holes in the text to make room
for them.  What about such procedure:

1. While building the line TeX checks if there is any overlay ahead.
2 if so, it puts empty hbox of the overlay width when it reaches
necessary distance from the edge.
3. and does so for the number of lines which equal overlay height.

Of course that  leaves aside the problem of justification and without
justification such page would probably look very ugly (I dare not to
think if hz optimization, which I really got used to, would still
work).
Is there still hope I could stay with ConTeXt this time as well?

Many thanks for any ideas in advance

Piotr
--
http://okle.pl
___________________________________________________________________________________
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:[~2009-05-12  9:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12  9:22 Piotr Kopszak [this message]
2009-05-12 10:02 ` Hans Hagen
2009-05-12 10:16   ` Piotr Kopszak
2009-05-12 10:44     ` Hans Hagen
2009-05-12 10:28 ` luigi scarso
2009-05-12 11:28   ` Piotr Kopszak
2009-05-12 11:46     ` luigi scarso
2009-05-12 13:03       ` Piotr Kopszak
2009-05-12 13:11         ` luigi scarso
2009-05-12 13:18           ` Piotr Kopszak
2009-05-12 13:32             ` Wolfgang Schuster
2009-05-12 13:45               ` Piotr Kopszak
2009-05-12 14:16               ` luigi scarso
2009-05-14  9:17                 ` Piotr Kopszak
2009-05-12 13:29       ` ppchtex color Alan BRASLAU
2009-05-12 17:57         ` Hans Hagen
2009-05-12 18:07         ` Hans Hagen
2009-05-12 18:17         ` Hans Hagen
2009-05-12 20:45         ` Hans Hagen
2009-05-12 21:30         ` Alan BRASLAU
2009-05-12 21:53           ` Hans Hagen
2009-05-12 21:51         ` Alan BRASLAU
2009-05-13  8:33           ` Hans Hagen
2009-05-13  8:55             ` Alan BRASLAU
2009-05-13 11:25               ` Hans Hagen

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=d56d340e0905120222s78a22fedo586434178f0d994f@mail.gmail.com \
    --to=kopszak@gmail.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).