Re: [PATCH 00/53] Get rid of UTF-8 chars that can be mapped as ASCII
David Woodhouse <[email protected]> Mon, 10 May 2021 14:49:44 +0100
| Newsgroups | gmane.comp.freedesktop.xorg.drivers.intel,gmane.linux.alsa.devel,gmane.comp.emulators.kvm.devel,gmane.linux.documentation,gmane.linux.kernel.iio,gmane.linux.kernel.pci,gmane.comp.video.dri.devel,gmane.linux.ports.riscv,gmane.linux.drivers.rdma,gmane.linux.acpi.devel,gmane.linux.kernel.input,gmane.comp.file-systems.ext4,gmane.linux.drivers.video-input-infrastructure,gmane.linux.power-management.general,gmane.comp.video.mjpeg.user,gmane.linux.ports.arm.kernel,gmane.linux.kernel.hwmon,gmane.linux.network,gmane.linux.usb.general,gmane.linux.kernel,gmane.linux.file-systems.f2fs |
|---|---|
| Message-ID | <[email protected]> |
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. _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
smime.p7s
(application/x-pkcs7-signature, 5.1 KB) - not displayed