I agree. This is a remnant of the first original Ant script done many years ago and really I should have deleted it. The good news I guess is that it's now possible to override it in tools R8 release a couple of hours ago.
Xav On Mon, Dec 6, 2010 at 10:01 AM, Matt Quigley <[email protected]> wrote: > We are externalizing all of our text; we support both English and > Spanish. There still are valid occurrences of non-ascii strings > appearing in .java files. > > Nonetheless, this is not a "feature" this is a "bug". Ascii is > neither the default encoding of Java, nor even the correct encoding to > use for Android applications. > > I created a bug here: > http://code.google.com/p/android/issues/detail?id=12924 > > On Dec 2, 9:30 pm, Zsolt Vasvari <[email protected]> wrote: >> Totally agree. >> >> I just changed all my instances of non-ASCII characters to use the >> \uXXXX notation (I have a few for currency codes and for a minus sign >> where I use a long-dash for asthetic reasons instead of a regular -). >> That said, having non-ASCII in your source file probably means that >> you should be externalizing text, unless you write comments in your >> native language, but guessing by your name, that's not the case. >> >> On Dec 3, 1:18 am, Matt Quigley <[email protected]> wrote: >> >> >> >> >> >> >> >> > First of all, I find it odd that the encoding is even specified at >> > all. Why not just leave it as the default system encoding? >> >> > Secondly, if one is going to specify an encoding, then it should NOT >> > be ascii. It should be UTF-8. After all, the files themselves are >> > not ascii, they are UTF-8 (or Cp1252). >> >> > Thirdly, the Eclipse compiler does not use ascii. This is why you see >> > tons of "warning: unmappable character for encoding ascii" when using >> > ant to compile your project, but you don't see that with Eclipse. >> >> > I believe this isn't just a nuance, I believe it to be a bug. If you >> > use a non-ascii character, such as a vowel with an accent in any .java >> > or .xml file, the compiler may not interpret those PERFECTLY VALID >> > characters correctly. >> >> > One can, of course, change it yourself, by looking in <sdk.dir>/tools/ >> > ant, and removing all occurrences of encoding="ascii", but if you have >> > to do this to make your programs correct, then this indicates a bug in >> > the toolset. (At the very least, it should be a changeable property, >> > such as ${java.encoding}. >> >> > But, I would like to know if there is a good reason for overriding the >> > default Java encoding. >> >> > Thanks, >> > -Matt > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Xavier Ducrohet Android SDK Tech Lead Google Inc. Please do not send me questions directly. Thanks! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
