From: "Anthony J. Bentley" <anthony@anjbe.name>
To: Ingo Schwarze <schwarze@usta.de>
Cc: discuss@mandoc.bsd.lv
Subject: Re: HTML output: section headers with diacritics not in table of contents
Date: Sat, 26 Mar 2022 11:55:13 -0600 [thread overview]
Message-ID: <50325-1648317313.709340@li8c.ggMJ.xEbA> (raw)
In-Reply-To: <Yj7r+NR9idXjijR7@asta-kit.de>
Hi Ingo,
Ingo Schwarze writes:
> All the same, before starting work on an implementation, i would
> also appreciate your opinion, Anthony (and possibly of similarly
> prolific users and maintainers in other operating systems) whether
> such functionality seems desirable to you, because i feel like
> sitting on the fence myself.
As a user, I was mildly surprised to learn Mandoc limits URL fragments
to ASCII; I would expect it to create UTF-8 fragments seamlessly.
So consider me in favor of such a change.
In fact, if it’s workable, I would also like to be able to use UTF-8
tags in less(1) as well.
--
Anthony J. Bentley
--
To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
next prev parent reply other threads:[~2022-03-26 17:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 17:13 Mario Blättermann
2022-03-24 17:33 ` Michael Stapelberg
2022-03-24 18:00 ` Mario Blättermann
2022-03-25 12:27 ` Ingo Schwarze
2022-03-25 16:07 ` Mario Blättermann
2022-03-25 20:58 ` Jan Stary
2022-03-26 12:34 ` Ingo Schwarze
2022-03-26 13:35 ` Mario Blättermann
2022-03-25 16:21 ` Anthony J. Bentley
2022-03-25 21:15 ` Jan Stary
2022-03-26 10:33 ` Ingo Schwarze
2022-03-26 17:55 ` Anthony J. Bentley [this message]
2022-03-27 11:17 ` Ingo Schwarze
2022-03-27 11:44 ` Ingo Schwarze
2022-03-25 16:57 ` Mario Blättermann
2022-03-25 20:36 ` Jan Stary
2022-03-25 20:59 ` Mario Blättermann
2022-03-25 21:20 ` Jan Stary
2022-03-26 9:25 ` 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=50325-1648317313.709340@li8c.ggMJ.xEbA \
--to=anthony@anjbe.name \
--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).