From: Kristaps Dzonsons <kristaps@bsd.lv>
To: tech@mdocml.bsd.lv
Cc: Ingo Schwarze <schwarze@usta.de>, Yuri Pankov <yuri.pankov@gmail.com>
Subject: Re: tbl issues with 1.11.1
Date: Wed, 21 Sep 2011 00:33:20 +0200 [thread overview]
Message-ID: <4E7914B0.7010101@bsd.lv> (raw)
In-Reply-To: <20110920173247.GF13269@iris.usta.de>
On 20/09/2011 19:32, Ingo Schwarze wrote:
> Hi,
>
> Ingo Schwarze wrote on Sat, May 14, 2011 at 06:12:28AM +0200:
>
>> Getting this right in both cases - with and without vertical rulers -
>> requires rather large changes. The logic, as far as i understand it
>> so far, goes like this:
>>
>> - box produces "|"
>> - no spacing at this point
>> - first cell, width is max(lengths)
>> - one space
>> - vertical ruler, if none, another space
>> - another space, unless there was a double ruler (!!)
>> - second cell
>> - and so on.
>>
>> That is vastly different from what we have now, both regarding the
>> width calculations - which apparently must not include padding - and
>> regarding the output itself.
>>
>> The work-in-progress patch below comes closer. However, it still
>> has at least two deficiencies, so it is not ready for commit:
>> - There still is a bogus space after double rulers, see (!!).
>> - The handling of explicit spacing options got sweeped away
>> by the reorg i was forced to do. Probably, i need to put
>> it back in at the right places. It was in the calc routine
>> but probably belongs in the output routines themselves.
>
> I now have an updated diff that i consider ripe for commit,
> which is improved in four respects:
> - do not use spanned cells for width calculations
> - draw horizontal rulers of the right width
> - correctly draw horizontal frames
> - guard against integer underflow in tbl_literal
>
> As explicit spacing options seem to be used very rarely, if at all,
> i have left them out for now to not make the diff yet larger.
>
> OK?
> Ingo
Ingo,
This looks ok---the table output formatting has always been spotty.
Please check this in (I like the in-line documentation you have, but the
more the better, as this area's tricksy).
Thanks!
Kristaps
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2011-09-20 22:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110414014526.GB1280@darklight.org.ru>
[not found] ` <20110416213413.GI13629@iris.usta.de>
[not found] ` <20110426201050.GA5448@britannica.bec.de>
[not found] ` <20110512220226.GA23153@britannica.bec.de>
[not found] ` <4DCD9CA4.2060708@bsd.lv>
[not found] ` <20110514041228.GA30797@iris.usta.de>
2011-09-20 17:32 ` Ingo Schwarze
2011-09-20 22:33 ` Kristaps Dzonsons [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=4E7914B0.7010101@bsd.lv \
--to=kristaps@bsd.lv \
--cc=schwarze@usta.de \
--cc=tech@mdocml.bsd.lv \
--cc=yuri.pankov@gmail.com \
/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).