grub-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: C.UTF-8 may not be present resulting in failed build


From: Andrei Borzenkov
Subject: Re: C.UTF-8 may not be present resulting in failed build
Date: Wed, 4 Nov 2015 11:14:16 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0

03.11.2015 21:44, Vladimir 'phcoder' Serbinenko пишет:
Le 2 nov. 2015 7:48 PM, "Andrei Borzenkov" <address@hidden> a écrit :

Extra catalogs added in da0d5b3f explicitly require C.UTF-8 locale. This
locale may not be present (e.g. openSUSE does not have it).

Upstream gettext (and hence address@hidden rules) does not use it. Is forcing
this locale really needed?


We use them in tests as an easy alternative to real translations. But we
can generate them without this locale. We could replace y sed command with
bunch of s and use pain C locale

But it has C.UTF-8 not only for sed, but for all other commands invocations. Is it really needed



reply via email to

[Prev in Thread] Current Thread [Next in Thread]