From: "Anthony J. Bentley" <anthony@anjbe.name>
To: Ingo Schwarze <schwarze@usta.de>
Cc: tech@mandoc.bsd.lv
Subject: Re: table borders don't span entire width
Date: Fri, 08 Feb 2019 16:18:37 -0700 [thread overview]
Message-ID: <48691.1549667917@desktop.ajb.soy> (raw)
In-Reply-To: <20190208223911.GH20044@athene.usta.de>
Hi Ingo,
The missing characters ring a bell. I'm pretty sure I investigated this
before, came to the same conclusion (that needed box drawing characters
don't exist), and then must have forgotten all about it.
Ingo Schwarze writes:
> So in particular, the following are missing:
>
> * double right
> * double down
> * single left with double right
> * single left down with double right
> * single left with double right down
> * double left
> * double left with single right
> * double left with single right down
> * double left down with single right
>
> and so on...
>
> With heavy instead of double, such combinations exist.
That's a real shame. I looked in the Unicode standard but couldn't find
any rationale, only a comment that the box drawing section of Unicode
exists for compatibility with historic systems. I guess there wasn't
anything out there that used double boxes in this way.
https://www.unicode.org/versions/Unicode11.0.0/ch22.pdf
> So, should i leave this untouched, or am i missing something?
Leave it as is, I guess. But we should document this limitation in
tbl(7) since it's non-obvious and seems to have come up multiple times.
Or just draw twice as many lines, like groff attempts poorly with
doublebox...
--
Anthony J. Bentley
--
To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv
next prev parent reply other threads:[~2019-02-08 23:18 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
2019-02-08 22:39 ` Ingo Schwarze
2019-02-08 23:18 ` Anthony J. Bentley [this message]
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=48691.1549667917@desktop.ajb.soy \
--to=anthony@anjbe.name \
--cc=schwarze@usta.de \
--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).