I've updated OmegaT for F15 and F16[1] without novelty. But compiling in rawhide showed a strange to me error: «error: unmappable character for encoding ASCII»[2].
In a first approach the suspects were some strange coded chars (which 1.6 can eat, btw) but after patching them I found in local tests the same error with the*'ß' letter [3]. The file codification seems to be common UTF-8.
I'm not a programmer at all but this sounds _very_ weird to me. Is anybody aware if openjdk 1.7 has some bug related with UNICODE or similar? I didn't find anything like this in BZ. Any other idea?
--
java-devel mailing list
java-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/java-devel
11-21-2011, 08:30 PM
Deepak Bhole
Java 7 can't understand some chars
* Ismael Olea <ismael@olea.org> [2011-11-21 15:00]:
> Hi:
>
> I've updated OmegaT for F15 and F16[1] without novelty. But compiling
> in rawhide showed a strange to me error: «error: unmappable character
> for encoding ASCII»[2].
>
> In a first approach the suspects were some strange coded chars (which
> 1.6 can eat, btw) but after patching them I found in local tests the
> same error with the 'ß' letter [3]. The file codification seems to be
> common UTF-8.
>
> I'm not a programmer at all but this sounds _very_ weird to me. Is
> anybody aware if openjdk 1.7 has some bug related with UNICODE or
> similar? I didn't find anything like this in BZ. Any other idea?
>
Hi Ismael,
This is expected behaviour with Java 7. Until Java 6, encoding errors
were only presented as warnings. Now they are errors:
"This is the default value. No language changes were introduced in Java
SE 6. However, encoding errors in source files are now reported as
errors, instead of warnings, as previously."
You can get around it by specifying -source 1.6, but fixing the source
is a better fix IMO.
Cheers,
Deepak
--
java-devel mailing list
java-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/java-devel
11-21-2011, 10:50 PM
Ismael Olea
Java 7 can't understand some chars
On Mon, Nov 21, 2011 at 10:30 PM, Deepak Bhole <dbhole@redhat.com> wrote:*
This is expected behaviour with Java 7. Until Java 6, encoding errors
were only presented as warnings. Now they are errors:
--
java-devel mailing list
java-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/java-devel
11-21-2011, 11:03 PM
Orion Poplawski
Java 7 can't understand some chars
On 11/21/2011 02:30 PM, Deepak Bhole wrote:
>
> This is expected behaviour with Java 7. Until Java 6, encoding errors
> were only presented as warnings. Now they are errors:
>
> http://docs.oracle.com/javase/7/docs/technotes/tools/windows/javac.html
>
> "This is the default value. No language changes were introduced in Java
> SE 6. However, encoding errors in source files are now reported as
> errors, instead of warnings, as previously."
>
> You can get around it by specifying -source 1.6, but fixing the source
> is a better fix IMO.
How does one fix the source?
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion@cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
--
java-devel mailing list
java-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/java-devel
11-21-2011, 11:36 PM
Deepak Bhole
Java 7 can't understand some chars
* Orion Poplawski <orion@cora.nwra.com> [2011-11-21 19:04]:
> On 11/21/2011 02:30 PM, Deepak Bhole wrote:
> >
> >This is expected behaviour with Java 7. Until Java 6, encoding errors
> >were only presented as warnings. Now they are errors:
> >
> >http://docs.oracle.com/javase/7/docs/technotes/tools/windows/javac.html
> >
> >"This is the default value. No language changes were introduced in Java
> >SE 6. However, encoding errors in source files are now reported as
> >errors, instead of warnings, as previously."
> >
> >You can get around it by specifying -source 1.6, but fixing the source
> >is a better fix IMO.
>
> How does one fix the source?
>
By removing the encoding errors. The problem only occurs if there is an
error in the encoding i.e. file contains characters not defined by
that encoding.
* Ismael Olea <ismael@olea.org> [2011-11-21 18:50]:
> On Mon, Nov 21, 2011 at 10:30 PM, Deepak Bhole <[1]dbhole@redhat.com>
> wrote:
>
> This is expected behaviour with Java 7. Until Java 6, encoding
> errors
> were only presented as warnings. Now they are errors:
> [2]http://docs.oracle.com/javase/7/docs/technotes/tools/windows/java
> c.html
> "This is the default value. No language changes were introduced in
> Java
> SE 6. However, encoding errors in source files are now reported as
> errors, instead of warnings, as previously."
>
> Aha
>
> You can get around it by specifying -source 1.6, but fixing the
> source
> is a better fix IMO.
>
> Thanks for the tip! I fixed it[1]
> btw, which is the default encoding for openjdk?
It is set by the system. You can check for it by printing the
file.encoding system property. On Fedora, it should default to UTF-8.
Java 7 can't understand some chars
