A Chinese user of Saxon on .NET has reported a problem with character
encoding gb2312.
As far as I can see Saxon is simply calling
new OutputStreamWriter(System.err)
and this fails with the message
Encoding: gb2312 not found
The significant part of the stack trace is:
gnu.classpath.ServiceFactory.lookupProviders(Class spi) +0
java.nio.charset.Charset.providers2() +261
java.nio.charset.Charset.charsetForName(String ) +68
java.nio.charset.Charset.forName(String charsetName) +81
java.io.OutputStreamWriter..ctor(OutputStream out) +237
This is with Saxon 9.0, which is still using IKVM 0.32.0.0.
I can understand that gb2312 might not be available, but if it isn't
available then why has OutputStreamWriter() decided to use it? Is there any
way of influencing it to choose something else?
Regards,
Michael Kay
http://www.saxonica.com/-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace_______________________________________________
Ikvm-developers mailing list
Ikvm-developers@...
https://lists.sourceforge.net/lists/listinfo/ikvm-developers