From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] dtv-scan-tables: rename file to have only ASCII characters
Date: Mon, 14 Nov 2016 22:12:35 +0100 [thread overview]
Message-ID: <20161114221235.2f101d88@free-electrons.com> (raw)
In-Reply-To: <20161114211024.GC3399@free.fr>
Hello,
On Mon, 14 Nov 2016 22:10:24 +0100, Yann E. MORIN wrote:
> At first, I was not very happy about this, because the filename is also
> displayed to the user, so it would make sense to keep localised names.
>
> However, you are right that there is no standard way to encode
> filenames, so this is not very reliable to depend on the filename to
> provide a user-visible representation of the city/country/... Instead,
> the location should be encoded in the file itself, possibly using the
> filename as a ascii-only fallback.
There are already many many other files that should have non-ASCII
characters to accurately represent the name of the city or region, but
that don't have them. From the commit log of the patch I just sent
upstream:
- pl-Wroclaw should be written pl-Wroc?aw
- se-Laxsjo should be written se-Laxsj?
- de-Dusseldorf should be written de-D?sseldorf
- vn-Thaibinh should be written vn-Th?i_B?nh
> > + mv $(TARGET_DIR)/usr/share/dvb/dvb-t/pl-Krosno_Sucha* \
> > + $(TARGET_DIR)/usr/share/dvb/dvb-t/pl-Krosno_Sucha_Gora
>
> Can't you do that in a post-extrat or post-patch hook?
Sure, v2 coming.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-11-14 21:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 20:55 [Buildroot] [PATCH] dtv-scan-tables: rename file to have only ASCII characters Thomas Petazzoni
2016-11-14 21:10 ` Yann E. MORIN
2016-11-14 21:12 ` Thomas Petazzoni [this message]
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=20161114221235.2f101d88@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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