Hi, 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 LibO. 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, Peter -- Unsubscribe instructions: E-mail to [email protected] Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/discuss/ All messages sent to this list will be publicly archived and cannot be deleted
