Hi,
Well I'm back to the stage I was at before I moved over to sablepath
from a classpath 0.02. I found that I had to set a rather obscure
property. Surely the VM integrators guide should mention these things.
The property needed to be set so that EncodingManager could be used to
load some other properties. Anyhow, the list of properties I set in
VMSystem.insertSystemProperties is:
line.separator - \n
file.separator - /
path.separator - :
gnu.java.io.encoding_scheme_alias.ISO-8859-1 - 8859_1
The last property stops the JVM trying to load
gnu/java/io/decode/DecoderISO-8859-1 and switches it to loading
gnu/java/io/decode/Decoder8859_1 . If the default action is to load
DecoderISO-8859-1 then shouldn't the java file be called
DecoderISO-8859-1 rather than Decoder8859_1 ?
Anyhow, I'd love to know if I'm missing any obvious properties I'm
forgetting to set. Are the .properties files being pulled across from
classpath to sablepath? Should we alter the decoder naming scheme?
All the best,
Ian Rogers
-The University of Manchester
-http://www.cs.man.ac.uk/~rogersi5/
|
