Saxon

Legacy ID: #4618724 Legacy Poster: Michael Kay (mhkay)

The simple answer is, I don't know. I'll try to find time to do some experiments. For what it's worth, the code is using java's new File(uri) on the absolutized version of the URI that you supply, and then creating a FileOutputStream for that File. This is relying on URI-to-filename conversion as implemented in GNU Classpath. A few years ago Dave Pawson did some experiments on how UNC filenames were mapped to URIs and everyone seemed to do it differently - there's basically no standard.

Legacy ID: #4618934 Legacy Poster: pvallone (pvallone)

Thanks Michael, Since I am using the .net version, I will just add a simple file copy after the tranformation in my code. All I am doing is calling the Transform.exe and passing the arguments. Is there a SAXON 8.8 .net version? Maybe I could use that instead? I appreciate the help. Phil

Legacy ID: #4619855 Legacy Poster: Michael Kay (mhkay)

The code in this area hasn't changed, I wouldn't expect it to work differently in an earlier release.

Legacy ID: #4619993 Legacy Poster: Michael Kay (mhkay)

You may have noticed another thread relating to UNC filenames started today: https://sourceforge.net/forum/message.php?msg_id=4619860 That one is about the Java product, however. The test case in that bug report works fine under Saxon on .NET, so on the input side, UNC filenames seem to be working fine using a file:////machine/folder/x.xml style of URI. For writing, however, I confirmed that these don't work. Internally Saxon is using completely different code for the two cases - the input side uses .NET libraries including the XmlResolver, while the writing side is using the GNU Classpath implementation of java.net.URI, and if that doesn't handle UNC filenames well then I'm not at all surprised. I'll note a "TODO" to consider making improvements in this area, but I'm not sure it will get an enormously high priority. Perhaps moving forward to the latest IKVMC will help - I refrained from doing that in 9.0 because of the amount of retesting that would be involved, but it's probably a good thing to do next time.

Legacy ID: #4620043 Legacy Poster: Michael Kay (mhkay)

I've added some notes on UNC filename support to the Wiki at http://saxon.wiki.sourceforge.net/UNC+filenames Michael Kay

Legacy ID: #4620118 Legacy Poster: pvallone (pvallone)

Hi Michael, Thank you very much for the help. Would I have the same problem using the Java version? Thanks,

Legacy ID: #4620122 Legacy Poster: pvallone (pvallone)

Also in reference to: http://saxon.wiki.sourceforge.net/UNC+filenames you wrote: "Specifying a regular UNC filename in the -o option on the command line appears to work, but the files are not created (at least, not in the expected place)." I can confirm that I receive no errors, and have no output.