tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: "Anthony J. Bentley" <anthony@anjbe.name>
Cc: tech@mandoc.bsd.lv
Subject: Re: table borders don't span entire width
Date: Fri, 8 Feb 2019 23:02:21 +0100	[thread overview]
Message-ID: <20190208220221.GF20044@athene.usta.de> (raw)
In-Reply-To: <29630.1549662225@desktop.ajb.soy>

Hi Anthony,

Anthony J. Bentley wrote on Fri, Feb 08, 2019 at 02:43:45PM -0700:

> In response to a mailing list question

I marvel that you understood that question.
I looked at it and didn't understand a word...

> I tried out an example from The Awk Programming Language.
> The tbl(7) source it generates looks in part like this:
> 
> .TS
> center;
> n n n n.
> _	_	_	_
> 2173	77.1	13765	53.6
> =	=	=	=
> .TE
> 
> groff creates solid lines as in the book:
> 
>                    ---------------------------
>                    2173   77.1   13765   53.6
>                    ---------------------------
> 
> But mandoc breaks the lines between cells:
> 
>                           ----   ----   -----   ----
>                           2173   77.1   13765   53.6
>                           ====   ====   =====   ====

That looks like a bug.
Here is what the tbl(7) manual page says:

     If a data cell contains only the single character '_' or '=',
     a single or double horizontal line is drawn across the cell,
     joining its neighbours.  If a data cells contains only the two
     character sequence '\_' or '\=', a single or double horizontal
     line is drawn inside the cell, not joining its neighbours.

> Side note: while using = for the double line is an improvement over
> groff, in UTF-8 the double line is output with U+2501. Wouldn't U+2550
> be more appropriate? The typeset output displays a double line, not a
> heavy line.

I think i did that because the heavy lines looked better to me,
but it's not the first time someone asks, so maybe i should change it.
Adjusting borders_utf8[] in tbl_term.c is probably all that is needed.

Yours,
  Ingo
--
 To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv

  reply	other threads:[~2019-02-08 22:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-08 21:43 Anthony J. Bentley
2019-02-08 22:02 ` Ingo Schwarze [this message]
2019-02-08 22:39   ` Ingo Schwarze
2019-02-08 23:18     ` Anthony J. Bentley
2019-02-09 16:55       ` Ingo Schwarze
2019-02-09 21:06   ` 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=20190208220221.GF20044@athene.usta.de \
    --to=schwarze@usta.de \
    --cc=anthony@anjbe.name \
    --cc=tech@mandoc.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).