Phillip Susi writes:
> On 8/13/2014 7:53 AM, Ludovic Courtès wrote:
>> Hello,
>>
>> t0251-gpt-unicode.sh requires the C.UTF-8 locale and fails if it
>> isn’t available.
>>
>> What about:
>>
>> 1. Exiting with 77 when the locale is unavailable?
>>
>> 2. Choosing another locale, such as en_US.u
Phillip Susi skribis:
> How can the C locale possibly not exist on a system that is not
> totally broken? It is the default and fallback locale when you don't
> have any locales installed.
C always exists, but C.UTF-8 no.
Ludo’.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/13/2014 7:53 AM, Ludovic Courtès wrote:
> Hello,
>
> t0251-gpt-unicode.sh requires the C.UTF-8 locale and fails if it
> isn’t available.
>
> What about:
>
> 1. Exiting with 77 when the locale is unavailable?
>
> 2. Choosing another locale, suc
On Wed, Aug 13, 2014 at 09:55:26PM +0200, Ludovic Courtès wrote:
> The test could look for a valid UTF-8 locale like this:
>
> --8<---cut here---start->8---
> found_locale=no
> for locale in en_US de_DE fr_FR es_ES
> do
> LC_ALL="$locale.utf8"
>
> # In a UT
"Brian C. Lane" skribis:
> See my patch here:
>
> http://lists.alioth.debian.org/pipermail/parted-devel/2014-July/004568.html
-export LC_ALL=C.UTF-8
+if [ -e "/usr/share/locale/en_US/" ]; then
+export LC_ALL=en_US.UTF-8
+else
+export LC_ALL=C.UTF-8
+fi
The problem is that this directory
Hello,
t0251-gpt-unicode.sh requires the C.UTF-8 locale and fails if it isn’t
available.
What about:
1. Exiting with 77 when the locale is unavailable?
2. Choosing another locale, such as en_US.utf8? As of GNU libc 2.19,
C.UTF-8 (or any other spelling) does not exist.
Thanks,
Ludo’.
