OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [docbook-apps] trademark tag not rendered correctly in javahelp


Hi Mauritz,
This is definitely a better solution for those creating a customization
layer to deal with the problem.

But I can't add this to the CVS tree because I can't make the attributes in
<xsl:output> conditional on the processor.  My fix was just so that the
stylesheets as distributed did not fail to produce something usable, if not
optimal.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net


----- Original Message ----- 
From: "Mauritz Jeanson" <mj@johanneberg.com>
To: "'Bob Stayton'" <bobs@sagehill.net>; <paul_t100@fastmail.fm>
Cc: <docbook-apps@lists.oasis-open.org>
Sent: Sunday, October 24, 2004 10:03 AM
Subject: RE: [docbook-apps] trademark tag not rendered correctly in javahelp


> > -----Original Message-----
> > From: Bob Stayton
> >
> ...
> > So I added a kludge to javahelp.xsl to the
> > "dingbat.characters" template,
> > which generates the trademark symbol for <trademark>.  If the
> > processor is
> > Xalan, it outputs <sup>TM</sup> for the trademark symbol.
> > But it won't have
> > any effect on any &trade; symbols you enter in your text.
> > For those, you
> > should customize the entity definition in the internal subset of your
> > documents, or in a special javahelp customization of the DTD:
> >
> > <!ENTITY trade "<superscript>TM</superscript">
>
> I have found another, maybe somewhat less kludgy, solution.
>
> To prevent Xalan from producing entity references, you can create a file
> that overrides the HTMLEntities.properties file that maps characters and
> HTML entities, and then point to it in the JavaHelp customization layer:
>
> <xsl:output encoding="UTF-8"
>             xalan:entities="somefile"/>
>
> The existence of this file, empty or not, disables HTML entities
altogether
> (which is good for JavaHelp). The idea is that you should be able to
define
> your own mappings, but for that to work you have to rebuild xalan.jar
after
> editing HTMLEntities.properties.
>
> See http://xml.apache.org/xalan-j/usagepatterns.html#outputprops.
>
> And this does work for HTML chunks. The xalanredirect:write element that
> Xalan uses to generate chunks does not have any encoding or entities
> attribute, but the attributes on xsl:output are recognized.
>
> /MJ
>
>
>




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]