From: Alejandro Colomar <alx.manpages@gmail.com>
To: Stefan Puiu <stefan.puiu@gmail.com>,
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, 29 Jan 2023 19:35:39 +0100 [thread overview]
Message-ID: <534b83d9-0936-4a45-7d1e-159bfb07f492@gmail.com> (raw)
In-Reply-To: <CACKs7VAbs=fuqfEYhXALq3_PfoVbvVYUCc_D-GK5ObZJUPNwSw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1151 bytes --]
Hi Stefan,
On 1/29/23 17:45, Stefan Puiu wrote:
> Hi Helge,
>
> On Sun, Jan 22, 2023 at 9:39 PM Helge Kreutzmann <debian@helgefjell.de> wrote:
>>
>> Without further ado, the following was found:
>>
>> Issue: „“ are not old-style, they are the current quotation marks required by German othography
>
> Those are also used in Romanian, and probably other languages as well.
>
>>
>> "Latin-1 covers many West European languages such as Albanian, Basque,"
>> "Danish, English, Faroese, Galician, Icelandic, Irish, Italian, Norwegian,"
>> "Portuguese, Spanish, and Swedish. The lack of the ligatures Dutch IJ/ij,"
>> "French œ, and old-style „German“ quotation marks was considered tolerable."
>
> A bit weird to include Albanian in West European languages, isn't it?
> Maybe the text could be reworked to:
>
> "many West European languages such as Basque, Danish, [... other
> languages ...] and also Albanian."
I'd rather remove the "West" adjective from Europe. It's simpler. Does it
sound reasonable to you?
Cheers,
Alex
>
> Regards,
> Stefan.
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-01-29 18:36 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 19:31 Issue in man page charsets.7 Helge Kreutzmann
2023-01-29 16:45 ` Stefan Puiu
2023-01-29 18:35 ` Alejandro Colomar [this message]
2023-01-29 19:20 ` Bernd Petrovitsch
2023-01-29 19:29 ` Alejandro Colomar
2023-01-31 10:56 ` Stefan Puiu
-- 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-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-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-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-03-11 17:13 Helge Kreutzmann
2023-03-11 23:27 ` Alejandro Colomar
2023-03-12 5:14 ` Helge Kreutzmann
2023-03-12 11:28 ` Alejandro Colomar
2023-01-22 19:31 Helge Kreutzmann
2023-02-05 14:28 ` Alejandro Colomar
2023-02-05 14:49 ` Helge Kreutzmann
2023-01-22 19:31 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=534b83d9-0936-4a45-7d1e-159bfb07f492@gmail.com \
--to=alx.manpages@gmail.com \
--cc=debian@helgefjell.de \
--cc=linux-man@vger.kernel.org \
--cc=mario.blaettermann@gmail.com \
--cc=stefan.puiu@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