Description of problem: Internet Explorer users cannot use the html documentation that is generated by publican. The object tag that is required for all non-IE browsers to display SVG seems to cause IE to break the entire page. If you use <img>it still renders as a broken image because the format is not supported but doesn't break the whole page. <object data="Common_Content/images/redhat-logo.svg" type="image/svg+xml"/> This means that page breaks immediately after the subtitle and is not usable. A JBoss JIRA was raised, https://jira.jboss.org/jira/browse/SOA-1179 , to report this. Because SVG content does not display natively in Internet Explorer anyway perhaps we should convert the SVG to png and display via <img> Version-Release number of selected component (if applicable): publican 0.42 How reproducible: everytime Steps to Reproduce: 1.attempt to view publican generated html docs in Internet Explorer 7 eg. http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.GA/html-single/Programmers_Guide/index.html Actual results: screenshot from JIRA attached Expected results: Additional info:
Created attachment 332666 [details] screenshot as per jira SOA-1179
Possible fix is to modify the XSL that generates the object tags to output: <object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> <img src="Common_Content/images/title_logo.png" alt="Alternate image for broken browsers"> </object> This should allow non-compliant browsers to fall back to a png image. Hope to get to test this next week.
I modified the SQL so that browsers that can not display the SVG will display the text object used for the ALT text. Tested OK in IE 7. This solution will mean most existing books do not need to be modified to display in IE7.
publican-fedora-0.18-0.fc10,publican-0.44-0.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/publican-fedora-0.18-0.fc10,publican-0.44-0.fc10
publican-fedora-0.18-0.fc10, publican-0.44-0.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 512471 has been marked as a duplicate of this bug. ***