From: Alejandro Colomar <alx.manpages@gmail.com>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page charsets.7
Date: Sun, 12 Mar 2023 00:27:36 +0100 [thread overview]
Message-ID: <f4fd4e46-7129-0f0b-519b-54ae39e2aba8@gmail.com> (raw)
In-Reply-To: <20230311171358.GA5005@Debian-50-lenny-64-minimal>
[-- Attachment #1.1: Type: text/plain, Size: 765 bytes --]
Hi Helge,
On 3/11/23 18:13, Helge Kreutzmann wrote:
> Without further ado, the following was found:
>
> Issue: ISO → ISO/IEC
I've already seen several reports about ISO -> ISO/IEC in several pages
from several people. I'd like someone who knows about these standards
to take a look at all the man pages and suggest a global fix about this.
Thanks,
Alex
>
> "The ISO 2022 and 4873 standards describe a font-control model based on VT100 "
> "practice. This model is (partially) supported by the Linux kernel and by "
> "B<xterm>(1). Several ISO 2022-based character encodings have been defined, "
> "especially for Japanese."
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-03-11 23:27 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 17:13 Issue in man page charsets.7 Helge Kreutzmann
2023-03-11 23:27 ` Alejandro Colomar [this message]
2023-03-12 5:14 ` Helge Kreutzmann
2023-03-12 11:28 ` Alejandro Colomar
-- strict thread matches above, loose matches on Subject: below --
2024-11-17 10:46 Helge Kreutzmann
2024-11-17 14:47 ` Alejandro Colomar
2024-11-17 15:07 ` Helge Kreutzmann
2024-11-17 15:16 ` Alejandro Colomar
2023-11-01 14:02 Helge Kreutzmann
2023-11-01 14:02 Helge Kreutzmann
2023-11-01 14:02 Helge Kreutzmann
2023-11-01 14:02 Helge Kreutzmann
2023-11-01 14:02 Helge Kreutzmann
2023-11-11 19:38 ` Alejandro Colomar
2023-11-11 19:45 ` Helge Kreutzmann
2024-01-28 20:22 ` Alejandro Colomar
2024-01-28 20:32 ` Helge Kreutzmann
2023-03-11 17:14 Helge Kreutzmann
2023-03-11 17:14 Helge Kreutzmann
2023-03-11 17:13 Helge Kreutzmann
2023-03-11 17:13 Helge Kreutzmann
2023-03-11 17:13 Helge Kreutzmann
2023-03-11 23:26 ` Alejandro Colomar
2023-03-12 5:08 ` Helge Kreutzmann
2023-03-11 17:13 Helge Kreutzmann
2023-01-22 19:31 Helge Kreutzmann
2023-01-29 16:45 ` Stefan Puiu
2023-01-29 18:35 ` Alejandro Colomar
2023-01-29 19:20 ` Bernd Petrovitsch
2023-01-29 19:29 ` Alejandro Colomar
2023-01-31 10:56 ` Stefan Puiu
2023-01-22 19:31 Helge Kreutzmann
2023-01-22 19:31 Helge Kreutzmann
2023-02-05 14:28 ` Alejandro Colomar
2023-02-05 14:49 ` Helge Kreutzmann
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=f4fd4e46-7129-0f0b-519b-54ae39e2aba8@gmail.com \
--to=alx.manpages@gmail.com \
--cc=debian@helgefjell.de \
--cc=linux-man@vger.kernel.org \
--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