discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Ingo Schwarze <schwarze@usta.de>
Cc: discuss@mandoc.bsd.lv
Subject: Re: Broken tables in HTML output
Date: Tue, 4 Dec 2018 17:44:14 +0100	[thread overview]
Message-ID: <20181204164414.bm4rdirdfcz3aveg@pali> (raw)
In-Reply-To: <20181203223743.GE92067@athene.usta.de>

[-- Attachment #1: Type: text/plain, Size: 1538 bytes --]

On Monday 03 December 2018 23:37:43 Ingo Schwarze wrote:
> Hi Pali,
> 
> Pali Rohar wrote on Mon, Dec 03, 2018 at 11:20:45PM +0100:
> > On Monday 03 December 2018 23:14:54 Ingo Schwarze wrote:
> >> Pali Rohar wrote on Mon, Dec 03, 2018 at 11:01:42PM +0100:
> 
> >>> Seems that it is needed to put "border-bottom-style: solid"
> >>> for rowspanned td element.  At least this is working in chrome.
> 
> >> That would further degrade the quality of the HTML code written by
> >> mandoc.  As a rule, "style=" attributes should be avoided and CSS
> >> should instead by used.  Unfortunately, that's not possible here
> >> because the hard-coded presentational decisions like "draw a border
> >> right here" are already contained in the tbl(7) input, and there
> >> is no way to convert those purely presentational decisions of the
> >> author into semantic or structural markup that could be handled
> >> with CSS.
> >> 
> >> But at least the amount of "style=" attributes written should be
> >> minimized.  Only those "style=" attributes should be written that
> >> are required to correctly express the author's intent.
> 
> > This suggestion is to move border style definition from tr do td.
> 
> That would mean writing more "style=" attributes.
> If a row intersects N cells, N times more.
> That is not good.

You can avoid all style= attributes in tables, by declaring class=
attributes instead of them and then in CSS defines border styles for
defined classes.

-- 
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2018-12-04 16:44 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-16 11:03 Pali Rohár
2018-07-16 15:29 ` Ingo Schwarze
2018-07-16 16:36   ` Pali Rohár
2018-07-16 17:44     ` Ingo Schwarze
2018-11-24 23:15   ` Ingo Schwarze
2018-11-25 19:34   ` Ingo Schwarze
2018-11-25 21:25     ` Ingo Schwarze
2018-11-26  8:53       ` Pali Rohár
2018-11-26 21:27   ` Ingo Schwarze
2018-11-26 21:58     ` Pali Rohár
2018-11-26 22:01       ` Pali Rohár
2018-11-26 22:05         ` Pali Rohár
2018-12-01 17:20           ` Ingo Schwarze
2018-12-01 19:35             ` Pali Rohár
2018-12-03 20:46             ` Pali Rohár
2018-12-04  5:33               ` Ingo Schwarze
2018-12-03 22:01             ` Pali Rohár
2018-12-03 22:14               ` Ingo Schwarze
2018-12-03 22:20                 ` Pali Rohár
2018-12-03 22:37                   ` Ingo Schwarze
2018-12-04 16:44                     ` Pali Rohár [this message]
2018-12-04 18:04                       ` Ingo Schwarze
2019-01-21  9:39                         ` Pali Rohár
2019-01-21 13:16                           ` Ingo Schwarze
2018-11-29  2:15     ` Ingo Schwarze

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=20181204164414.bm4rdirdfcz3aveg@pali \
    --to=pali.rohar@gmail.com \
    --cc=discuss@mandoc.bsd.lv \
    --cc=schwarze@usta.de \
    /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).