> have you tried this with your 'real world' documents?
Peter,
Although adding the \blank didn't fix the table splitting on this contrived
document, it actually seems to fix the problem on the few "real world"
documents that have shown this behavior. Although some of the breaks are still
not
Hans Hagen schrieb:
> Santy, Michael wrote:
>>> have you tried this with your 'real world' documents?
>> Peter,
>>
>> Although adding the \blank didn't fix the table splitting on this contrived
>> document, it actually seems to fix the problem on the few "real world"
>> documents that have shown
Santy, Michael wrote:
>> have you tried this with your 'real world' documents?
>
> Peter,
>
> Although adding the \blank didn't fix the table splitting on this contrived
> document, it actually seems to fix the problem on the few "real world"
> documents that have shown this behavior. Although
Peter Rolf wrote:
> just some further tests. i was wrong, as there is no table breaking
> without the \placetable[split] option. seems my command reference is
> outdated :(
>
> if you don't use \placetable at all, things work again. so there must be
> some vspace mess with the splitting option
Santy, Michael schrieb:
>
> Peter,
>
> There definitely seems to be something wrong with the splitting
> behavior, but I'm able to illustrate the same problem regardless of
> whether its wrapped in a \placetable (see example below). From my
> experiments, wrapping a table in placetable didn't se
Peter,
There definitely seems to be something wrong with the splitting behavior, but
I'm able to illustrate the same problem regardless of whether its wrapped in a
\placetable (see example below). From my experiments, wrapping a table in
placetable didn't seem to fix the broken tables or brea
...just some further tests. i was wrong, as there is no table breaking
without the \placetable[split] option. seems my command reference is
outdated :(
if you don't use \placetable at all, things work again. so there must be
some vspace mess with the splitting option of placetable and the one of
T
Santy, Michael schrieb:
>
>> The same as in my first reply. Look at the first page with the text
>> only. There isn't a space behind the sentence(s) and TeX can't break the
>> paragraph (text expands it's lower border). This also breaks the
>> splitting of the table, as it is (partly) on the same
Hagen, Hans wrote:
> it's always a problem to determine what's left on a page
>
> \def\blah{The quick brown fox jumped over the lazy stupid dog.}
> \dorecurse{62}{\blah} \synchronizeoutput
>
> this will force the otr but is not always fails safe (i.e. vertical
> spacing may be messed)
>
> ...
> The same as in my first reply. Look at the first page with the text
> only. There isn't a space behind the sentence(s) and TeX can't break the
> paragraph (text expands it's lower border). This also breaks the
> splitting of the table, as it is (partly) on the same page.
Peter, all of the infor
Santy, Michael wrote:
> Thanks Peter for the pointer to the multipage table in the wiki. I don't
> know how I overlooked that example. However, I was still able to duplicate
> the problem with this sample table by including a page full of text before
> the table (see below).
>
> If the dore
Santy, Michael schrieb:
>
> Thanks Peter for the pointer to the multipage table in the wiki. I
> don't know how I overlooked that example. However, I was still able to
> duplicate the problem with this sample table by including a page full of
> text before the table (see below).
>
> If the dor
Thanks Peter for the pointer to the multipage table in the wiki. I don't know
how I overlooked that example. However, I was still able to duplicate the
problem with this sample table by including a page full of text before the
table (see below).
If the dorecurse is set to 62 or 63, the con
Santy, Michael schrieb:
>
> In our XML->ConTeXt->PDF workflow, we've encountered a few intermittent
> problems when using split natural tables. I'm not able to post the
> original documents in which the problems are manifesting, but below is a
> document that reproduces one of the problems. The
In our XML->ConTeXt->PDF workflow, we've encountered a few intermittent
problems when using split natural tables. I'm not able to post the original
documents in which the problems are manifesting, but below is a document that
reproduces one of the problems. The first page of the document is f
15 matches
Mail list logo
