Hi Oliver,
Oliver Brinzing wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Svante,
I have a recent build m178 and it works fine..
tried it with m180 and SO 7.0 PU 7 ...
is it possible that it will work only for *exports* ?
I got them for my import, tested yesterday on m178.
i can find the mentioned parameters only in the export sample filters
(share\xslt\ ...)
is it possible to provide a small example for import ?
You might edit the sources of the OOo2XHTML export
<YOUR_OFFICE_PATH>\share\xslt\export\xhtml\ooo2xhtml.xsl
Just remove the xsl:includes and the line
<xsl:call-template name="collect-global-OOo-properties" />
You will see there is a parameter test and even some comments on the
variables.
BTW I recently added an enhancement to the the XSLT debug log, where all
is it possible to get a log file / use a logger ?
Let's stick on the latest greatest version (m180 or even better m182,
later more about this)...
The logfile is being activated by setting a Java System Property in the
office (Tools->Option->Java), e.g.
-DXSLTransformer.statsfile=E:\offices\xslt_debug_m160.txt
or
-DXSLTransformer.statsfile=/usr/local/offices/xslt_debug_m160.txt
And finally the Java source setting the properties to the XSLT processor
is in the filter module,
filter\source\xsltfilter\XSLTransformer.java
With the m182, the CWS Xalanupgrade has been integrated.
Caolán did an update on the Xalan to 2.7.0 and I did some improvements
on the log file (as I mentioned earlier).
i am using log4j for my oo components ...
An enhanced logging and configuration would be most welcome for the XML
based filter framework, compare my recent mail to the Redoffice team on
this mailinglist.
Hope that helps you,
Svante
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
