Red Hat Bugzilla – Bug 549925
<entry> tag causes unpredictable output when building translations with po files
Last modified: 2010-11-23 23:18:42 EST
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:220.127.116.11) Gecko/20091216 Fedora/3.5.6-1.fc11 Firefox/3.5.6
The <entry> tag seems to be causing some unpredictable behaviour when replacing translated strings from po files. Some symptoms are:
- text without <para> tags is not replaced
- text with inline tagging is omitted
- fuzzy translations are being included in the build
These issues are fixed by enclosing text in the table entries in the en-US xml files within <para> tags (i.e. <entry><para>text</para></entry>) and updating po files. However the Docbook spec seems to indicate that <entry>text</entry> is well-formed.
Will attach xml and po files that exhibit this problem.
Created attachment 379951 [details]
Table entry problems demonstrated in Japanese
Changing version to 11 per user agent.
This problem doesn't seem to be restricted to table entries. <para>s with nested variable lists and item lists also appear to have the same behaviour. Text in the root of the <para> is not being replaced by its respective translation and inline tagged text is also being omitted.
Text here is problematic.
Modified logic in translation merging code to insert translated text in mix-mode content correctly.
workaround: avoid using mixed mode content.
publican-1.4-1.fc12 has been submitted as an update for Fedora 12.
publican-1.4-1.fc11 has been submitted as an update for Fedora 11.
publican-1.4-1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
publican-1.4-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.