Xueming Shen wrote:
Obviously your locale setting is not being "exported"...what "shell" are
you using?
It's bash. I'm pretty sure it's exported, because env sees it, and env
isn't a shell builtin in bash (at least not yet :).
You can try to set your locale to en_US.ISO8859-1 explicitly at
Obviously your locale setting is not being "exported"...what "shell" are
you using?
You can try to set your locale to en_US.ISO8859-1 explicitly at command
line first,
type in "locale" to confirm that your locale is being set correctly to
en_US.ISO8859-1,
then run the "find + java" to see if t
It still errors with a file not found:
+ LC_ALL=en_US.ISO8859-1
+ export LC_ALL
+ find /home/dstromberg/Sound/Music -type f -print
+ java -Xmx512M -jar equivs.jar equivs.main
java.io.FileNotFoundException: /home/dstromberg/Sound/Music/Various
Artists/Dreamland/11 - Canci??n Para Dormir a un Ni?
Martin, don't trap people into using -Dfile.encoding, always treat it as
a read only property:-)
I believe initializeEncoding(env) gets invoked before -Dxyz=abc
overwrites the default one,
beside the "jnu encoding" is introduced in 6.0, so we no longer look
file.encoding since, I believe
y
Sadly, I'm still getting ghost files with C and ISO-8859-1:
./wrapper
+ case 3 in
+ export LC_ALL=C
+ LC_ALL=C
+ export LC_CTYPE=C
+ LC_CTYPE=C
+ export LANG=C
+ LANG=C
+ find /home/dstromberg/Sound/Music -type f -print
+ java -Xmx512M -Dfile.encoding=ISO-8859-1 -jar equivs.jar equivs.main
java.
