Opera might be smart enough to look at the tag. Firefox
apparently does not
On Fri 09 Sep 2011 11:38:08 AM CDT, Steve Ebersole wrote:
> Looking at the sources, the heard information is the same. NOw it is
> possible that they set the response encoding, which local browsing
> would not have a
I check my docs locally with Opera, which shows the document with the
correct encoding, exactly as they render in Firefox after they are
deployed to jboss.org
Sanne
On 9 September 2011 18:38, Steve Ebersole wrote:
> Looking at the sources, the heard information is the same. NOw it is
> possible
Looking at the sources, the heard information is the same. NOw it is
possible that they set the response encoding, which local browsing would
not have a chance to do.
On 09/09/2011 11:22 AM, Hardy Ferentschik wrote:
> This is the issue I have been talking about -
> https://issues.jboss.org/bro
This is the issue I have been talking about -
https://issues.jboss.org/browse/JDOCBOOKSTYLE-32
FYI, this does not happen when I view the documentation deployed online. I
assume that Apache
sets some header information.
--Hardy
On Fri, 09 Sep 2011 18:14:26 +0200, Steve Ebersole
wrote:
> T
Hi,
this has been recently discussed on Core I think and I think an issue got
created as well.
It has to with the character set used for displaying. In Firefox just
select View->Character Encoding
and select UFT-8 explicitly.
I will dig out the issue.
--Hardy
On Fri, 09 Sep 2011 18:14:26
