atom feed6 messages in org.oasis-open.lists.docbook-appsRE: [docbook-apps] xhtml output
FromSent OnAttachments
Marius ScurtescuOct 15, 2003 10:50 am 
Daniel VeillardOct 15, 2003 12:51 pm 
Bob StaytonOct 15, 2003 1:42 pm 
Marius ScurtescuOct 15, 2003 3:16 pm 
Bob StaytonOct 15, 2003 3:41 pm 
Marius ScurtescuOct 17, 2003 10:31 am 
Subject:RE: [docbook-apps] xhtml output
From:Marius Scurtescu (mscu@healthmetrx.com)
Date:Oct 17, 2003 10:31:59 am
List:org.oasis-open.lists.docbook-apps

Thanks Bob,

I was able to identify the exact version of Xalan I am getting based on the pointer you gave me (it is 2.5.1).

It turned out that Xalan has an extension which checks the environment and you can create a very simple style sheet to do this check: http://xml.apache.org/xalan-j/apidocs/org/apache/xalan/xslt/EnvironmentCheck .html

I attached this stylesheet (along with a dummy XML document) in case someone else wants to run this check in their editor.

Thanks, Marius

-----Original Message----- From: Bob Stayton [mailto:bo@sco.com] Sent: Wednesday, October 15, 2003 2:56 PM To: Marius Scurtescu Cc: Docbook-Apps Subject: Re: [docbook-apps] xhtml output

It is quite possible that you aren't getting the Xalan you think you are. Sun bundled a version of Xalan with Java 1.4. See this reference for making sure you are actually using a recent Xalan:

http://www.sagehill.net/docbookxsl/InstallingAProcessor.html#InstallXalan

Bob Stayton 400 Encinal Street Publications Architect Santa Cruz, CA 95060 Technical Publications voice: (831) 427-7796 The SCO Group fax: (831) 429-1887 email: bo@sco.com

On Wed, Oct 15, 2003 at 03:19:26PM -0700, Marius Scurtescu wrote:

Sorry for not mentioning the xslt processor, you are right, the problem is there.

I was using Xalan version 2.5.x under Win2K. I don't know the exact version since it came with the XML editor I am using (oXygen).

As soon as I switched to Saxon both problems went away (empty xmlns attributes and broken a tags).

I will try to find out the exact version of Xalan and use a newer one if available. I thought that Xalan is rock solid, but now it feels quite flaky :-(

Thanks, Marius

-----Original Message----- From: Bob Stayton [mailto:bo@sco.com] Sent: Wednesday, October 15, 2003 12:57 PM To: Marius Scurtescu Cc: Docbook-Apps Subject: Re: [docbook-apps] xhtml output

On Wed, Oct 15, 2003 at 10:52:48AM -0700, Marius Scurtescu wrote:

Hi,

I am converting DocBook documents to XHTML using the xhtml stylesheets from the XSL package version 1.62.0 and 1.62.4.

In both cases the generated XHTML is invalid.

The major problem is the generation of empty 'xmlns' attributes on many of the output tags (meta, div and p).

Is there a way to prevent this and generate valid XHTML?

As Daniel pointed out, this is coming from an older version of xsltproc, not the stylesheet.

Generally, the stylesheets output valid Transitional XHTML 1.0.

Are the XHTML stylesheets considered stable or just work in progress?

Stable, but always with room for improvement. 8^)

Another issue with the XHTML stylesheet is the conversion of the ulink DocBook tag. It gets converted into a broken a tag like: <a ="" target="_top">...</a>

Ulink usually works. Do you have a 'url' attribute in the ulink (it's required by the DTD)?

--

Bob Stayton 400 Encinal Street Publications Architect Santa Cruz, CA 95060 Technical Publications voice: (831) 427-7796 The SCO Group fax: (831) 429-1887 email: bo@sco.com

To unsubscribe from this list, send a post to

docb@lists.oasis-open.org, or visit http://www.oasis-open.org/mlmanage/.

--

Bob Stayton 400 Encinal Street Publications Architect Santa Cruz, CA 95060 Technical Publications voice: (831) 427-7796 The SCO Group fax: (831) 429-1887 email: bo@sco.com

<?xml version="1.0"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0" xmlns:xalan="http://xml.apache.org/xalan" exclude-result-prefixes="xalan">

<xsl:output indent="yes"/>

<xsl:template match="/"> <xsl:copy-of select="xalan:checkEnvironment()"/> </xsl:template>

</xsl:stylesheet>

<?xml version="1.0" encoding="UTF-8"?> <root> </root>