ansaurus

Question

"unmappable character for encoding" warning in Java

Answer 1

+10 A:

Use the "\uxxxx" escape format.

According to Wikipedia, the copyright symbol is unicode U+00A9 so your line should read:

String copyright = "\u00a9 2003-2008 My Company. All rights reserved.";

Jon Skeet 2009-01-21 11:20:51

Be careful with \uNNNN characters... they are parsed before doing lexical analysis. For example, if you put this comment /* c:\unit */ to your code, it will not compile anymore, because "nit" isn't correct hex number.

Peter Štibraný 2009-01-21 11:25:40

Absolutely. (This is better handled in C#, where unicode escaping is only applied in certain contexts - but then there's the dangerous \x escape sequence as well, which is awful.)

Jon Skeet 2009-01-21 11:38:31

Excellent, the escape format worked great. Thanks Jon!

seanhodges 2009-01-21 11:48:58

This sounds more like a band-aid than a cure. The real problem appears to be that you're telling javac to expect source files in UTF-8 when they're really in a single-byte encoding like ISO-8859-1 or windows-1252.

Alan Moore 2009-01-27 01:31:40

@Alan M: In my experience, it's a lot easier to make sure you won't have a problem by keeping source files in ASCII than it is to make sure you use the right encoding *everywhere* your source might be compiled (Ant, Eclipse, IDEA etc).

Jon Skeet 2009-01-27 06:38:25

The old Seven-bit Solution, sure. But character-encoding problems crop up in many other contexts, too. Every developer has to have a pretty good grasp of the issues involved.

Alan Moore 2009-01-28 07:08:19

@Alan: Yes, every developer should know about encodings etc. That doesn't mean it's a good idea to cause problems where you don't have to. I prefer portable code where you don't *have* to choose the encoding (as almost everything is ASCII-friendly).

Jon Skeet 2009-01-28 07:54:31

Answer 2

+7 A:

Try with: javac -encoding ISO-8859-1 file_name.java

Fernando Nah 2009-10-24 20:59:58

I like this solution. I added "-encoding UTF-8" as a compilerarg in my ant build.xml and I still get "warning: unmappable character for encoding ASCII". If I modify it to "-encoding jjjj" it won't compile, complaining "error: unsupported encoding: jjjj", so I know it is recognizing UTF-8, but it still seems to be treated .java files as ascii. Sigh.

dfrankow 2010-07-03 00:13:55

I tried the "encoding" parameter of the ant javac task, same problem. It recognizes the parameter, but then ignores it somehow.

dfrankow 2010-07-03 03:04:50

Answer 3

A:

If you use eclipse (Eclipse can put utf8 code for you even you write utf8 character. You will see normal utf8 character when you programming but background will be utf8 code) ;

Select Project
Right click and select Properties
Select Resource on Resource Panel(Top of right menu which opened after 2.)
You can see in Resource Panel, Text File Encoding, select other which you want

P.S : this will ok if you static value in code. For Example String test = "İİİİİııııııççççç";

javaloper 2009-12-07 07:56:16

Answer 4

A:

I had the same problem, where the character index reported in the java error message was incorrect. I narrowed it down to the double quote characters just prior to the reported position being hex 094 (cancel instead of quote, but represented as a quote) instead of hex 022. As soon as I swapped for the hex 022 variant all was fine.

Kelvin Goodson 2010-06-22 12:14:13

ansaurus

tags:

views:

answers:

"unmappable character for encoding" warning in Java

related questions