This is the mail archive of the docbook-apps@lists.oasis-open.org mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


Hi Bob

I provided the full files I'm running in an earlier mail. Are you actually testing this with javahelp.xsl or just the html xsl ?
If you are I think Ill just give up on this and use the superscript fix you wrote earlier
thanks Paul
Bob Stayton wrote:


Paul,
It would help if you could provide full details of how you are processing
your files.  I can't get Saxon on Windows to output ™ no matter what I
try.   So I'm mystified that you can't seem to prevent it.

If you are using a script and a customization layer, try running a straight
java command using the stock javahelp stylesheet from the distribution.  And
write the files to a different location so you can compare them for other
changes.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net


----- Original Message ----- From: "Paul Taylor" <paul_t100@fastmail.fm>
To: "Mauritz Jeanson" <mj@johanneberg.com>
Cc: <docbook-apps@lists.oasis-open.org>
Sent: Monday, October 18, 2004 2:12 PM
Subject: Re: [docbook-apps] trademark tag not rendered correctly in javahelp





I dont know if Im missing the point but Ive done as you suggested and
changed my script, the output files still contain &trade;
Im running on Windows vould this be a problem


Mauritz Jeanson wrote:




-----Original Message-----
From: Paul Taylor







Ok I tried to this by creating a file javahelpdriver which references
javahelp (this is the way Ive pased paramters before and it doesnt
require me to alter the docbook stuff directly) but it didnt work ,
however Im probably calling it wrong.




...




<xsl:output method="html"
encoding="UTF-8"
indent="no"
saxon:character-representation="native;decimal"/>




Since you are generating HTML chunks for JavaHelp, you must set the
parameters like this:

<xsl:param name="chunker.output.encoding">UTF-8</xsl:param>
<xsl:param


name="saxon.character.representation">native;decimal</xsl:param>


With these particular settings, you will get raw (native) UTF-8 with no
entity references or character references at all.






Just seen this, saxon is outputting &trade; which doesnt work. I
havent yet tried getting it to output the &#8482 but Ill




try tommorrow.




There must be something very strange going on if you are getting &trade;.
Saxon doesn't know about that entity reference, and cannot output it.

/MJ
















Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]