From: Joerg Sonnenberger <joerg@britannica.bec.de>
To: tech@mdocml.bsd.lv
Subject: HTML output for tbl
Date: Wed, 12 Jan 2011 22:58:01 +0100 [thread overview]
Message-ID: <20110112215801.GA5059@britannica.bec.de> (raw)
Hi Kristaps et al,
looking at the output for queue(3), there is a rather obvious bug in the
width output. It repeats the width: xxx for every column, e.g. the third
column has three width in order. This magically works due to the
overwrite rules, but is far from pretty. I also wonder if we should use
min-width and screw IE 6. That and using a single table (not one per
row) would be enough to give queue(3) a properly formatted table without
having to go extra wide by switching spacing from ex to em.
Joerg
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next reply other threads:[~2011-01-12 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 21:58 Joerg Sonnenberger [this message]
2011-01-13 12:36 ` Kristaps Dzonsons
2011-01-13 12:53 ` Joerg Sonnenberger
2011-01-13 14:30 ` Kristaps Dzonsons
2011-01-13 14:51 ` Joerg Sonnenberger
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=20110112215801.GA5059@britannica.bec.de \
--to=joerg@britannica.bec.de \
--cc=tech@mdocml.bsd.lv \
/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).