Rick Mann wrote:
>You're missing the point. The WHOLE POINT is to NOT have to specify -
>encoding this every time. It's too easy to forget to do, just as it's too
>easy to get a file that defaults to MacRoman. In general, it's easier (on
>the Mac) to set the default encoding in the various programmers' text
>editors, but Java still won't behave correctly if it's expecting MacRoman.
Then specify -encoding UTF8 in your build-process files.
AFAIK, you can specify source-encoding in an Ant build-file, though it may
not be the -encoding attribute. Check the Ant reference docs to see
exactly which attribute to use.
I don't see why you or any other human would have to remember anything, if
the source-file encoding is clearly stated in your build-process files.
The build-file remembers, so forgetful humans don't have to.
When the source encoding is specified in the build-file, you can even bring
a new machine on-line and it will just work, without having to first
configure a system-wide default encoding for it, and without making any
assumptions about what its default encoding is. The host's default could
be Chinese or Urdu and it'd still work. The default encoding could even
vary by who's logged in and it will still compile correctly.
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
