From: Michael J Gruber <git@drmicha.warpmail.net>
To: Yann Droneaud <yann@droneaud.fr>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] t9129: fix UTF-8 locale detection
Date: Tue, 18 May 2010 18:05:16 +0200 [thread overview]
Message-ID: <4BF2BABC.2010405@drmicha.warpmail.net> (raw)
In-Reply-To: <1274193685-5468-1-git-send-email-yann@droneaud.fr>
Yann Droneaud venit, vidit, dixit 18.05.2010 16:41:
> Since I don't have en_US.utf8, some tests failed:
>
> * UTF-8 locale not available, test skipped
> * skip 10: ISO-8859-1 should match UTF-8 in svn
> * skip 11: eucJP should match UTF-8 in svn
> * skip 12: ISO-2022-JP should match UTF-8 in svn
>
> On my system locale -a reports:
>
> en_US
> en_US.ISO-8859-1
> en_US.UTF-8
>
locale -a|grep en_US
en_US
en_US.iso88591
en_US.iso885915
en_US.utf8
This is on Fedora 13, which is not exactly exotic. What is your system?
> According to Wikipedia utf8 is not a correct name
> for the UTF-8 encoding:
> http://en.wikipedia.org/wiki/UTF-8#Official_name_and_incorrect_variants
>
> And compare_svn_head_with() is explicitly using en_US.UTF-8
> locale.
>
> Signed-off-by: Yann Droneaud <yann@droneaud.fr>
> ---
> t/t9129-git-svn-i18n-commitencoding.sh | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/t/t9129-git-svn-i18n-commitencoding.sh b/t/t9129-git-svn-i18n-commitencoding.sh
> index b9224bd..ec6ed4f 100755
> --- a/t/t9129-git-svn-i18n-commitencoding.sh
> +++ b/t/t9129-git-svn-i18n-commitencoding.sh
> @@ -69,7 +69,7 @@ do
> '
> done
>
> -if locale -a |grep -q en_US.utf8; then
> +if locale -a |grep -q en_US.UTF-8; then
> test_set_prereq UTF8
> else
> say "UTF-8 locale not available, test skipped"
Funny thing is the test succeeds for me, even when run within
LANG=en_US.iso88591.
So I'd suggest to use
-if locale -a |grep -q en_US.utf8; then
+if locale -a |egrep -q 'en_US.utf8|en_US.UTF-8'; then
and embrace for more variants to appear down the road...
Michael
next prev parent reply other threads:[~2010-05-18 16:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 14:41 [PATCH] t9129: fix UTF-8 locale detection Yann Droneaud
2010-05-18 16:05 ` Michael J Gruber [this message]
2010-05-18 17:08 ` Yann Droneaud
2010-05-18 17:16 ` Yann Droneaud
2010-05-18 17:45 ` Linus Torvalds
2010-05-18 19:58 ` Andreas Schwab
2010-05-18 20:00 ` Linus Torvalds
2010-05-18 20:49 ` Yann Droneaud
2010-05-19 15:16 ` Yann Droneaud
2010-06-02 19:14 ` Re* " Junio C Hamano
2010-05-24 17:08 ` Yann Droneaud
2010-05-25 7:33 ` Michael J Gruber
2011-01-06 14:22 ` [PATCH/RFC 0/4] en_US.UTF-8 " Yann Droneaud
2011-01-06 14:22 ` [PATCH 1/4] test: add a library to detect an en_US.UTF-8 locale Yann Droneaud
2011-01-07 18:37 ` Junio C Hamano
2011-01-06 14:22 ` [PATCH 2/4] test-lib.sh: add test_utf8() function Yann Droneaud
2011-01-07 18:45 ` Junio C Hamano
2011-01-06 14:22 ` [PATCH 3/4] test: use test_utf8 and GIT_LC_UTF8 where an en_US.UTF-8 locale is required Yann Droneaud
2011-01-07 18:48 ` Junio C Hamano
2011-01-06 14:22 ` [PATCH 4/4] t9129: use "$PERL_PATH" instead of "perl" Yann Droneaud
2011-01-07 18:49 ` Junio C Hamano
2010-05-18 20:37 ` [PATCH] t9129: fix UTF-8 locale detection Yann Droneaud
2010-05-19 2:44 ` Miles Bader
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=4BF2BABC.2010405@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=yann@droneaud.fr \
/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;
as well as URLs for NNTP newsgroup(s).