You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Jean T. Anderson" <jt...@bristowhill.com> on 2006/03/22 00:36:41 UTC
[doc] Java(TM) not getting rendered properly for html
The (TM) portion of Java(TM) is mangled on these html pages:
http://db.apache.org/derby/docs/dev/getstart/cgsintro.html
http://db.apache.org/derby/docs/dev/adminguide/cadminappsthenetworkserverandjvms.html
http://db.apache.org/derby/docs/dev/adminguide/tadminapps811695.html
http://db.apache.org/derby/docs/dev/devguide/cdevdvlp14839.html
I checked the Getting Started guide and the output is correct for the
HTML book and for the PDF, just not for the individual html pages
Here's the DITA tag in the source that isn't getting rendered properly:
<tm tmclass="special" tmowner="Sun Microsystems, Inc."
tmtype="tm" trademark="Java">Java</tm>
Does this ring a bell to anyone? or should I log a new Jira issue?
thanks,
-jean
Re: [doc] Java(TM) not getting rendered properly for html
Posted by Andrew McIntyre <mc...@gmail.com>.
On 3/27/06, Jeff Levitt <de...@mylevita.com> wrote:
>
> Here is the bug I reported to the DITA toolkit, along
> with some responses:
>
> https://sourceforge.net/tracker/?func=detail&atid=725074&aid=1456430&group_id=132728
>
> It sounds like the problem is on our end. Does anyone
> have an idea what the problem might be if itsnot with
> the Toolkit?
Figured it out. The web server on minotaur must default specifying a
charset of ISO-8859-1 in the HTTP headers. I added an .htaccess file
to derby/docs/ to set the charset for html files to UTF-8 and now the
files all appear correctly.
Sorry for the misdirection, I got confused about what was working
where and how it was fixed. The DITA bug can be closed.
andrew
Re: [doc] Java(TM) not getting rendered properly for html
Posted by Jeff Levitt <de...@mylevita.com>.
--- Andrew McIntyre <mc...@gmail.com> wrote:
> On 3/21/06, Jean T. Anderson <jt...@bristowhill.com>
> wrote:
> >
> > What browser are you using that it works on?
>
> I had been using Safari, but now I'm wondering if I
> had changed the
> default encoding, because using a different version
> of Safari on a
> different machine, I also see the problem. It is
> fixed by switching
> the default encoding of Safari to UTF-8 on that
> machine.
>
> Grepping through the DITA toolkit, there is a
> pathological use of
> lowercase 'utf-8'. We should report the problem to
> the DITA folks.
>
> andrew
>
Here is the bug I reported to the DITA toolkit, along
with some responses:
https://sourceforge.net/tracker/?func=detail&atid=725074&aid=1456430&group_id=132728
It sounds like the problem is on our end. Does anyone
have an idea what the problem might be if itsnot with
the Toolkit?
Re: [doc] Java(TM) not getting rendered properly for html
Posted by Andrew McIntyre <mc...@gmail.com>.
On 3/21/06, Jean T. Anderson <jt...@bristowhill.com> wrote:
>
> What browser are you using that it works on?
I had been using Safari, but now I'm wondering if I had changed the
default encoding, because using a different version of Safari on a
different machine, I also see the problem. It is fixed by switching
the default encoding of Safari to UTF-8 on that machine.
Grepping through the DITA toolkit, there is a pathological use of
lowercase 'utf-8'. We should report the problem to the DITA folks.
andrew
Re: [doc] Java(TM) not getting rendered properly for html
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
Andrew McIntyre wrote:
> On 3/21/06, Jean T. Anderson <jt...@bristowhill.com> wrote:
>
>>The (TM) portion of Java(TM) is mangled on these html pages:
>>
>></snip list of pages>
>>
>>I checked the Getting Started guide and the output is correct for the
>>HTML book and for the PDF, just not for the individual html pages
>>
>>Here's the DITA tag in the source that isn't getting rendered properly:
>>
>><tm tmclass="special" tmowner="Sun Microsystems, Inc."
>>tmtype="tm" trademark="Java">Java</tm>
>>
>>Does this ring a bell to anyone? or should I log a new Jira issue?
>
> The output HTML is correct. It looks like your browser isn't honoring
> the charset attribute in the header. The header specifies the charset
> to be UTF-8, and the trademark symbol is properly encoded as such.
I get the same mangled output on these browsers:
Linux: Firefox 1.0.7
Linux: Konqueror 3.3
Windows XP: Internet Explorer 6.0.2900
Windows XP: Mozilla 1.7.8
What browser are you using that it works on?
-jean
> It would be nicer if the DITA toolkit used the © character
> reference instead, but what they're doing is technically also correct.
> See if you can switch the default encoding in your browser to UTF-8.
> Even so, sounds like a bug in your browser.
>
> andrew
Re: [doc] Java(TM) not getting rendered properly for html
Posted by Jeff Levitt <de...@mylevita.com>.
--- "Dag H. Wanvik" <Da...@Sun.COM> wrote:
> Andrew McIntyre <mc...@gmail.com> writes:
>
> > On 3/21/06, Andrew McIntyre <mc...@gmail.com>
> wrote:
> > I'm guessing this is a problem with Firefox as
> well, but I don't have
> > that handy right now to check. The problem could
> be fixed in Mozilla
>
> I can conform it is a problem with firefox as well
> (1.5.0.1).
>
> Dag
>
> > as well, if they just ignored case when examining
> the charset
> > attribute. I found a couple of bugs in Bugzilla
> that looked like they
> > might be this one, but nothing that was an exact
> match.
> >
> > andrew
> >
>
I have submitted the following bug to the DITA toolkit
project:
http://sourceforge.net/tracker/index.php?func=detail&aid=1456430&group_id=132728&atid=725074
Re: [doc] Java(TM) not getting rendered properly for html
Posted by "Dag H. Wanvik" <Da...@Sun.COM>.
Andrew McIntyre <mc...@gmail.com> writes:
> On 3/21/06, Andrew McIntyre <mc...@gmail.com> wrote:
> I'm guessing this is a problem with Firefox as well, but I don't have
> that handy right now to check. The problem could be fixed in Mozilla
I can conform it is a problem with firefox as well (1.5.0.1).
Dag
> as well, if they just ignored case when examining the charset
> attribute. I found a couple of bugs in Bugzilla that looked like they
> might be this one, but nothing that was an exact match.
>
> andrew
>
Re: [doc] Java(TM) not getting rendered properly for html
Posted by Andrew McIntyre <mc...@gmail.com>.
On 3/21/06, Andrew McIntyre <mc...@gmail.com> wrote:
>
> The output HTML is correct. It looks like your browser isn't honoring
> the charset attribute in the header. The header specifies the charset
> to be UTF-8, and the trademark symbol is properly encoded as such.
I checked Mozilla to see if it had this problem, and it does, and
playing around with it, I found that Mozilla properly sets the
encoding only if UTF-8 is uppercased in the document, which is not the
case here. So this is an issue that could be fixed by the DITA folks,
and maybe should be, since technically the ISO code is uppercase
letters. We could implement a workaround by editing the stylesheet
that writes the header to fix the casing.
I'm guessing this is a problem with Firefox as well, but I don't have
that handy right now to check. The problem could be fixed in Mozilla
as well, if they just ignored case when examining the charset
attribute. I found a couple of bugs in Bugzilla that looked like they
might be this one, but nothing that was an exact match.
andrew
Re: [doc] Java(TM) not getting rendered properly for html
Posted by Andrew McIntyre <mc...@gmail.com>.
On 3/21/06, Jean T. Anderson <jt...@bristowhill.com> wrote:
> The (TM) portion of Java(TM) is mangled on these html pages:
>
> </snip list of pages>
>
> I checked the Getting Started guide and the output is correct for the
> HTML book and for the PDF, just not for the individual html pages
>
> Here's the DITA tag in the source that isn't getting rendered properly:
>
> <tm tmclass="special" tmowner="Sun Microsystems, Inc."
> tmtype="tm" trademark="Java">Java</tm>
>
> Does this ring a bell to anyone? or should I log a new Jira issue?
The output HTML is correct. It looks like your browser isn't honoring
the charset attribute in the header. The header specifies the charset
to be UTF-8, and the trademark symbol is properly encoded as such.
It would be nicer if the DITA toolkit used the © character
reference instead, but what they're doing is technically also correct.
See if you can switch the default encoding in your browser to UTF-8.
Even so, sounds like a bug in your browser.
andrew