Cheers,
Wendell

The internal representation does also contain the contents of content.xml, but also other information that will be stored separately in a Zip archive when you save an .odt file.

I suggest that you write a stylesheet with an identity template that allows exporting the internal representation in a single XML file. Because OpenOffice's debugging capabilities are very limited, you can develop your export filter against this XML export in your favorite XSL development environment.

Since version 3.2 or 3.3, OpenOffice uses Saxon 9.1 as XSLT processor, so it's possible to use XSLT 2.0.

-Gerrit

On 16.10.2010 01:08, Russell Urquhart wrote:

Hi,

Some of you have been of help to me in trying to hack a Open Office xsl filter. Thank you!

Another question i had. Does anyone know if the processing of the .xsl file, WHILE processed inside of Open Office (e.g. when doing a Save As using the filter) versus using an XSLT processor like Saxon or Xalan, applying the .xsl file to the content.xml file produces the same results? Is there anything special you need to do when applying the .xsl file from the command line?

I ask because it seems that, when i run a .xsl file within Open Office i get one thing and then when i run the same .xsl file in Saxonb or Xalan, on the content.xml file, i get something else.

Any help is appreciated!

======================================================================
Wendell Piez                            mailto:wapiez@xxxxxxxxxxxxxxxx
Mulberry Technologies, Inc.                http://www.mulberrytech.com
17 West Jefferson Street                    Direct Phone: 301/315-9635
Suite 207                                          Phone: 301/315-9631
Rockville, MD  20850                                 Fax: 301/315-8285
----------------------------------------------------------------------
  Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================