[PATCH 00/53] Get rid of UTF-8 chars that can be mapped as ASCII
Mauro Carvalho Chehab
mchehab+huawei at kernel.org
Tue May 11 02:25:08 PDT 2021
Em Mon, 10 May 2021 14:49:44 +0100
David Woodhouse <dwmw2 at 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.
> 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.
More information about the linux-riscv