From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: issue with xtable in latest beta
Date: Wed, 13 May 2015 19:00:25 +0200 [thread overview]
Message-ID: <55538329.5090507@gmx.es> (raw)
In-Reply-To: <9C5FA21D-F3D6-4062-B2F9-958979F47320@gmail.com>
On 05/13/2015 05:57 PM, Wolfgang Schuster wrote:
> [...]
> The missing indentation of the paragraph after the table is caused
> by the \noindentationcommand which is called when you set “split=no”
> for your xtables. In older versions ofthe code Hans used \noindent instead
> which didn’t lead to the indentation problem.
>
> \setvalue{\??xtableflushsplit\v!no}%
> {\noindentation % better than \noindent (no \dontleavehmode here) % else no leftskip etc
> %\ignorespaces
> \clf_x_table_flush
> method {\v!normal}%
> \relax
> \removeunwantedspaces}
Many thanks for your reply, Wolfgang.
The code above was introduced to solve an extra blank space reported by
me (http://www.ntg.nl/pipermail/ntg-context/2015/082111.html).
Removing also \noindentation seems to work here.
Wouldn’t it be possible to remove it? (I mean, split=yes lacks
\noidentation and it works fine with this.)
BTW, I discovered another issue with "split=yes". There is less blank
space after the table than when the table isn’t splitted.
\setupindenting[yes, always, big]
\starttext
This is the first pagraph.
\startxtable[option=stretch, split=yes, align=center]
\startxrow
\startxcell[width=.3\textwidth] a \stopxcell
\startxcell[width=.2\textwidth] b \stopxcell
\startxcell[width=.2\textwidth] c \stopxcell
\startxcell[width=.3\textwidth] d \stopxcell
\stopxrow
\stopxtable
This is the second paragraph.
\startxtable[option=stretch, align=center]
\startxrow
\startxcell[width=.2\textwidth] a \stopxcell
\startxcell b \stopxcell
\startxcell c \stopxcell
\startxcell[width=.2\textwidth] d \stopxcell
\stopxrow
\stopxtable
This is the third paragraph.
\stoptext
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2015-05-13 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 15:34 Pablo Rodriguez
2015-05-13 15:57 ` Wolfgang Schuster
2015-05-13 17:00 ` Pablo Rodriguez [this message]
2015-05-13 17:12 ` Hans Hagen
2015-05-13 17:36 ` Pablo Rodriguez
2015-05-13 18:02 ` 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=55538329.5090507@gmx.es \
--to=oinos@gmx.es \
--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).