I'm encountering failures running an XLST filter which worked fine on Open Office, but fails after the switch to LibreOffice. I asked in the user forums and they said to open a bug. Here are the details: I made the switch from OpenOffice to LibreOffice. However, I have an XML Filter I use with calc which worked fine in OpenOffice, but fails in LibreOffice Calc 3.4.1 (LibreOffice 3.4.1 OOO340m1 (Build:103)) (on Windows XP SP3) When I run Tools - XML Filter Settings - Test XSLTs against my current file - I don't get any apparent failures (not sure what output to expect though) When I run File - Export - select my transformation - save - I get a popup: "Error saving the document ... Write Error. The file could not be written." I suspect there is something about the XSLT script that the new version doesn't like, and wasn't detected in the OpenOffice version. However, in OpenOffice I was able to debug this via: Tools - Options - OpenOffice - Java - <select a run time environment> - assign a start parameter: -DXSLTransformer.statsfile=/xslt_debug.txt which would cause the xslt transformation messages to be written to c:/xslt_debug.txt This does not appear to be working in LibreOffice. So - is there another way to get the output in LibreOffice? Or any other ideas how to debug this? I tried java se 1.6.0_21 on anothers suggestion, and also upgraded to 3.4.2 including installing the 3.4.2 SDK - but it didn't help. Thanks much
Do you have any example files ?
No examples at the moment - the data is classified. How can I capture the error output from running of the XSLT script? There are really three problems to resolve: 1) why is the filter failing (probably my problem) 2) How do I get the script output to debug? 3) The really poor non-helpful error message (".. file could not be written"). If I can figure out how to get the script output - I think I can create a public example for further debug. Thx
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian