* C.UTF-8 may not be present resulting in failed build
@ 2015-11-02 18:47 Andrei Borzenkov
2015-11-02 22:04 ` Mike Gilbert
2015-11-03 18:44 ` Vladimir 'phcoder' Serbinenko
0 siblings, 2 replies; 4+ messages in thread
From: Andrei Borzenkov @ 2015-11-02 18:47 UTC (permalink / raw)
To: The development of GNU GRUB
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 en@quot rules) does not use it. Is forcing
this locale really needed?
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: C.UTF-8 may not be present resulting in failed build
2015-11-02 18:47 C.UTF-8 may not be present resulting in failed build Andrei Borzenkov
@ 2015-11-02 22:04 ` Mike Gilbert
2015-11-03 18:44 ` Vladimir 'phcoder' Serbinenko
1 sibling, 0 replies; 4+ messages in thread
From: Mike Gilbert @ 2015-11-02 22:04 UTC (permalink / raw)
To: The development of GNU GRUB
On Mon, Nov 2, 2015 at 1:47 PM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
> Extra catalogs added in da0d5b3f explicitly require C.UTF-8 locale. This
> locale may not be present (e.g. openSUSE does not have it).
I think it is specific to Debian-derived distros actually. We don't
have it on Gentoo either.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: C.UTF-8 may not be present resulting in failed build
2015-11-02 18:47 C.UTF-8 may not be present resulting in failed build Andrei Borzenkov
2015-11-02 22:04 ` Mike Gilbert
@ 2015-11-03 18:44 ` Vladimir 'phcoder' Serbinenko
2015-11-04 8:14 ` Andrei Borzenkov
1 sibling, 1 reply; 4+ messages in thread
From: Vladimir 'phcoder' Serbinenko @ 2015-11-03 18:44 UTC (permalink / raw)
To: The development of GRUB 2
[-- Attachment #1: Type: text/plain, Size: 663 bytes --]
Le 2 nov. 2015 7:48 PM, "Andrei Borzenkov" <arvidjaar@gmail.com> 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 en@quot 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
_______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
[-- Attachment #2: Type: text/html, Size: 917 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: C.UTF-8 may not be present resulting in failed build
2015-11-03 18:44 ` Vladimir 'phcoder' Serbinenko
@ 2015-11-04 8:14 ` Andrei Borzenkov
0 siblings, 0 replies; 4+ messages in thread
From: Andrei Borzenkov @ 2015-11-04 8:14 UTC (permalink / raw)
To: grub-devel
03.11.2015 21:44, Vladimir 'phcoder' Serbinenko пишет:
> Le 2 nov. 2015 7:48 PM, "Andrei Borzenkov" <arvidjaar@gmail.com> 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 en@quot 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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-11-04 8:14 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-11-02 18:47 C.UTF-8 may not be present resulting in failed build Andrei Borzenkov
2015-11-02 22:04 ` Mike Gilbert
2015-11-03 18:44 ` Vladimir 'phcoder' Serbinenko
2015-11-04 8:14 ` Andrei Borzenkov
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.