From: наб <nabijaczleweli@nabijaczleweli.xyz>
To: discuss@mandoc.bsd.lv
Subject: No/broken handling of backspaces in the source?
Date: Sat, 17 Sep 2022 19:03:31 +0200 [thread overview]
Message-ID: <20220917170331.otv4msv3aebcyizy@tarta.nabijaczleweli.xyz> (raw)
[-- Attachment #1: Type: text/plain, Size: 713 bytes --]
Hi!
A common pattern in very old (especially pre-troff) manuals I read often
is "aecn^H^H^H^H____" used to underline aecn ‒ this is a trivial
consequence of being made for typewriters.
[In the following examples a diacriticised character is used to
represent that character but underlined.]
groff handles this correctly, i.e.
printf 'aecn\b\b\b\b____ ____\b\b\b\bAECN\n.br\na\b_\t_\bA'
is rendered by groff as
ąęćń ĄĘĆŃ
ą Ą
and by less as
ą___ ĄECN
.br
ą Ą
but by mandoc (1.14.5-1 and current CVS) as
aecn????____ ____????AECN
a?_ _?A
It's unclear to me if this is supposed to happen, but I didn't see it in
the TODO, so.
Best,
наб
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2022-09-17 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 17:03 наб [this message]
2022-09-23 1:39 ` Mingye Wang
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=20220917170331.otv4msv3aebcyizy@tarta.nabijaczleweli.xyz \
--to=nabijaczleweli@nabijaczleweli.xyz \
--cc=discuss@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).