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: Sat, 1 Dec 2018 20:35:04 +0100	[thread overview]
Message-ID: <20181201193504.xhz534ttymgpvcrd@pali> (raw)
In-Reply-To: <20181201172057.GD89021@athene.usta.de>

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

On Saturday 01 December 2018 18:20:57 Ingo Schwarze wrote:
> Hi Pali,
> 
> Pali Rohar wrote on Mon, Nov 26, 2018 at 11:05:16PM +0100:
> > On Monday 26 November 2018 23:01:33 Pali Rohar wrote:
> >> On Monday 26 November 2018 22:58:26 Pali Rohar wrote:
> 
> >>> I tested new cvs changes for following table:
> 
> >>> .TS
> >>> box;
> >>> c|c|c.
> >>> A	A1	A_
> >>> \^	A2	\^
> >>> _
> >>> B	B1	B_
> >>> _
> >>> C	C1	C_
> >>> \^	C2	\^
> >>> _
> >>> E	E1	E_
> >>> \^	E2	\^
> >>> \^	E3	\^
> >>> _
> >>> F	F1	F_
> >>> .TE
> 
> The table syntax looks sane to me.
> 
> >>> And in chromium browser 70 there is missing horizontal line between
> >>> A and B; and also between C and D. See attachment how it looks like.
> >>>
> >>> It is really suspicious that horizontal line is just between A2 and B1.
> >>> And not across whole line.
> 
> The rendering in the PNG file you attached seems broken in multiple
> respects:
> 
>  * The outer border of the table as a whole is rendered as "double",
>    even though the mandoc HTML output clearly says:
> 
>    <table class="tbl" style="border-style: solid;">
> 
>  * Same for the horizontal line between B and C:
> 
>    <tr style="border-bottom-style: solid;">
>      <td style="text-align: center; border-right-style: solid;">B</td>
> 
>  * Same for the horizontal line between A and B:
> 
>    <tr style="border-bottom-style: solid;">
>      <td style="text-align: center; border-right-style: solid;">A2</td>
>    </tr>
> 
> So whatever produced that PNG file seems quite broken.

That PNG file is "printscreen" of Chromium browser window. I just wanted
to show how output looks in Chromium.

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

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

  reply	other threads:[~2018-12-01 19:35 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 [this message]
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
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=20181201193504.xhz534ttymgpvcrd@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).