Ant encoding problem on Windows - UTF-8 files but

问题:

Somehow I can't get my UTF-8 sources to play nice with Ant.

I get a whole lot of "warning: unmappable character for encoding ascii". I'm going crazy, really. Hours and hours and hours. Btw, I noticed 5 people already used the tag crazy. :-)

And yes, I've read this, this and others. Google also (the first 5 page results of at least 3 or 4 different searches, at least). There are javac options. I've tried. There is also some preset or something (sorry, 3 AM). Didn't work either.

I'm generating Android apk files with Ant. I can't use Eclipse, so no. And by the way, the ant documentation is gibberish to me. Those examples are of no use at all. I've lost count on how much I've tried.

I've tried using the Dfile.encoding option, tried mixing that with CHCP 65001 Windows command. Did all the combinations, and it even makes Ant (Javac I guess) stop spitting errors, but it still doesn't matter. My code still ends up with garbage carachters (a bunch of ?? instead of á, í etc).

回答1:

Are you specifying the file encoding to the compiler correctly? The java compiler will otherwise default to use the platform's default encoding, which on Windows (for example) is not UTF-8. The encoding is specified by using the -encoding flag to javac.

javac -encoding utf8 ...

And in ant build.xml:

<javac ... encoding="UTF-8" ... />

回答2:

Just specify encoding in your build.xml script:

<javac encoding="UTF-8" ... />

But for code re-use it's better to extract value into project-specific configuration file:

<property file="build.properties" />
<property name="java.encoding" value="ascii" />
<javac encoding="${java.encoding}"
       source="${java.source}" ....>
       <src path="${source.dir}" />
       <classpath>
            <fileset ... />
       </classpath>
 </javac>

And then just add java.encoding=UTF-8 to build.properties to override encoding on per-project basis.

回答3:

To all you who use UTF-8 source files on Windows and was trying to build Android packages with Proguard using the famous blog post by Dan Galpin/Tim Bray.

This encoding problem happens with javac (thanks for the tip, JesperE). However, I was unable to create a new javac rule on my project's files, because of needed parameters that I didn't know anything about. So here is the easy answer (probably not the only answer):

1. Try the usual "ant release" command.

2. Notice that, on the start, there is an output talking about some imported ANT rules. Right on the start you will see some [setup] rules. Look for this one:

   [setup] Importing rules file: tools\ant\ant_rules_r3.xml

3. Find that file and open it. Search for "javac encoding". You will see that is set to "ascii". Change to "UTF-8".

4. Do the "ant release" again and it will be fine.

That's how I did here. I'm sure there is a way to override this on a per-project basis. But it kept giving me errors on mandatory parameters, as I said. So for me at least it was that much easier doing this way. Besides, I only work with UTF-8 anyway.

回答4:

You should set the same page in many places:

1. in Ant Script javac encoding="UTF-8" ... /
2. -Dfile.encoding=UTF-8 in parameters of Ant calling

3. In file-properties-resource-encoding - again choose the same page. You can also change it for all files in the container by the IDE (preferences for Eclipse). Then make all files to inherit it from the container.

4. If some files were created in wrong encoding, rework their content through PsPad or maybe, another text editor (copy-paste, change file encoding, back copy-paste). These files will be mentioned in unmappable character errors.

After setting all these four problems you will have NO unmappable character lines.

回答5:

below is the usage of -Dfile.encoding=UTF-8 in ant build.xml file:

<java classname="${main-class}" fork="true">
<jvmarg value="-Dfile.encoding=UTF-8"/>

This will solve the problem. Working for all UTF 8 char's.