From: Mauro Carvalho Chehab <mchehab+huawei@kernel•org>
To: David Woodhouse <dwmw2@infradead•org>
Cc: Linux Doc Mailing List <linux-doc@vger•kernel.org>,
linux-kernel@vger•kernel.org, Jonathan Corbet <corbet@lwn•net>,
alsa-devel@alsa-project•org, coresight@lists•linaro.org,
dri-devel@lists•freedesktop.org, intel-gfx@lists•freedesktop.org,
intel-wired-lan@lists•osuosl.org, keyrings@vger•kernel.org,
kvm@vger•kernel.org, linux-acpi@vger•kernel.org,
linux-arm-kernel@lists•infradead.org, linux-edac@vger•kernel.org,
linux-ext4@vger•kernel.org,
linux-f2fs-devel@lists•sourceforge.net,
linux-fpga@vger•kernel.org, linux-hwmon@vger•kernel.org,
linux-iio@vger•kernel.org, linux-input@vger•kernel.org,
linux-integrity@vger•kernel.org, linux-media@vger•kernel.org,
linux-pci@vger•kernel.org, linux-pm@vger•kernel.org,
linux-rdma@vger•kernel.org, linux-riscv@lists•infradead.org,
linux-sgx@vger•kernel.org, linux-usb@vger•kernel.org,
mjpeg-users@lists•sourceforge.net, netdev@vger•kernel.org,
rcu@vger•kernel.org, x86@kernel•org
Subject: Re: [PATCH 00/53] Get rid of UTF-8 chars that can be mapped as ASCII
Date: Tue, 11 May 2021 11:25:08 +0200 [thread overview]
Message-ID: <20210511112508.4547bca8@coco.lan> (raw)
In-Reply-To: <de6d1fa5b7934f4afd61370d9c58502bef588466.camel@infradead.org>
Em Mon, 10 May 2021 14:49:44 +0100
David Woodhouse <dwmw2@infradead•org> escreveu:
> On Mon, 2021-05-10 at 13:55 +0200, Mauro Carvalho Chehab wrote:
> > This patch series is doing conversion only when using ASCII makes
> > more sense than using UTF-8.
> >
> > See, a number of converted documents ended with weird characters
> > like ZERO WIDTH NO-BREAK SPACE (U+FEFF) character. This specific
> > character doesn't do any good.
> >
> > Others use NO-BREAK SPACE (U+A0) instead of 0x20. Harmless, until
> > someone tries to use grep[1].
>
> Replacing those makes sense. But replacing emdashes — which are a
> distinct character that has no direct replacement in ASCII and which
> people do *deliberately* use instead of hyphen-minus — does not.
>
> Perhaps stick to those two, and any cases where an emdash or endash has
> been used where U+002D HYPHEN-MINUS *should* have been used.
Ok. I'll rework the series excluding EM/EN DASH chars from it.
I'll then apply manually the changes for EM/EN DASH chars
(probably on a separate series) where it seems to fit. That should
make easier to discuss such replacements.
> And please fix your cover letter which made no reference to 'grep', and
> only presented a completely bogus argument for the change instead.
OK!
Regards,
Mauro
next prev parent reply other threads:[~2021-05-11 9:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 10:26 [PATCH 00/53] Get rid of UTF-8 chars that can be mapped as ASCII Mauro Carvalho Chehab
2021-05-10 10:26 ` [PATCH 34/53] docs: networking: scaling.rst: avoid using UTF-8 chars Mauro Carvalho Chehab
2021-05-10 10:26 ` [PATCH 35/53] docs: networking: devlink: devlink-dpipe.rst: " Mauro Carvalho Chehab
2021-05-10 10:26 ` [PATCH 36/53] docs: networking: device_drivers: " Mauro Carvalho Chehab
2021-05-10 10:52 ` [PATCH 00/53] Get rid of UTF-8 chars that can be mapped as ASCII Thorsten Leemhuis
2021-05-10 11:19 ` Mauro Carvalho Chehab
2021-05-10 12:27 ` Mauro Carvalho Chehab
2021-05-10 10:54 ` David Woodhouse
2021-05-10 11:55 ` Mauro Carvalho Chehab
2021-05-10 13:16 ` Edward Cree
2021-05-10 13:38 ` Mauro Carvalho Chehab
2021-05-10 13:58 ` Edward Cree
2021-05-10 13:59 ` Matthew Wilcox
2021-05-10 14:33 ` Edward Cree
2021-05-11 9:00 ` Mauro Carvalho Chehab
2021-05-11 9:19 ` David Woodhouse
2021-05-10 13:49 ` David Woodhouse
2021-05-10 19:22 ` Theodore Ts'o
2021-05-11 9:37 ` Mauro Carvalho Chehab
2021-05-11 9:25 ` Mauro Carvalho Chehab [this message]
2021-05-10 14:00 ` Ben Boeckel
2021-05-10 21:57 ` Adam Borowski
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=20210511112508.4547bca8@coco.lan \
--to=mchehab+huawei@kernel$(echo .)org \
--cc=alsa-devel@alsa-project$(echo .)org \
--cc=corbet@lwn$(echo .)net \
--cc=coresight@lists$(echo .)linaro.org \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=dwmw2@infradead$(echo .)org \
--cc=intel-gfx@lists$(echo .)freedesktop.org \
--cc=intel-wired-lan@lists$(echo .)osuosl.org \
--cc=keyrings@vger$(echo .)kernel.org \
--cc=kvm@vger$(echo .)kernel.org \
--cc=linux-acpi@vger$(echo .)kernel.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-edac@vger$(echo .)kernel.org \
--cc=linux-ext4@vger$(echo .)kernel.org \
--cc=linux-f2fs-devel@lists$(echo .)sourceforge.net \
--cc=linux-fpga@vger$(echo .)kernel.org \
--cc=linux-hwmon@vger$(echo .)kernel.org \
--cc=linux-iio@vger$(echo .)kernel.org \
--cc=linux-input@vger$(echo .)kernel.org \
--cc=linux-integrity@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-media@vger$(echo .)kernel.org \
--cc=linux-pci@vger$(echo .)kernel.org \
--cc=linux-pm@vger$(echo .)kernel.org \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=linux-riscv@lists$(echo .)infradead.org \
--cc=linux-sgx@vger$(echo .)kernel.org \
--cc=linux-usb@vger$(echo .)kernel.org \
--cc=mjpeg-users@lists$(echo .)sourceforge.net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=rcu@vger$(echo .)kernel.org \
--cc=x86@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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