On 05/10/2015 05:00 AM, Orion Poplawski wrote:
More and more tests/builds appear to require a UTF-8 locale. Perhaps
it's time to have rpm set LANG=C.UTF-8?
Which?
IMO, these packages are broken. Packages must support "C" and be able to
fall back to "C"
Ralf
--
devel mailing list
devel@lis
On Mon, May 11, 2015 at 12:22 PM, Petr Pisar wrote:
> On 2015-05-10, Nico Kadel-Garcia wrote:
>> If a build system needs a particular language, it should be in the
>> build scripts themselves. People do local, personal compilation in
>> environments that use other languages, and in 'LANG=C' or 'L
On 11/05/15 04:43, Lars Seipel wrote:
> On Sun, May 10, 2015 at 09:02:31AM +0200, Matěj Cepl wrote:
>> Which part f C.UTF-8 is not covered by en_US.UTF-8?
>
> Let's see:
>
> % export LC_COLLATE=C
> % bash -c 'case b in [A-Z]) echo upper;; *) echo lower;; esac'
> lower
>
> Ok. Now en_US.UTF-8:
>
On 2015-05-10, Nico Kadel-Garcia wrote:
> If a build system needs a particular language, it should be in the
> build scripts themselves. People do local, personal compilation in
> environments that use other languages, and in 'LANG=C' or 'LANG=POSIX'
> to fix the case-sensitive sorting problem for
On Sun, May 10, 2015 at 09:02:31AM +0200, Matěj Cepl wrote:
> Which part f C.UTF-8 is not covered by en_US.UTF-8?
Let's see:
% export LC_COLLATE=C
% bash -c 'case b in [A-Z]) echo upper;; *) echo lower;; esac'
lower
Ok. Now en_US.UTF-8:
% export LC_COLLATE=en_US.UTF-8
% bash -c 'case b in [A-Z]
On Sat, May 9, 2015 at 11:00 PM, Orion Poplawski wrote:
> More and more tests/builds appear to require a UTF-8 locale. Perhaps it's
> time to have rpm set LANG=C.UTF-8?
If a build system needs a particular language, it should be in the
build scripts themselves. People do local, personal compilat
On 2015-05-10, 03:00 GMT, Orion Poplawski wrote:
> More and more tests/builds appear to require a UTF-8 locale. Perhaps
> it's time to have rpm set LANG=C.UTF-8?
Which part f C.UTF-8 is not covered by en_US.UTF-8?
Best,
Matěj
--
http://www.ceplovi.cz/matej/, Jabber: mceplceplovi.cz
GPG Finger
More and more tests/builds appear to require a UTF-8 locale. Perhaps
it's time to have rpm set LANG=C.UTF-8?
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA DivisionFAX: 303-415-9702
3380 Mitchell Lane or...@cora.nwra.com
Hi Ian,
On 08/25/2013 04:17 PM, Ian Pilcher wrote:
> I'm trying to build a jpackage SRPM (jena-iri) on Fedora 19, and it's
> failing, because the locale (LANG) is apparently set to "C" during the
> build. (javac and javadoc don't like non-ASCII characters in source
> files in an ASCII locale.)
>
sön 2013-08-25 klockan 23:13 +0200 skrev punto...@libero.it:
> Il 25/08/2013 22:17, Ian Pilcher ha scritto:
> > I'm trying to build a jpackage SRPM (jena-iri) on Fedora 19, and it's
> > failing, because the locale (LANG) is apparently set to "C" during the
> > build. (javac and javadoc don't like
Il 25/08/2013 22:17, Ian Pilcher ha scritto:
I'm trying to build a jpackage SRPM (jena-iri) on Fedora 19, and it's
failing, because the locale (LANG) is apparently set to "C" during the
build. (javac and javadoc don't like non-ASCII characters in source
files in an ASCII locale.)
What's the bes
I'm trying to build a jpackage SRPM (jena-iri) on Fedora 19, and it's
failing, because the locale (LANG) is apparently set to "C" during the
build. (javac and javadoc don't like non-ASCII characters in source
files in an ASCII locale.)
What's the best way to set it to a UTF-8? (Should I just add
12 matches
Mail list logo
