On 10.05.21 14:55, Mauro Carvalho Chehab wrote:
The main point on this series is to replace just the occurrences
where ASCII represents the symbol equally well, e. g. it is limited
for those chars:

        - U+2010 ('‐'): HYPHEN
        - U+00ad ('­'): SOFT HYPHEN
        - U+2013 ('–'): EN DASH
        - U+2014 ('—'): EM DASH

        - U+2018 ('‘'): LEFT SINGLE QUOTATION MARK
        - U+2019 ('’'): RIGHT SINGLE QUOTATION MARK
        - U+00b4 ('´'): ACUTE ACCENT

        - U+201c ('“'): LEFT DOUBLE QUOTATION MARK
        - U+201d ('”'): RIGHT DOUBLE QUOTATION MARK

        - U+00d7 ('×'): MULTIPLICATION SIGN
        - U+2212 ('−'): MINUS SIGN

        - U+2217 ('∗'): ASTERISK OPERATOR
          (this one used as a pointer reference like "*foo" on C code
           example inside a document converted from LaTeX)

        - U+00bb ('»'): RIGHT-POINTING DOUBLE ANGLE QUOTATION MARK
          (this one also used wrongly on an ABI file, meaning '>')

        - U+00a0 (' '): NO-BREAK SPACE
        - U+feff (''): ZERO WIDTH NO-BREAK SPACE

Using the above symbols will just trick tools like grep for no good
reason.
Since when is ASCII able to represent dashes and all those quotation marks? As far as I remember, these characters were the main reason to ditch ASCII in favor of national text encodings.


_______________________________________________
Linux-f2fs-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

Reply via email to