[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [docbook-apps] Public/System doctype IDs misbehaving in Eclipse output (1.73)
And once again I am left wishing that I had simply asked for help sooner. Removed the default values from docbook.xsl and things started behaving. Thanks Bob. Jeff. -----Original Message----- From: Bob Stayton [mailto:bobs@sagehill.net] Sent: Friday, March 19, 2010 1:48 PM To: Jeff Hooker; DocBook Apps Subject: Re: [docbook-apps] Public/System doctype IDs misbehaving in Eclipse output (1.73) Regarding passing blank values for doctype parameters, I presume you are using Saxon. It is a feature of Saxon that you cannot reset the doctype to blank after it has been set earlier in the stylesheet in an xsl:output element. In the case of xhtml, the stock xhtml/docbook.xsl file sets the doctype values for the standard XHTML doctypes. Any xsl:output in a customization layer after that can reset the value to a different string, but Saxon cannot set it to blank to eliminate it. You actually have to edit or replace the original xhtml/docbook.xsl file to turn off the original doctype values. Very awkward. Bob Stayton Sagehill Enterprises bobs@sagehill.net ----- Original Message ----- From: "Jeff Hooker" <Jeff_Hooker@pmc-sierra.com> To: "DocBook Apps" <docbook-apps@lists.oasis-open.org> Sent: Friday, March 19, 2010 1:11 PM Subject: RE: [docbook-apps] Public/System doctype IDs misbehaving in Eclipse output (1.73) Spoke a little too soon on this one; the change took care of the problem in html output, it remains stubbornly persistent in xhtml. Interestingly, if I pass a value to doctype-public and doctype-system when generating the plugin, the values are reproduced, but if I try passing the parameters as blank values, the global values are used. I'm going to keep picking at this, but any further suggestions would be welcome. Thanks, Jeff. -----Original Message----- From: Jeff Hooker [mailto:Jeff_Hooker@pmc-sierra.com] Sent: Thursday, March 18, 2010 12:12 PM To: Keith Fahlgren; David Cramer Cc: DocBook Apps Subject: RE: [docbook-apps] Public/System doctype IDs misbehaving in Eclipse output (1.73) That addressed the problem quite nicely, thank you very much. I would have been groping for that for quite a while. -----Original Message----- From: Keith Fahlgren [mailto:abdelazer@gmail.com] Sent: Thursday, March 18, 2010 7:15 AM To: David Cramer Cc: Jeff Hooker; DocBook Apps Subject: Re: [docbook-apps] Public/System doctype IDs misbehaving in Eclipse output (1.73) On Wed, Mar 17, 2010 at 6:27 PM, David Cramer <dcramer@motive.com> wrote: > I was never able to get around that (but I don't think it occurred to me > to ask here). I ended up post-processing the plugin.xml and toc.xml > files to remove the doctype. > > I'll be interested in hearing if there's a right way. I have a vague > idea/memory that this is a saxon thing. I ran into the same problem with the ePub stylesheets. Under the hood, this uses the template named "write.chunk". From a quick look at the SVN trunk, I think you'd want to add two paramaters to the call to write.chunk that generates these files and overrides the doctype you're setting elsewhere: Index: eclipse.xsl =================================================================== --- eclipse.xsl (revision 8582) +++ eclipse.xsl (working copy) @@ -114,6 +114,8 @@ <xsl:with-param name="encoding" select="'utf-8'"/> <xsl:with-param name="indent" select="'yes'"/> <xsl:with-param name="quiet" select="$chunk.quietly"/> + <xsl:with-param name="doctype-public" select="''"/> <!-- intentionally blank --> + <xsl:with-param name="doctype-system" select="''"/> <!-- intentionally blank --> <xsl:with-param name="content"> <xsl:choose> @@ -207,6 +209,8 @@ <xsl:with-param name="encoding" select="'utf-8'"/> <xsl:with-param name="indent" select="'yes'"/> <xsl:with-param name="quiet" select="$chunk.quietly"/> + <xsl:with-param name="doctype-public" select="''"/> <!-- intentionally blank --> + <xsl:with-param name="doctype-system" select="''"/> <!-- intentionally blank --> <xsl:with-param name="content"> <plugin name="{$eclipse.plugin.name}" id="{$eclipse.plugin.id}" ...that said, I've never used the Eclipse output, so this is just a guess based on what is in SVN... Keith --------------------------------------------------------------------- To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org --------------------------------------------------------------------- To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]