Description of problem: When Publican generates a POT file from an XML file, all apostrophes (single quote marks) in the text are presented as ' This breaks translations made when Publican presented single quote marks/apostrophes in PO files. Using numerical entities for apostrophes makes translation more difficult, since the nature of the entity is not always obvious. Version-Release number of selected component (if applicable): 2.1 How reproducible: 100% Steps to Reproduce: 1. Place a string with an apostrophe in an XML file 2. run publican update_pot Actual results: The string appears in the POT file with ' in place of the apostrophe Expected results: The apostrophe is presented as a normal single quote mark.
Confirmed fixed in build 2.1-0.fc13.t36 Reverting to this earlier behaviour will affect any books where the POT files have been refreshed in the last few months. However, it will prevent fuzzies being generated for strings with apostrophes in them when you reuse translations made previous to the last few months. Also, it ensures that single and double quotation marks are presented in the PO files as ' and " instead of ' and " Manuel, is the earlier behaviour (' and ") what you would expect?
I think having the ' and " is clearer for translators.
A similar issue us happening with < and > -- these get changed into < and > in POT Discovered on 2.1-0.fc13.t106
Fixed < and >. Fixed in build: 2.1-0%{?dist}.t110
publican-2.2-0.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/publican-2.2-0.fc13
publican-2.2-0.fc12 has been submitted as an update for Fedora 12. https://admin.fedoraproject.org/updates/publican-2.2-0.fc12
publican-2.2-0.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/publican-2.2-0.fc14
publican-2.2-0.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
A number of my older books showed this problem with a large number of entities. Posting the list here in case of later regression: ' ’ " (remember to replace this with \" in po files, to escape the " character) < > “ ” (remember to replace this with \" in po files, to escape the " character) –     — % $