On Wed, 2021-05-12 at 10:44 +0200, Mauro Carvalho Chehab wrote: > The main point here is that a large amount of those UTF-8 characters > appeared as result of document conversion from DocBook/LaTeX/Markdown. > > As the conversion ended, I don't expect the need of re-doing a series > like that in the near future. > > There are even some cases where the UTF-8 were doing wrong things, like > using an EN DASH instead of an hyphen in order to pass a command line > parameter, and the addition of non-printable BOM characters. > > So, IMO, this is a necessarily cleanup after the conversion. That part — fixing characters that are *wrong*, such as converting a UTF-8 U+2014 EM DASH to a UTF-8 U+002D HYPHEN-MINUS, is reasonable enough. But you're not "avoiding using UTF-8 chars" there, as it says in the title of this patch. HYPHEN-MINUS encoded as 0x2D *is* UTF-8. I think you meant "avoid using non-ASCII chars", and even *that* is an entirely bogus reason for doing anything at all, as discussed. Limit yourself to fixing characters which are actually wrong, and it's fine. One level of pointless trivia below spelling errors, mind you, but at least not actively wrong.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
