Bug 126921
Summary: | xmlto (docbook) doesn't generate UTF8 compatible output | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Jack Neely <jjneely> |
Component: | xmlto | Assignee: | Tim Waugh <twaugh> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 0.0.18-4 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-07-01 11:26:08 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jack Neely
2004-06-29 02:45:36 UTC
Please try changing line 124 of /usr/bin/xmlto from: if false; to: if [ -x /usr/bin/locale ] Does that help? It does. The output looks proper with UTF8. However, now there are similar issues with the Latin1 encoding. Ã Ã Ã Ã Ã Ã Ã Ã </p></div></div></div> Can you explain in more detail the issue you now see with Latin1? The output you get from running xmlto (with the above change) in a UTF-8 locale should be UTF-8, and marked as such with an encoding tag. Is that not the case? The patched xmlto output is marked as content="text/html; charset=UTF-8" It seems that if the above charset doesn't match the 'AddDefaultCharset' Apache configuration option I get weird characters displayed in my browser. Apparently the HTTP header charset specification overrules the actual HTML content (!). So don't use 'AddDefaultCharset'. :-) I'll make that change in Fedora development (package built as xmlto-0.0.18-4) and check that it doesn't cause other problems -- before it caused bug #80732 -- and then hopefully it will appear in a future version of Red Hat Enterprise Linux. |