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: Mon, 16 Jul 2018 18:36:56 +0200	[thread overview]
Message-ID: <20180716163656.ttlmwsdtjvcsyadc@pali> (raw)
In-Reply-To: <20180716152919.GB85992@athene.usta.de>

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

Hi! Thanks for quick reply.

On Monday 16 July 2018 17:29:19 Ingo Schwarze wrote:
> Hi Pali,
> 
> i'm rearranging your text while quoting because you address
> most of the issues twice.
> 
> 
> Pali Rohar wrote on Mon, Jul 16, 2018 at 01:03:35PM +0200:
> 
> > It seems that mandoc is not able to format tables in HTML output
> > correctly.  Output is rather ugly which makes it less readable.
> 
> You have designed a very complicated table for testing, exercising
> many advanced features of the tbl(7) language:

Complicated? This is just simplified version of real used table in man
page. E.g.: https://github.com/pali/udftools/blob/master/doc/mkudffs.8

> > Because now ASCII version is better then what produce HTML.
> 
> Absolutely.  ASCII output is always better than HTML.  We consider
> terminal output by far the most important output mode in OpenBSD.
> But lately, HTML has also be improved in many respects, and that
> work will continue.  The importance of HTML output is increasing.

I was told that mandoc has support for formatting manpages to HTML and
it is really good, therefore I tested it on some manpages (like above).
And I had to say that no. ASCII of mandoc is better. And when I compared
table ASCII table generated by mandoc and groff, groff output is better.

So based on your reply, all those reports are not supported by mandoc
yet and marked as TODO...

I hope that they will be resolved, specially now when e.g. Arch Linux
and Debian started to generate HTML versions of manpages by mandoc.
Because otherwise it would be better to stick with UTF-8 output from
groff and do some HTMLization of plain text output...

About borders in html tables, I think that all is possible to describe
via CSS properties like buttom-border, left-border, etc, ...

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

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

  reply	other threads:[~2018-07-16 16:37 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 [this message]
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
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=20180716163656.ttlmwsdtjvcsyadc@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).