discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: anthony@anjbe.name, mario.blaettermann@gmail.com
Cc: discuss@mandoc.bsd.lv
Subject: Re: HTML output: section headers with diacritics not in table of contents
Date: Sun, 27 Mar 2022 13:44:54 +0200	[thread overview]
Message-ID: <YkBONjZTI8oQJrmK@asta-kit.de> (raw)
In-Reply-To: <YkBH5pLZ6PqJoLCb@asta-kit.de>

Duh, the classical gaffe yet again.

Ingo Schwarze wrote on Sun, Mar 27, 2022 at 01:17:58PM +0200:
> Anthony J. Bentley wrote on Sat, Mar 26, 2022 at 11:55:13AM -0600:
>> 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.

> OK, i see.  So i have added a TODO entry, see below.
> I'll not start working on it before the upcoming OpenBSD release,
> but after that would be a good time to see what can be done.


Log Message:
-----------
new TODO entry: handle Unicode letters in tags

Modified Files:
--------------
    mandoc:
        TODO

Revision Data
-------------
Index: TODO
===================================================================
RCS file: /home/cvs/mandoc/mandoc/TODO,v
retrieving revision 1.321
retrieving revision 1.322
diff -LTODO -LTODO -u -p -r1.321 -r1.322
--- TODO
+++ TODO
@@ -313,6 +313,11 @@ are mere guesses, and some may be wrong.
   weerd@ 28 Sep 2021 12:44:07 +0200
   loc **  exist *  algo *  size *  imp ***
 
+- handle Unicode letters in tags in both HTML and terminal output
+  thread "section headers with diacritics" starting with
+  Mario Blaettermann 24 Mar 2022 18:13:23 +0100
+  loc **  exist *  algo *  size *  imp **
+
 - -T man does not handle eqn(7) and tbl(7)
   Stephen Gregoratto 16 Feb 2020 01:28:07 +1100
   also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901636
--
 To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv


  reply	other threads:[~2022-03-27 11:45 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
2022-03-27 11:17         ` Ingo Schwarze
2022-03-27 11:44           ` Ingo Schwarze [this message]
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=YkBONjZTI8oQJrmK@asta-kit.de \
    --to=schwarze@usta.de \
    --cc=anthony@anjbe.name \
    --cc=discuss@mandoc.bsd.lv \
    --cc=mario.blaettermann@gmail.com \
    /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).