From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Jakub Wilk <jwilk@jwilk.net>,
"G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] posix.py: ffix: Correctly format URIs
Date: Thu, 21 Jan 2021 20:54:49 +0100 [thread overview]
Message-ID: <bdbf6dee-e74f-e2e3-8c44-4ce63d396aa1@gmail.com> (raw)
In-Reply-To: <20210112205115.g3nuoodpn7xxpx5u@jwilk.net>
Hi Jakub and Branden,
On 1/12/21 9:51 PM, Jakub Wilk wrote:
>> On 1/10/21 7:50 AM, G. Branden Robinson wrote:
>>> They use left and right angle bracket special character escapes
>>> (Unicode U+2039 and U+203A)
>
> I think that's a bug in groff. It should use plain <> for URLs, at least
> for tty output devices.
>
> * Alejandro Colomar <alx.manpages@gmail.com>, 2021-01-10, 15:35:
>> I checked, and yes, it renders some character (the character depends
>> on the terminal: on tty I've seen a diamond, and on the xfce terminal
>> something similar (but slightly different) to a parenthesis).
>
> Your console font doesn't support U+2039/U+203A and uses diamond as a
> replacement character.
>
> I have this in /etc/groff/mdoc.local and /etc/groff/mdoc.local as a
> work-around:
>
> . if '\V[TERM]'linux' \
> . tr \[la]<
> . if '\V[TERM]'linux' \
> . tr \[ra]>
>
> (In the long run, I should probably fix the font instead.)
>
After seeing Branden's answer to Michael (Escaping hyphens),
I've seen groff_char(7), and I found that my tty correctly supports
U+2039 and U+203A. I clearly see the symbols I would expect: something
quite similar to plain <>, but a bit more obtuse.
In the XFCE terminal, I also see something quite expected: a slightly
smaller version of <>.
But both show me very different characters for .UR/.UE.
tty displays a diamond, and XFCE term displays (a weird version of)
round parentheses.
So... does it mean there's a bug in .UR/.UE?
Thanks,
Alex
next prev parent reply other threads:[~2021-01-21 19:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 19:58 [PATCH] posix.py: ffix: Correctly format URIs Alejandro Colomar
2021-01-09 21:07 ` Alejandro Colomar (man-pages)
2021-01-10 6:50 ` G. Branden Robinson
2021-01-10 14:35 ` Alejandro Colomar (man-pages)
2021-01-10 14:57 ` [PATCH v2] " Alejandro Colomar
2021-01-19 19:59 ` Ping: " Alejandro Colomar (man-pages)
2021-01-20 8:50 ` Michael Kerrisk (man-pages)
2021-01-20 8:55 ` Michael Kerrisk (man-pages)
2021-01-12 20:51 ` [PATCH] " Jakub Wilk
2021-01-14 7:11 ` G. Branden Robinson
2021-01-21 19:54 ` Alejandro Colomar (man-pages) [this message]
2021-01-21 20:14 ` Jakub Wilk
2021-01-21 20:19 ` Alejandro Colomar
2021-01-22 3:23 ` G. Branden Robinson
2021-01-22 9:35 ` Jakub Wilk
2021-01-22 10:07 ` G. Branden Robinson
2021-01-22 10:50 ` Alejandro Colomar (man-pages)
2021-01-22 14:51 ` G. Branden Robinson
2021-01-22 17:27 ` Alejandro Colomar (man-pages)
2021-01-09 22:09 ` Alejandro Colomar (man-pages)
2021-01-22 12:37 ` Ping: " Alejandro Colomar (man-pages)
2021-01-22 15:13 ` Michael Kerrisk (man-pages)
2021-01-22 18:19 ` Alejandro Colomar (man-pages)
2021-01-23 9:15 ` Michael Kerrisk (man-pages)
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=bdbf6dee-e74f-e2e3-8c44-4ce63d396aa1@gmail.com \
--to=alx.manpages@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=jwilk@jwilk.net \
--cc=linux-man@vger.kernel.org \
/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