All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: wmpalmer@gmail.com, Jeff King <peff@peff.net>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: RFD: tables in documentation
Date: Sun, 02 May 2010 21:23:56 +0200	[thread overview]
Message-ID: <4BDDD14C.7040503@drmicha.warpmail.net> (raw)
In-Reply-To: <20100502175353.GA15521@progeny.tock>

Jonathan Nieder venit, vidit, dixit 02.05.2010 19:53:
> Hi Michael,
> 
> Michael J Gruber wrote:
>> Michael J Gruber venit, vidit, dixit 02.05.2010 17:08:
> 
>>> Further experimentation (editing the xml) indicates that with my
>>> toolchain, I can either shut off all borders (between cells as well as
>>> outer) or none.
> [...]
>> For completeness, it results in this:
>>
>>      I                H         M               Result
>>
>>  0   nothing          nothing   nothing         (does not happen)
>>
>>  1   nothing          nothing   exists          use M
>>
>>  2   nothing          exists    nothing         remove path from index
>>
>>  3   nothing          exists    exists, H ==M   use M if "initial
>>                                                 checkout", keep index
>>      exists, H != M             fail            otherwise
>>
>> [Same unealt rowspan issue, of course.]
> 
> For what it’s worth, except for the broken last row, I like this and
> find it readable.  It is too bad there is no way to make it more
> compact so more rows can fit on a screen or page.
> 
> The ideal, to delimit the header without appearing busy, would be to
> just have a thin horizontal rule separating the header from the
> remaining rows[1].  Vertical rules are almost never a good idea.
> Maybe frame="topbot",grid="none",options="header" would be a good
> approximation.

That looks nice in HTML (and produces the correct xml), but
unfortunately my docbook renders this as if I had frame="all",grid="all" :(

> 
> Jonathan
> 
> [1] Just my opinion.  I probably learned the aesthetic from Simon Fear.
> http://www.tex.ac.uk/cgi-bin/texfaq2html?label=destable

  reply	other threads:[~2010-05-02 19:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-01 18:37 RFD: tables in documentation Michael J Gruber
2010-05-02  5:06 ` Jeff King
2010-05-02 13:31   ` Michael J Gruber
2010-05-02 14:43     ` Will Palmer
2010-05-02 14:51       ` Will Palmer
2010-05-02 15:08         ` Michael J Gruber
2010-05-02 15:27           ` Michael J Gruber
2010-05-02 17:53             ` Jonathan Nieder
2010-05-02 19:23               ` Michael J Gruber [this message]
2010-05-25  9:46     ` Jeff King
2010-05-25 11:59       ` Michael J Gruber

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=4BDDD14C.7040503@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=peff@peff.net \
    --cc=wmpalmer@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.