Re: [PATCH 00/53] Get rid of UTF-8 chars that can be mapped as ASCII
From: David Woodhouse <dwmw2@infradead.org>
Date: 2021-05-10 14:10:27
Also in:
alsa-devel, dri-devel, intel-gfx, intel-wired-lan, keyrings, kvm, linux-acpi, linux-arm-kernel, linux-doc, linux-edac, linux-ext4, linux-fpga, linux-hwmon, linux-iio, linux-integrity, linux-media, linux-pci, linux-pm, linux-rdma, linux-riscv, linux-usb, lkml, netdev, rcu
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. And please fix your cover letter which made no reference to 'grep', and only presented a completely bogus argument for the change instead.
Attachments
- smime.p7s [application/x-pkcs7-signature] 5174 bytes