To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=100324





------- Additional comments from cche...@openoffice.org Fri Mar 20 15:43:45 
+0000 2009 -------
It appears to have been caused by using system saxon instead of internal saxon.
There needs to either be a big configure warning not to use system saxon until
the OOo patches are integrated upstream or to convert the xsl stylesheets to
XSLT 2.0 which looks like it would solve this problem as well.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@sc.openoffice.org
For additional commands, e-mail: issues-h...@sc.openoffice.org


---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org

Reply via email to