Hi Michael,
Hi Peter,
Thanks for your answers.
I tried to put the implementation name in the <data> node as specified by Peter,
but it doesn't work, my package is not loaded when I put
"com.sun.star.comp.JAXTHelper" at that place which must contains in fact the
name of my filter (if I understand well). When reading code of XSLTFilter.cxx, I
saw that the name of the specific implementation is retrieved in msUserData[1]
and that stylesheet is retrieved in msUserData[5], it's why I assume that each
msUserData corresponds to the sequence of value in the data node, values
separated by semi-colon because stylesheet is the sixth entry in this string (ok
to msUserData[5] found in code). And also beacuse the second entry is empty
and a comment in code tell that we use this not used user data for specific
implementation.
Michael, If I understand you, you tell that XSLT 2 support must be redone. But I
think that this support is still here, we only have to find where to set the
java implementation to override the default libxslt. Do you confirm Pete ?
Thanks Pete, to have a look on this.
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.