From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 1/5] board/armadeus: replace utf-8 graphic sympols by ascii characters
Date: Sun, 19 May 2019 11:08:53 +0200 [thread overview]
Message-ID: <20190519090853.GA4569@scaer> (raw)
In-Reply-To: <20190518233634.432e4b00@windsurf>
Peter, Thomas, Peter, All,
On 2019-05-18 23:36 +0200, Thomas Petazzoni spake thusly:
> On Wed, 8 May 2019 19:28:18 +0200
> Peter Seiderer <ps.report@gmx.net> wrote:
>
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> > ---
> > board/armadeus/readme.txt | 10 +++++-----
> > 1 file changed, 5 insertions(+), 5 deletions(-)
>
> Series applied to master. Thanks!
Sorry, but I still fail to see why we want to remove non-ascii chars,
especially in docs and the likes. The commit logs for these patches fail
to explain the problem they fix, if there is even a problem.
This whole "no UTF-8 chars patches" are totally nonsense nowadays. If
your system still can't display them properly, upgrade and get a decent
font.
Now, if I need to add a comment like:
# As explained by Fr?d?ric in [0], blurb da dee woops blabla...
then, check-package whines. While "Fr?d?ric" can be easily asciified to
Frederic, this is not nice and there are a lot of names that can't be
easily asciified, like ??? or anyone whose language is not using a
latin script.
I agree that the unicode NO-BREAK-SPACE (U+00A0, UTF-8 C2A0) is nasty,
and should be replaced, but otherwise it feels like we're going
something like 30 years back in time...
BTW, a good editor can be made to report such "trolling" chars. For
example, there is a plugin for vim that can highlight such chars, like
NO-BREAK-SPACE "?" (U+00A0) which is highlighted red for me here:
https://github.com/vim-utils/vim-troll-stopper
And for emacs (untested, I don't use emacs):
https://www.emacswiki.org/emacs/highlight-chars.el
Regards,
Yann E. MORIN.
PS. Yes, I was the first one to report and fix U+00A0 (C2 A0) in
5d436ac5a6 and 911ac036e0, but those were fixing real problems.
YEM.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2019-05-19 9:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 17:28 [Buildroot] [PATCH v1 1/5] board/armadeus: replace utf-8 graphic sympols by ascii characters Peter Seiderer
2019-05-08 17:28 ` [Buildroot] [PATCH v1 2/5] board/beagleboardx15: " Peter Seiderer
2019-05-08 17:28 ` [Buildroot] [PATCH v1 3/5] board/beaglebone: " Peter Seiderer
2019-05-08 17:28 ` [Buildroot] [PATCH v1 4/5] board/csky: " Peter Seiderer
2019-05-08 17:28 ` [Buildroot] [PATCH v1 5/5] board/pandaboard: " Peter Seiderer
2019-05-18 21:36 ` [Buildroot] [PATCH v1 1/5] board/armadeus: " Thomas Petazzoni
2019-05-19 9:08 ` Yann E. MORIN [this message]
2019-05-19 21:42 ` Peter Seiderer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190519090853.GA4569@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox