ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: no line breaks between figures
Date: Tue, 21 Jul 2009 21:08:15 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LNX.2.00.0907212040510.22956@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <6faad9f00907211140j11ce2c4xa41d1b443abcf3c7@mail.gmail.com>

CCed to ConTeXt mailing list.

On Tue, 21 Jul 2009, Mojca Miklavec wrote to pgf.user list:

> Hello,
>
> I noticed that a large number of
>    \begin{tikzpicture} \draw (0,0) -- (5,1); \end{tikzpicture}
> breaks at line end while
>    \starttikzpicture \draw (0,0) -- (5,1); \stoptikzpicture
> just generates an infinitely long line.
>
> Is there any simple way to fix the behaviour in ConTeXt?

Don't know.

> I also don't like the behaviour in
>    \placefigure{title}{\starttikzpicture ... \stoptikzpicture}
> that has to be surrounded with
>    \hbox{\starttikzpicture ... \stoptikzpicture}
> else the figure gets placed at the beginning of line instead of being centered.

This is what is happening. The pgf code basically boils down to this.

\starttext
\newbox\pgfpic

\setbox\pgfpic\hbox to 10pt\bgroup abc \egroup

\placefigure
   {testing box placement}
   {\leavevmode\raise-2pt\box\pgfpic}

\stoptext

Now since \placefigure internally places its contents in a \vbox, this 
boils down to a differnce beween

\hbox to \textwidth {\hss \vbox{\hbox{abc}} \hss}

\hbox to \textwidth {\hss \vbox{\leavevmode\raise-2pt \hbox{abc}} \hss}

So, the solution is to either patch \placefigure so that

\def\setlocalfloatdimensions#1%
  {...
   \global\setbox\floatbox\hbox% was \vbox
  ....}

or redefine \pgfsys@typesetpicturebox to

\def\pgfsys@typesetpicturebox#1{%
   ....
   \hbox{\leavevmode\raise-\pgf@x\box#1}%\hbox added
}


The redefinition at ConTeXt will break some existing documents (i.e., the 
authors will have to manually add a \vbox where there was none earlier). 
The redefinition at tikz end will make all pgf code run slightly slower 
(an extra hbox for each typeset pgfpicture)

If neither of these is acceptable, then we can have a simple wrapper 
around \start-stop tikzpicture:

\def\startTIKZcode{\hbox\bgroup\starttikzpicture}
\def\stopTIKZcode {\stoptikzpicture\egroup}

which will only affect ConTeXt code.

Aditya
___________________________________________________________________________________
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-07-22  1:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6faad9f00907211140j11ce2c4xa41d1b443abcf3c7@mail.gmail.com>
2009-07-22  1:08 ` Aditya Mahajan [this message]
2009-07-22 11:16   ` Hans Hagen
2009-07-22 12:05   ` [NTG-context] " Mojca Miklavec
2009-07-22 17:46     ` Aditya Mahajan

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=alpine.LNX.2.00.0907212040510.22956@ybpnyubfg.ybpnyqbznva \
    --to=adityam@umich.edu \
    --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).