From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: weird issue with xtable
Date: Thu, 13 Aug 2020 15:33:11 +0200 [thread overview]
Message-ID: <b0147fb6-c2fa-f085-70d3-076b23862a8c@gmx.es> (raw)
In-Reply-To: <02982329-171A-4143-B8C8-46D9998E2F69@elvenkind.com>
On 8/13/20 2:33 PM, Taco Hoekwater wrote:
> [...]
> I forgot to answer this. Simple explanation:
>
> * 'restricted horizontal mode' is inside an \hbox{} or something similar like a header/footer,
> where line breaks are forbidden
> * ‘horizontal mode’ is inside a paragraph, where line breaks are possible
>
> But the ‘restricted’ part is not relevant to your problem, \prevdepth
> is forbidden in horizontal mode regardless of restrictions; it is
> only allowed in vertical mode.
Manny thanks for your explanation, Taco.
> Somehow your table ends up being typeset in a horizontal context,
> based on the error message (at least, if we assume that the error
> message was triggered by a table).
I think it is easy to trigger the error:
\setupxtable[split=yes]
\starttext
\ifvmode yes\else no\fi
\startxtable[align={middle,lohi},columndistance=0em]
\startxrow
\startxcell
\dontleavehmode
\externalfigure[cow.pdf]
[scale=500]
\stopxcell
\stopxrow
\stopxtable
\stoptext
> But why that is? I do not have any other good ideas. And
> unfortunately lots of different things in ConTeXt can trigger an
> implicit horizontal context.>
> For debugging, you could try adding this to the preamble (or grouped
> around each xtable, for slightly less damage to the vertical
> spacing):>
> \let\prevdepth\relax
> \newdimen\prevdepth
>
> that should at least remove the error report. The vertical spacing
> in the pdf output will be wrong (!!!), but perhaps the output can
> provide a clue about what triggered the problem.
No idea of what is going wrong here.
My setups are even simplistic:
\setupxtable
[frame=off,
option=stretch,
split=repeat,
header=repeat]
\setupxtable
[split-table]
[split=yes]
\startxmlsetups xml:table:split
\blank
\startembeddedxtable[split-table]
\xmlflush{#1}
\stopembeddedxtable
\blank
\stopxmlsetups
But it seems that this cannot be fixed without investing much time.
I’m afraid I don’t have this time now.
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2020-08-13 13:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 11:07 Pablo Rodriguez
2020-08-13 11:16 ` Taco Hoekwater
2020-08-13 12:15 ` Pablo Rodriguez
2020-08-13 12:33 ` Taco Hoekwater
2020-08-13 13:11 ` Wolfgang Schuster
2020-08-13 14:18 ` Pablo Rodriguez
2020-08-13 16:06 ` Wolfgang Schuster
2020-08-13 18:30 ` Pablo Rodriguez
2020-08-13 18:47 ` Wolfgang Schuster
2020-08-13 20:11 ` Wolfgang Schuster
2020-08-13 20:44 ` Pablo Rodriguez
2020-08-13 13:33 ` Pablo Rodriguez [this message]
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=b0147fb6-c2fa-f085-70d3-076b23862a8c@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).