Apache OpenOffice (AOO) Bugzilla – Issue 27325
XSLT filter import / export by GUI does not allow multiple stylesheets
Last modified: 2013-02-07 22:11:39 UTC
By importing / exporting a XSLT filter via the Office GUI (i.e. Tools -> XML Filter Settings) only one stylesheet is being packed / unpacked (most probably even one DTD file). This should work for multiple stylesheets and the exported JAR should work with the pkgchk as well.
SUS->LO: As discussed with MIB, we change the milestone and add the issue to specification (http://ui.openoffice.org/proposals/XMLFilterSpec.sxw)
"According to the OpenOffice.org roadmap (http://development.openoffice.org/releases/) this issue was retargeted to OOo Later." TM->SUS: retargeted as requested by MBA.
I made up my mind about this issue, it is definetly not an enhancement, but a bug as basic functionality of the XSLT 1.0 is not supported. This issue is quite severe and anoying for the user, therefore I suggest to overthink the target.
xmlfilter for you
Even if the GUI can't export a package containing multiple stylesheets, there needs to be a mechanism to (a) create such a package and (b) import it. I tried adding additional XSL files to a jar but couldn't find any way for the Open dialog to actually import more than the single top level stylesheet for my export filter.
I agree, the solution to this would be to make the imported/exported JAR packages obsolete and use UNO components (zip) as a filter, zipping a folder to a package instead importing one XSLT file. Multiple XSLT files could be zipped to the package without the need to distinguish remotely linked stylesheets. Even images and default XML fragments could be part of this zip. Additional features from the UNO packages would be versioning and possibly updating. I would like to have this in OOo 3.0, but if nobody helps, I am not sure if this can be solved in this timeframe as there might come other tasks with a higher priority.
When you talk about UNO Package, I suppose you mean an oxt file ?
I think UNO poackaging beudl eb fine. Better documentation and examples for the TypeDetection mechanism would also help. How much effort do you think would be involved?
You are right, they have been renamed to oxt, but they are still a ZIP file. Using OXT files for XML based (e.g. XSLT) filter would allow to deploy similar to all OXT / UNO components.
Yes, using the extension mecanism would be really nice.
SUS->ibshields: Sorry, have not made a time assumption so far, but in relation to it's benefit it can not be that high.