It works.
We have launched the application with another user and this user has
other environment variables.
With the setting export [EMAIL PROTECTED] all works fine.
Schapitz, the steps that you perform in the email help us.
Thanks
Th. Schapitz wrote:
The default encoding the jvm uses on *any* io
The default encoding the jvm uses on *any* io (file, network or else) is
determined by the jvm property
file.encoding.
You can do several things:
a.) check the setting in effect, by using the Echoproperties task, to
find out the current setting in effect.
b.) enforce a certain setting, e.g. by u
It can be worse - Java itself may use a different encoding. I saw
JBuilder creating strange directories on Windows when my user id
contained Cyrillic characters.
- Alexey.
Dominique Devienne wrote:
I assume you have the filename directly in the build file, no? Because if it
was picked up by a f
I assume you have the filename directly in the build file, no? Because if it
was picked up by a fileset, it would probably work.
Did you think to change the XML declaration at the top to have the proper
encoding value? I don't know for sure, but XML may default to UTF-8. --DD
> -Original