I just pushed 2 commits to LO master that fix the problem you encountered.
The configuration of the custom XML filter packages works a little
different compared to the built-in filters. The 2nd userdata parameter
currently is just ignored upon importing a package.
The first patch supports importing (but not exporting) the 2nd userdata
parameter, so you can use the saxon/j based xslt 2.0 aware
transformation in your filter (but still requires manually editing
TypeDetection.xcu).
http://cgit.freedesktop.org/libreoffice/core/commit/?id=960f4bdd71c9de19059279d61abb142ddfdac0ce
Thanks a lot. This patch is exactly what I need in first time.
The second patch adds a simple entry field that lets you edit the
transformation service that should be used with your filter. If you
leave it blank, the built-in service (currently libxslt) will be used,
but you're free to enter any service, like the
com.sun.star.comp.JAXTHelper thing that uses to saxon9/j internally.
http://cgit.freedesktop.org/libreoffice/core/commit/?id=11fbde8fed1a866c4ec9565d56f5f5034631d8b2
The ui is really the simplest thing that could possibly work, and it
doesn't do any input validation or whatever, but at least it's there.
Great. Much easier. Thanks.
If anyone could tell my how to include a simple help snippet for that
input fields I'd gratefully write a line or two.
If you're in a hurry those patches should apply cleanly to a checkout of
the 3.4.3 release branch, otherwise they hopefully make it into one of
the upcoming releases.
OK. I've not already get LibreOffice source and build it.But I thoughtfor a long
time.Maybea good opportunity.
Thanks again
Cheers,
Peter
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.