From: Rik <rik@panix.com>
To: ntg-context@ntg.nl
Subject: Re: linebreaks and cell width in xtables
Date: Sun, 04 May 2014 18:19:05 -0400 [thread overview]
Message-ID: <5366BCD9.9070006@panix.com> (raw)
In-Reply-To: <536698F9.4010108@gmx.es>
[-- Attachment #1.1: Type: text/plain, Size: 2418 bytes --]
On 2014-05-04 15:46, Pablo Rodriguez wrote:
> On 05/04/2014 08:27 PM, Rik Kabel wrote:
>> Any of the following will work here. Which is or are idiomatic I will
>> leave for others to say.
>>
>> This cell has multiple lines.\\
>>
>> This cell has multiple lines.\par
>>
>> This cell has multiple lines.\blank[none]
> Many thanks for your reply, Rik.
>
> I’m afraid none of them works. Here is my sample:
>
> \starttext
> \startxtable[option=stretch]
> \startxrow
> \startxcell
> aaa\blank[none]aaa
> \stopxcell
> \startxcell
> \ConTeXt\ \contextversion
> \stopxcell
> \stopxrow
> \startxrow
> \startxcell
> This cell has multiple lines.
> Vertical spacing is wrong.
> \stopxcell
> \startxcell
> What am I missing?
> \stopxcell
> \stopxrow
> \stopxtable
> \stoptext
>
> I’m using latest beta (2014.04.28 23:24) and the issue happens when
> there is text before and after the break.
>
>
> Pablo
Pablo,
With your example, I get
which shows a problem in row 2. When I add \\ to the first line of text
in row 2 column 1, as shown here
\starttext
\startxtable[option=stretch]
\startxrow
\startxcell
aaa\blank[none]aaa
\stopxcell
\startxcell
\ConTeXt\ \contextversion
\stopxcell
\stopxrow
\startxrow
\startxcell
This cell has multiple lines.\\
Vertical spacing is wrong.
\stopxcell
\startxcell
What am I missing?
\stopxcell
\stopxrow
\stopxtable
\stoptext
I get
which perhaps has some faults in the vertical spacing, but is much
better than the original. The spacing can be improved by specifying
[align=lohi] for that cell.
I get the same result with the other two methods I suggested. Is there a
reason that you cannot use one of these methods in row 2 as you do in row 1?
Perhaps we would all benefit from an obeylines alignment option?
--
Rik Kabel
[-- Attachment #1.2.1: Type: text/html, Size: 3620 bytes --]
[-- Attachment #1.2.2: fdbgicad.png --]
[-- Type: image/png, Size: 7684 bytes --]
[-- Attachment #1.2.3: jajfgfjj.png --]
[-- Type: image/png, Size: 7832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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:[~2014-05-04 22:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 16:30 Pablo Rodriguez
2014-05-04 18:27 ` Rik Kabel
2014-05-04 19:46 ` Pablo Rodriguez
2014-05-04 22:19 ` Rik [this message]
2014-05-04 22:20 ` Rik Kabel
2014-05-05 14:48 ` Pablo Rodriguez
2014-05-05 18:45 ` Hans Hagen
2014-05-05 19:01 ` Pablo Rodriguez
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=5366BCD9.9070006@panix.com \
--to=rik@panix.com \
--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).