Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


the XML filter settings dialog contains a test facility for user-defined 
XSLT import and export filters. For the export filters, you can view the 
highlighted source code of the exported XML and then validate the result 
against the given DOCTYPE or schema. 

Instead of offering that validation I'd rather make it possible to open 
the result in whatever editor is registered as defaul for XML in your 
desktop environment. 

First, we're not able to maintain a proper XML catalog anywhere in LibO, 
so for any non-trivial DOCTYPE or schema definition, the validation might 
just fail because the schema or some parts of the schema are not found by 

Second, I've been working on and off on replacing the Saxon/Java based 
transformation service with one based on libxslt, thus removing the Java 
dependency when working with XSLT in LibO. Implementing a validation 
service based on libxslt would require some additional non-trivial (seen 
from my humble C++ coding skills) work, which I'd like to avoid because I 
don't see much value in the built-in validation (see above). 

So I'd like to hear your opinions on that: is anyone using the validation 
button or at least theoretically sees some practical value to it, 
compared to offering to open the resulting XML in your favourite editor? 

Thanks and cheers, 


Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.