Bug 577068
| Summary: | Bug When Rendering PDF Files - Publican Creates Erroneous Program Listings | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Community] Publican | Reporter: | David Le Sage <dlesage> | ||||||||||||||
| Component: | publican | Assignee: | Jeff Fearn 🐞 <jfearn> | ||||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||||
| Priority: | low | ||||||||||||||||
| Version: | 1.6 | CC: | abeekhof, djorm, dlackey, icon, jfearn, lbrindle, mmcallis, pmorgan, publican-list, rlandman | ||||||||||||||
| Target Milestone: | --- | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | All | ||||||||||||||||
| OS: | Linux | ||||||||||||||||
| Whiteboard: | |||||||||||||||||
| Fixed In Version: | publican-1.6.3-0.fc12 | Doc Type: | Bug Fix | ||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2010-05-17 18:56:18 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: | |||||||||||||||||
| Bug Depends On: | |||||||||||||||||
| Bug Blocks: | 591745 | ||||||||||||||||
| Attachments: |
|
||||||||||||||||
|
Description
David Le Sage
2010-03-26 00:49:35 UTC
Hi, I have tested this on F12 and can not duplicate this behaviour. Can you build the PDF and then check the following files to see if, and where, the offending hyphen has been added? tmp/en-US/xml_tmp/<FILE>.xml tmp/en-US/xml/<FILE>.xml If the hyphen isn't there, then it may be in the XML:FO file, which would be: tmp/en-US/xml/<BOOKNAME>.fo The fo file is quite large and poorly formatted, so you will need to search for a string, e.g. retries in the example provided, to find the right place. If the hyphen isn't there then it is probably being added by FOP. Cheers, Jeff. (collision) I cannot reproduce this in F12: html and pdf versions are identical: <property name="retries"><int value="3" /<</property< (literal output of the DocBook in step 1 above) <property name="retries"><int value="3"/></property> (corrected DocBook) Hello Jeff, Thanks for the quick feedback. I checked all of those files and it did not appear in any of them, so probably a FOP issue. The Fed 13 builds are currently utilising FOP 0.95 release 4. $ uname -a Linux captcha 2.6.32.9-70.fc12.x86_64 #1 SMP Wed Mar 3 04:40:41 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux $ rpm -q fop fop-0.95-4.noarch Spook diddley ooky! LOL - I thought it was just me being naughty and being a veeerrrry early adopter of Fed 13.... (In reply to comment #5) > LOL - I thought it was just me being naughty and being a veeerrrry early > adopter of Fed 13.... It probably is, maybe something in the java stack related to the XSLT or layout engines. Which Java are you using? LOL - was trying to dodge the guilt. On a serious note, I am running OpenJDK and the version is 1.6.0_17. Hey Jeff, Rudi has found a way around it. Changing: <xsl:-Param name="hyphenate.verbatim" select="1"/> to <xsl:-Param name="hyphenate.verbatim" select="0"/> eliminates the problem. He thinks it is due to changes in hyphenation that you guys have been trying to implement. Cheers. *** Bug 578706 has been marked as a duplicate of this bug. *** *** Bug 579786 has been marked as a duplicate of this bug. *** set hyphenate.verbatim to 0 *** Bug 581961 has been marked as a duplicate of this bug. *** I'm still seeing this. See attached screenshots labeled "vdso..." It also appears to be doubling single hyphens. See attached screenshots labeled "sysctl..." LKB Created attachment 406934 [details]
VDSO PDF
Created attachment 406935 [details]
VDSO HTML
Created attachment 406936 [details]
VDSO Source
Created attachment 406937 [details]
sysctl PDF
Created attachment 406938 [details]
sysctl HTML
Created attachment 406939 [details]
sysctl Source
# rpm -qa publican publican-1.6-0.fc12.noarch LKB (In reply to comment #13) > I'm still seeing this. See attached screenshots labeled "vdso..." This bug isn't 'CLOSED ERRATA' so no errata has been shipped. We are getting the translators to test some changes to the translation code before we ship 1.6.3. *** Bug 588748 has been marked as a duplicate of this bug. *** Confirmed fixed in 1.6.3.t122 Can we get an update for F-12 too please? publican-1.6.3-0.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/publican-1.6.3-0.fc13 publican-1.6.3-0.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/publican-1.6.3-0.fc12 publican-1.6.3-0.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update publican'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/publican-1.6.3-0.fc12 publican-1.6.3-0.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update publican'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/publican-1.6.3-0.fc13 publican-1.6.3-0.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. publican-1.6.3-0.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. |