On 06/04/2015 01:41 PM, KATO Tomoyuki wrote:
Hi team,
I'm translating User Guides (RST) recently. I found a below problem. Any thought?
Problem: Each message catalog "pot" file contains all strings of the RST document, including "common" files (glossary and so on). In particular, "user-guide" and "user-guide-admin" resource at Transifex have same strings in "common" files respectively. This causes unintended inconsistency of translation. In fact, Japanese "user-guide" and "user-guide-admin" have different translated strings, which need to sync manually.
Indeed this is not optimal yet.
Solution (just my idea): As is: 1. Sphinx(?) generates the "pot" file. 2. translate at Transifex. 3. Sphinx(?) merge the translated strings.
To be: 1. Sphinx(?) generates the "pot" file. 2. A new script split message stringss for "common". (maybe, based on "msgcat") So, generate 2 resources (main document resource and "common" resource). 3. translate at Transifex. 4. merge the 2 resources for Sphinx(?). 5. Sphinx(?) merge the translated strings.
Yes, translating the "common-rst" separate from user-guide and user-guide-admin (and other future RST guides) would be the better way forward but needs some scripting.
You need to enhance in openstack-doc-tools the file bin/doc-tools-check-languages and in openstack-manuals the file tools/generatepot-rst.sh.
If you like to tackle this, it would be appreciated and I'll give any help - just don't have time right now to work on this myself,
Feel free to ask any questions,
Hi Andreas, Thanks for response, and sorry for nonparticipation of me in RST migration test of i18n tools. I will try this tool enhancement. I will send it when it is complete. Regards, KATO Tomoyuki