You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by bu...@apache.org on 2001/03/23 14:51:36 UTC
[Bug 1091] New - Unusable HTML-transforming after upgrading to Xalan 2.x (Java)
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1091
*** shadow/1091 Fri Mar 23 05:51:35 2001
--- shadow/1091.tmp.1024 Fri Mar 23 05:51:35 2001
***************
*** 0 ****
--- 1,52 ----
+ +============================================================================+
+ | Unusable HTML-transforming after upgrading to Xalan 2.x (Java) |
+ +----------------------------------------------------------------------------+
+ | Bug #: 1091 Product: XalanJ2 |
+ | Status: NEW Version: 2.0.1 |
+ | Resolution: Platform: PC |
+ | Severity: Major OS/Version: |
+ | Priority: High Component: org.apache.xalan.transf |
+ +----------------------------------------------------------------------------+
+ | Assigned To: xalan-dev@xml.apache.org |
+ | Reported By: kingrob00@hotmail.com |
+ | CC list: Cc: |
+ +----------------------------------------------------------------------------+
+ | URL: |
+ +============================================================================+
+ | DESCRIPTION |
+ We've been runnig Xalan since 1999, mainly using the XML to HTML transforming
+ functions. We have plenty of XSL files in production.
+
+ Now we've upgraded from Xalan 1.x to 2, even tried 2.0.1 - all Java versions.
+ The problem is that some tags that used to be transformed for example <BR/> to
+ <BR>, which works much better with Netscape, doesn't any more!! In the new 2.x
+ versions <BR/> isn't transformed which have the effect that Netscape(4.x)
+ ignores it and the whole page looks like disaster. This is also a problem with
+ other tags like <P/> and <TD/>.
+
+ My eyes are bleeding from trying to find some useful information about this and
+ I've thoroughfully search all your webpages but can't find a solution.
+
+ This problem comes both for the command-line utility with the option -HTML and
+ the api-version where
+
+ transformer.getOutputProperty( OutputKeys.METHOD )
+
+ gives me "html".
+
+ The xsl-files are all defined as follows.
+
+ <xsl:output indent="yes" method="html" encoding="ISO-8859-1"
+ media-type="text/html"/>
+
+ It's easy to reproduce using
+
+ java -classpath xxx org.apache.xalan.xslt.Process -HTML -V -IN foo.xml -XSL
+ foo.xsl -OUT foo.htm
+
+ ...with appropriate foo-files and using both Xalan1.x and Xalan2.x. It will show
+ different behaviour considering tabs like <BR/>.
+
+ This is a major problem and means that we can't upgrade to the new version. I
+ can't even work around the problem using say <BR></BR> because it transformes to
+ <BR/> and ignores by Netscape. What can I do???