Please forgive this question, I am sure it lands in the RTFM category but I am having an issue which I would like some help with.
1) I checked out the document's repository from CVS and created a new document 2) I replicated the directory structure and made the needed changes to the Makefile (document name etc.)
3) I ran a make in my new doc's dir and it created the HTML.
Here is the issue.
When I browse to the document locally using Mozilla everything looks great, to be complete I tar'ed the dir up and sent it over to our webserver. When I browse to the document on the webserver it seems to add additional formatting which is causing my document to display a bunch of question marks all over the place, and little black boxes. Even viewing the source you can see the problem.
Source viewed when document loaded locally:
<title>Chapter 4. Adding Users <td width="40%" align="right"> <a accesskey="n" href="ch05.html">Next
Source viewed when document viewd over apache server:
<title>Chapter�4.�Adding align="right">�<a accesskey="n" href="ch05.html">
Can anyone point me in the right direction to fix this problem?
--Chris
On Thu, 2004-10-14 at 09:26, Chris Stankaitis wrote: [...snip...]
When I browse to the document locally using Mozilla everything looks great, to be complete I tar'ed the dir up and sent it over to our webserver. When I browse to the document on the webserver it seems to add additional formatting which is causing my document to display a bunch of question marks all over the place, and little black boxes. Even viewing the source you can see the problem.
Source viewed when document loaded locally:
<title>Chapter 4. Adding Users <td width="40%" align="right"> <a accesskey="n" href="ch05.html">Next
Source viewed when document viewd over apache server:
<title>Chapter�4.�Adding align="right">�<a accesskey="n" href="ch05.html">
What does the "Page Info" tell you about the document? For instance, when I browse a local file it is seen as ISO-8859-1 encoding, text/html MIME type. Is that what you see from the Apache-served file? If not, the httpd.conf file might be the place to start. The version of Apache you are running might be an issue.
I am out on a limb here since I don't run Web servers for a living. But, if in looking at the actual source of the file (I mean at a shell, using od or xxd, rather than post-Mozilla), you see that the file clearly contains spaces (0x20 ASCII), and not some other wackiness, the server is obviously to blame. (Well, it *seems* obvious to me, but someone more informed may have a different, and probably better, take on this.)
What does the "Page Info" tell you about the document? For instance, when I browse a local file it is seen as ISO-8859-1 encoding, text/html MIME type. Is that what you see from the Apache-served file? If not, the httpd.conf file might be the place to start. The version of Apache you are running might be an issue.
Yes, that was exactly the problem... the html was encoding in ISO, but on Apache it was trying to use UTF-8.
I had to make modifications to the main-html.xsl by adding:
<xsl:param name="chunker.output.encoding" select="'UTF-8'"/>
to tell /usr/share/sgml/docbook/xsl-stylesheets/html/manifest.xsl to not convert the html to ISO.
--Chris.
Chris Stankaitis wrote:
What does the "Page Info" tell you about the document? For instance, when I browse a local file it is seen as ISO-8859-1 encoding, text/html MIME type. Is that what you see from the Apache-served file? If not, the httpd.conf file might be the place to start. The version of Apache you are running might be an issue.
Yes, that was exactly the problem... the html was encoding in ISO, but on Apache it was trying to use UTF-8.
I had to make modifications to the main-html.xsl by adding:
<xsl:param name="chunker.output.encoding" select="'UTF-8'"/>
to tell /usr/share/sgml/docbook/xsl-stylesheets/html/manifest.xsl to not convert the html to ISO.
--Chris.
UTF-8 is a standard, why is the Fedora Doc's program not using UTF-8 as it's default encoding type?
On Thu, 2004-10-14 at 12:37, Chris Stankaitis wrote:
Chris Stankaitis wrote:
What does the "Page Info" tell you about the document? For instance, when I browse a local file it is seen as ISO-8859-1 encoding, text/html MIME type. Is that what you see from the Apache-served file? If not, the httpd.conf file might be the place to start. The version of Apache you are running might be an issue.
Yes, that was exactly the problem... the html was encoding in ISO, but on Apache it was trying to use UTF-8.
I had to make modifications to the main-html.xsl by adding:
<xsl:param name="chunker.output.encoding" select="'UTF-8'"/>
to tell /usr/share/sgml/docbook/xsl-stylesheets/html/manifest.xsl to not convert the html to ISO.
--Chris.
UTF-8 is a standard, why is the Fedora Doc's program not using UTF-8 as it's default encoding type?
I don't know of any reasons why not... even older Apache can serve out UTF-8 without a problem, AFAIK. Sounds like a candidate for a new bug in Bugzilla, eh?
On Thu, 2004-10-14 at 12:37 -0400, Chris Stankaitis wrote:
Chris Stankaitis wrote:
What does the "Page Info" tell you about the document? For instance, when I browse a local file it is seen as ISO-8859-1 encoding, text/html MIME type. Is that what you see from the Apache-served file? If not, the httpd.conf file might be the place to start. The version of Apache you are running might be an issue.
Yes, that was exactly the problem... the html was encoding in ISO, but on Apache it was trying to use UTF-8.
I had to make modifications to the main-html.xsl by adding:
<xsl:param name="chunker.output.encoding" select="'UTF-8'"/>
to tell /usr/share/sgml/docbook/xsl-stylesheets/html/manifest.xsl to not convert the html to ISO.
--Chris.
UTF-8 is a standard, why is the Fedora Doc's program not using UTF-8 as it's default encoding type?
The original xsl I wrote had UTF-8 specified. Then I removed it for some reason I can't remember now -- perhaps so it would work with the Fedora website? Let me change it to UTF-8 and post it on a test box for the website and see what happens.
Tammy
Tammy Fox wrote:
The original xsl I wrote had UTF-8 specified. Then I removed it for some reason I can't remember now -- perhaps so it would work with the Fedora website? Let me change it to UTF-8 and post it on a test box for the website and see what happens.
Tammy
Looking on a few Fedora Core 1 boxes we have here as well as some RHEL-3ES/WS boxes we use as web servers it looks like the httpd.conf has a default config option that sets UTF-8:
<snip> AddDefaultCharset UTF-8 </snip>
If your docs display the encoding issue on the test box check the httpd.conf for the above line.
--Chris
-
Chris Stankaitis -
Paul W. Frields -
Tammy Fox