ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Steffen Wolfrum <context@st.estfiles.de>
Subject: Re: Feature request
Date: Tue, 26 Jul 2005 17:00:16 +0200	[thread overview]
Message-ID: <a06230921bf0bfce456f3@[84.245.182.202]> (raw)

Hans Hagen <pragma@wxs.nl> wrote:

>  Steffen Wolfrum wrote:
>
>  > Hi,
>  >
>  > it would be great if the \placefigure macro could be extended to
>  > combinations like
>  >
>  > \placefigure{top,left}
>  >
>  > or
>  >
>  > \placefigure{bottom,outer}
>  >
>  >
>  > The reason for this request is that we use ConTeXt a lot for
>  > typesetting books from "arts and humanities".
>  >
>  > There we often have to place a lot of (more then 100) figures at
>  > "fixed" positions like top-outer and bottom-inner, wrapped by text.
>  >
>  > I guess it's not a trivial feature to be implemented in TeX's
>  > paragraph processing, but I know it might be worth the effort:
>  > ConTeXt's way to deal with fonts and text is so superior that it
>  > should be also accessible for disciplines that besides text also rely
>  > on images - as the arts and humanities do.
>
>  btw, do you know this trick?
>
>  \starttext
>
>  \hangsidefloat[2]
>  \placefigure[left][]{}{} \dorecurse{10}{\input zapf \par}
>
>  \stoptext
>



yes I know. you once told me (as for the first time I asked for this 
feature two years ago...).

true, it's a nice trick. and I used it in smaller publications.
but it is not practicable with a lot of images (and this cases are 
the regular ones, unfortunately).

typesetting with a lot of images wrapped by text is still a quite 
problematic task in ConTeXt/TeX .

Steffen

(P.S. actually my motivation to move to ConTeXt years ago was the 
hope that this image handling might be possible there. well, it 
wasn't ... )

             reply	other threads:[~2005-07-26 15:00 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-26 15:00 Steffen Wolfrum [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-07-03  6:00 feature request Atsuhito Kohda
2019-07-03  6:35 ` Henri Menke
2019-07-03  6:42 ` Henri Menke
2019-07-04  5:18   ` Atsuhito Kohda
2019-07-04  5:48     ` Henri Menke
2019-07-05 23:31       ` Atsuhito Kohda
2019-07-04 15:16     ` Aditya Mahajan
2019-07-04 15:54       ` Alan Braslau
2019-07-05 23:44         ` Atsuhito Kohda
2019-07-05 23:35       ` Atsuhito Kohda
2011-11-11 15:34 Steffen Wolfrum
2011-11-11 15:53 ` Andreas Harder
2011-11-11 15:57   ` Wolfgang Schuster
2011-11-11 16:01 ` Wolfgang Schuster
2011-11-11 18:47 ` Idris Samawi Hamid ادريس  سماوي حامد
2011-11-13 10:55   ` Steffen Wolfrum
2011-11-13 21:33     ` Andreas Schneider
2011-11-14  7:57       ` Steffen Wolfrum
2011-11-14  8:07         ` Hans Hagen
2011-11-14  9:22           ` Steffen Wolfrum
2011-11-14 18:38             ` Idris Samawi Hamid ادريس  سماوي حامد
2011-11-15 22:03               ` Idris Samawi Hamid ادريس   سماوي حامد
2011-11-15 22:11                 ` Wolfgang Schuster
2011-11-15 22:28                 ` Aditya Mahajan
2011-11-15 22:47                   ` Idris Samawi Hamid ادريس   سماوي حامد
2011-11-14  8:47 ` Aditya Mahajan
2011-11-14 14:03   ` Hans Hagen
2011-11-15  3:35     ` Aditya Mahajan
2011-11-15  5:43       ` Aditya Mahajan
2011-11-15  8:56         ` Hans Hagen
2007-07-05 17:41 Feature request John R. Culleton
2007-07-05 21:37 ` Patrick Gundlach
2007-07-05 22:27   ` John R. Culleton
2007-07-06  8:09     ` Patrick Gundlach
2005-07-27  9:58 Steffen Wolfrum
2005-07-27 22:16 ` Hans Hagen
     [not found] <a06210200bf0958f2bc0f@87.193.3.198>
2005-07-26 16:20 ` Mojca Miklavec
2005-07-26 22:56   ` Hans Hagen
2005-07-27  5:15     ` luigi.scarso
2005-07-26 15:33 Steffen Wolfrum
2005-07-26 22:38 ` Hans Hagen
2005-07-26 13:32 Steffen Wolfrum
2005-07-26 14:21 ` Hans Hagen
2005-07-26 14:32 ` 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='a06230921bf0bfce456f3@[84.245.182.202]' \
    --to=context@st.estfiles.de \
    --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).