Re: Broken tables in HTML output

["Pali Rohár" <pali.rohar@gmail.com>]

On Tuesday 04 December 2018 19:04:57 Ingo Schwarze wrote:
> Hi Pali,
> 
> Pali Rohar wrote on Tue, Dec 04, 2018 at 05:44:14PM +0100:
> > On Monday 03 December 2018 23:37:43 Ingo Schwarze wrote:
> >> 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.
> 
> Sure, i could write
> 
>   <td class="border-left-double">
>   <td class="border-bottom">
>   <td class="border-bottom border-right">
> 
> and then in mandoc.css
> 
>   .border-left-double { border-left-style: "double"; }
>   .border-bottom { border-bottom-style: "solid"; }
>   .border-right { border-right-style: "solid"; }
> 
> But is that better than
> 
>   <td style="border-left-style: double;">
>   <td style="border-bottom-style: solid;">
>   <td style="border-bottom-style: solid; border-right-style: solid;">
> 
> and if it is better, why?
> 
> It is almost the same amount of attribute text, with only a minor
> difference in syntax, and it doesn't add any information about
> meaning or structure.  Also, there is no point for the user to
> modify ".border-left-double { }" in the stylesheet - what should
> it be mapped to as a personal style?  Mapping it to, say,
> 
>   .border-left-double { border-top-style: solid; }
> 
> just wouldn't make sense.  Classes only make sense to me if they
> tell something about meaning or structure.  If they are merely
> other names for physical style attributes, they seem pointless
> to me.  Or am i wrong - and if so, why?

I was thinking about it... I can say there are two arguments why to use
classes instead of inline style=.

1) Separate style logic (semantics) outside of html text (syntax).

2) Ability to correctly set style via custom css file. If somebody wants
   to use custom css file, then inlined style= attributes can cause
   problems.

With <td style="..."> you are saying use this specific style. But with
<td class="..."> you are saying that it belongs to specific class and
make abstraction how styles are used. For me it looks like a "proper"
way how to implement different things, by usage of layering abstraction.

> Yours,
>   Ingo

-- 
Pali Rohár
pali.rohar@gmail.com
--
 To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv