3:17 p.m.
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 "export
LANG=en_US.UTF-8" to the relevant sections of the SPEC file?)
Thanks!
--
========================================================================
Ian Pilcher arequipeno(a)gmail.com
Sometimes there's nothing left to do but crash and burn...or die trying.
========================================================================
4:13 p.m.
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 best way to set it to a UTF-8? (Should I just add "export
LANG=en_US.UTF-8" to the relevant sections of the SPEC file?)
Thanks!
hi
convert the sources code wiith non-ASCII characters with
native2ascii
e.g.
native2ascii -encoding UTF8 A.java A.java
regards
10:10 p.m.
sön 2013-08-25 klockan 23:13 +0200 skrev puntogil(a)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 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 "export
> LANG=en_US.UTF-8" to the relevant sections of the SPEC file?)
>
> Thanks!
>
hi
convert the sources code wiith non-ASCII characters with
native2ascii
e.g.
native2ascii -encoding UTF8 A.java A.java
regards
In almost all cases converting to ascii is not an acceptable solution.
Not only for java source but for any text. Blindly converting java
sources to ascii can introduce bugs, since - unlike C and C++ - you are
allowed to use non-ascii characters in variable names and other
identifiers in java sources. Even if non-ascii characters are only
present in comments, those may end up in the javadoc documentation, so
converting to ascii is likely to introduce documentation bugs.
Better fix the broken build instructions to correctly state what
encoding is used by the project. E.g. by adding
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>
to the pom-file, or add -Dproject.build.sourceEncoding=UTF-8 to the
build on the command line.
Mattias
9:52 a.m.
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.)
What's the best way to set it to a UTF-8? (Should I just add "export
LANG=en_US.UTF-8" to the relevant sections of the SPEC file?)
I see that Mattias Ellert has already suggested fixing the encoding
being used by the java compiler to match the encoding used in actual
files. I just wanted to chime in and point out that there is a list of
common problems (and fixes) that you may run into when rebuilding older
packages against newer Java versions:
https://fedoraproject.org/wiki/Java7_Package_Rebuild_Status#Issues_descri...
Feel free to drop by #fedora-java if you run into more of these problems.
Cheers,
Omair
--
PGP Key: 66484681 (http://pgp.mit.edu/)
Fingerprint = F072 555B 0A17 3957 4E95 0056 F286 F14F 6648 4681
3943
days inactive
3944
days old
3 comments
4 participants
participants (4)
-
gil -
Ian Pilcher -
Mattias Ellert -
Omair Majid