Hi Michael,
M. Niedermair wrote:
1. Does the engine you are using support 8859-1?
OOo use the jdk (or ?) and the jdk support 8859-1
I will take the chance and extend your question to:
"What XML parser and processor are being used in OOo?"
As it is a little complicated I will be verbose this time, so I can
reference to this mail in the future. ;-)
In OO.o we use Java for the XML filter framework and have bundled the
Apache Xalan-J 2.6 XSLT processor with the Apache Xerces parser since
OO.o 2.0 and OO.o 1.1.5.
In Java 1.4 Xalan was integrated by Sun to the JDK as well,
unfortunately with the same Java package structure.
By this, even if you use another Xalan in your classpath (as in OO.o)
the one from the JDK takes precedence and is being used.
This could have been prevented for the Office by using the Java command
line parameter
-Xbootclasspath/p:<CLASSPATH>
But the -X parameter are not specified and therefore not necessary
supported by any other Java implementation as 'BlackDown', therefore
this was no option to be used in OO.o.
For the sake of completeness, in JDK 1.4 the Apache crimson parser was
bundled.
In Java 5 both parser and processor has been changed.
The Apache Xerces parser is being used and the XSLTC processor, which is
part of the Xalan bundle. I have seen very promising results for the
XSLTC processor. (The 'C' stands for compiler, as it compiles the
stylesheets to Java classes in the first step).
But we do not use XSLTC as it has an small issue, which unfortunately
has a huge impact on our Office XSLT filter (node sets being created in
a template have a wrong namespace. This concept is used for instance
during the style generation of the XHTML export filter.)
Concerning your problem, I recently evaluated an issue for Xalan text
ouput in ISO-8859-1 (see. [1]), at least the Xalan 2.6 and 2.7 works
well when using XML output, but fails for text output even when used on
command line level. I hope the writer of that issue is going to write an
Xalan issue as well (at least I asked him for).
Finally, I am proud to anounce that we are on our way to update the
Xalan 2.6.0 to 2.7.0 in OO.o 2.0.3 (see [2]).
Aside of bug and performance fixes, Xalan 2.7.0 adds support for JAXP
1.3 and Namespace/XML 1.1 (for more details see [3]). I wrote an
enhancement today and Caloan was so kind to take over this task.
Regards,
Svante
[1] http://www.openoffice.org/issues/show_bug.cgi?id=56442
[2] http://www.openoffice.org/issues/show_bug.cgi?id=62422
[3] http://xml.apache.org/xalan-j/readme.html#done
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
