Hi all, I've been working on switching the docs translation infrastructure over to itstool. This affects openstack-manuals, operations-guide, and api-site. The current tools are based on xml2po, but they don't call xml2po directly. Instead, they import xml2po and mess around with its internals to get some custom behavior. itstool is designed to handle custom behavior with rules from the W3C Internationalization Tag Set (ITS). You can see the ITS I put together so far here: https://review.openstack.org/#/c/91869/3/os_doc_tools/resources/openstack.it... Using ITS also allows us to do local ITS attributes to override the behavior for specific elements. See a simple example here: https://review.openstack.org/#/c/91872/1/api-quick-start/src/docbkx/api-quic... Most messages in the PO files will be the same. The one big difference will be in how placeholders are done when there's a block-level element inside a block-level element (a practice I discourage anyway). Blueprint and some patches: https://blueprints.launchpad.net/openstack-manuals/+spec/itstool-for-docs https://review.openstack.org/#/q/topic:bp/itstool-for-docs,n,z I'd like to get input from translators, as well as any other docs folks who've worked on this. Most of the document translations are incomplete anyway, but it would nevertheless be best to do this at the beginning of a release cycle. -- Shaun
On 05/03/2014 02:53 PM, Shaun McCance wrote:
Hi all,
I've been working on switching the docs translation infrastructure over to itstool. This affects openstack-manuals, operations-guide, and api-site. The current tools are based on xml2po, but they don't call xml2po directly. Instead, they import xml2po and mess around with its internals to get some custom behavior.
itstool is designed to handle custom behavior with rules from the W3C Internationalization Tag Set (ITS). You can see the ITS I put together so far here:
https://review.openstack.org/#/c/91869/3/os_doc_tools/resources/openstack.it...
Using ITS also allows us to do local ITS attributes to override the behavior for specific elements. See a simple example here:
https://review.openstack.org/#/c/91872/1/api-quick-start/src/docbkx/api-quic...
Most messages in the PO files will be the same. The one big difference will be in how placeholders are done when there's a block-level element inside a block-level element (a practice I discourage anyway).
Could you give an example, please?
Blueprint and some patches:
https://blueprints.launchpad.net/openstack-manuals/+spec/itstool-for-docs https://review.openstack.org/#/q/topic:bp/itstool-for-docs,n,z
Looking at the patches, I really like what I see and would love to see us move forward. This needs also some documentation in the OpenStack wiki on the recommend usage of local ITS attributes like its:translate and its:withinText.
I'd like to get input from translators, as well as any other docs folks who've worked on this. Most of the document translations are incomplete anyway, but it would nevertheless be best to do this at the beginning of a release cycle.
I assume that we can convert the existing translated files in such a way that we do not loose translations? How to do this properly? Download current files from transifex, convert into new format, upload converted files - and then continue translating? Or will it be enough to upload the pot file and let transfix do the translation? Did you test a conversation of locale files and reconstructed translated manuals? Is this just working with the updated tools or are additional steps needed? I think we need to ensure with the infra team that itstools are installed on our machines. I see that some patches are dependent on each other and we need to do certain steps in a specific order. Is this something you can write down as plan, please? Thanks! Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Sun, 2014-05-04 at 13:33 +0200, Andreas Jaeger wrote:
On 05/03/2014 02:53 PM, Shaun McCance wrote:
Hi all,
I've been working on switching the docs translation infrastructure over to itstool. This affects openstack-manuals, operations-guide, and api-site. The current tools are based on xml2po, but they don't call xml2po directly. Instead, they import xml2po and mess around with its internals to get some custom behavior.
itstool is designed to handle custom behavior with rules from the W3C Internationalization Tag Set (ITS). You can see the ITS I put together so far here:
https://review.openstack.org/#/c/91869/3/os_doc_tools/resources/openstack.it...
Using ITS also allows us to do local ITS attributes to override the behavior for specific elements. See a simple example here:
https://review.openstack.org/#/c/91872/1/api-quick-start/src/docbkx/api-quic...
Most messages in the PO files will be the same. The one big difference will be in how placeholders are done when there's a block-level element inside a block-level element (a practice I discourage anyway).
Could you give an example, please?
In the user-guide, in section_dashboard_manage_images.xml, there's an itemizedlist inside a para. An itemizedlist is a block-level element, so it starts one or more new PO messages. The message for the para gets a placeholder element so translators know it's there, and can move it around if necessary. With xml2po, it looks like this: #: doc/user-guide/section_dashboard_manage_images.xml:179(para) msgid "" "In the Update Image dialog box, you can perform the following " "actions: <placeholder-1/>" msgstr "" With itstool, it looks like this: #. (itstool) path: step/para #: doc/user-guide/section_dashboard_manage_images.xml:179 msgid "" "In the Update Image dialog box, you can perform the following " "actions: <_:itemizedlist-1/>" msgstr "" itstool puts all its special elements in a namespace using the _ prefix. (It gets mapped to an internal namespace URI during processing.) This helps prevent conflicts, and it allows the local name of the placeholder element to reflect what kind of thing gets put there, which is helpful.
I'd like to get input from translators, as well as any other docs folks who've worked on this. Most of the document translations are incomplete anyway, but it would nevertheless be best to do this at the beginning of a release cycle.
I assume that we can convert the existing translated files in such a way that we do not loose translations? How to do this properly? Download current files from transifex, convert into new format, upload converted files - and then continue translating? Or will it be enough to upload the pot file and let transfix do the translation?
Any translations where the source string is the same will just continue to work. That's the way PO works. I looked into migrating obvious things like the placeholder difference. There are very few translations though. I could maybe fix up 20-30 across all translations of all books. There isn't anything else to migrate.
Did you test a conversation of locale files and reconstructed translated manuals? Is this just working with the updated tools or are additional steps needed?
Yes. My patch includes also using itstool for generating the DocBook from the PO files. I tested it. It works.
I think we need to ensure with the infra team that itstools are installed on our machines.
That's the big question I haven't been able to answer yet. Preferably at least version 2.0.1.
I see that some patches are dependent on each other and we need to do certain steps in a specific order. Is this something you can write down as plan, please?
I did write this: https://wiki.openstack.org/wiki/Documentation/Translation#ItsTool_Conversion It has steps that need to be done (roughly) in order. -- Shaun
On 05/09/2014 05:47 PM, Shaun McCance wrote:
[...]
I think we need to ensure with the infra team that itstools are installed on our machines.
That's the big question I haven't been able to answer yet. Preferably at least version 2.0.1.
Just talked briefly with the infra team and checked our setup: What is in Ubuntu Precise? I assume the package is not installed but if it's available, we can add rules to the gate machines to have it installed... Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 05/09/2014 05:57 PM, Andreas Jaeger wrote:
On 05/09/2014 05:47 PM, Shaun McCance wrote:
[...]
I think we need to ensure with the infra team that itstools are installed on our machines.
That's the big question I haven't been able to answer yet. Preferably at least version 2.0.1.
Just talked briefly with the infra team and checked our setup:
What is in Ubuntu Precise? I assume the package is not installed but if it's available, we can add rules to the gate machines to have it installed...
Shaun, this is in precise: http://packages.ubuntu.com/precise/itstool This is a python package, isn't it? Get 2.0.1 on pypi.python.org and we can install it from there... Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Fri, 2014-05-09 at 18:04 +0200, Andreas Jaeger wrote:
On 05/09/2014 05:57 PM, Andreas Jaeger wrote:
On 05/09/2014 05:47 PM, Shaun McCance wrote:
[...]
I think we need to ensure with the infra team that itstools are installed on our machines.
That's the big question I haven't been able to answer yet. Preferably at least version 2.0.1.
Just talked briefly with the infra team and checked our setup:
What is in Ubuntu Precise? I assume the package is not installed but if it's available, we can add rules to the gate machines to have it installed...
Shaun,
this is in precise: http://packages.ubuntu.com/precise/itstool
This is a python package, isn't it? Get 2.0.1 on pypi.python.org and we can install it from there...
itstool 2.0.2 is now on pypi as a source package. It's one executable pure python script, plus some data files. I'm almost positive the pip install will work everywhere, but if somebody could test on non-Linux systems, that would be great. -- Shaun
Shaun McCance <shaunm@gnome.org> 2014/06/04 01:06
To
Andreas Jaeger <aj@suse.com>,
cc
openstack-i18n@lists.openstack.org, openstack-docs@lists.openstack.org
Subject
Re: [Openstack-i18n] [Openstack-docs] Switch to itstool for docs
Hello, Shaun and Andreas I have approved the blueprint. Please do the migration smoothly. Best regards Ying Chun Guo (Daisy) Shaun McCance <shaunm@gnome.org> wrote on 2014/06/04 01:06:09: translation?
On Fri, 2014-05-09 at 18:04 +0200, Andreas Jaeger wrote:
On 05/09/2014 05:57 PM, Andreas Jaeger wrote:
On 05/09/2014 05:47 PM, Shaun McCance wrote:
[...]
I think we need to ensure with the infra team that itstools are installed on our machines.
That's the big question I haven't been able to answer yet.
Preferably at
least version 2.0.1.
Just talked briefly with the infra team and checked our setup:
What is in Ubuntu Precise? I assume the package is not installed but if it's available, we can add rules to the gate machines to have it installed...
Shaun,
this is in precise: http://packages.ubuntu.com/precise/itstool
This is a python package, isn't it? Get 2.0.1 on pypi.python.org and we
can install it from there...
itstool 2.0.2 is now on pypi as a source package. It's one executable pure python script, plus some data files. I'm almost positive the pip install will work everywhere, but if somebody could test on non-Linux systems, that would be great.
-- Shaun
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
On 06/05/2014 08:05 AM, Ying Chun Guo wrote:
Hello, Shaun and Andreas
I have approved the blueprint.
Great, thanks! I'm offline for the next two weeks. I can help afterwards.
Please do the migration smoothly.
;) Andreas
Best regards Ying Chun Guo (Daisy)
Shaun McCance <shaunm@gnome.org> wrote on 2014/06/04 01:06:09:
Shaun McCance <shaunm@gnome.org> 2014/06/04 01:06
To
Andreas Jaeger <aj@suse.com>,
cc
openstack-i18n@lists.openstack.org, openstack-docs@lists.openstack.org
Subject
Re: [Openstack-i18n] [Openstack-docs] Switch to itstool for docs translation?
On Fri, 2014-05-09 at 18:04 +0200, Andreas Jaeger wrote:
On 05/09/2014 05:57 PM, Andreas Jaeger wrote:
On 05/09/2014 05:47 PM, Shaun McCance wrote:
[...]
I think we need to ensure with the infra team that itstools are installed on our machines.
That's the big question I haven't been able to answer yet. Preferably at least version 2.0.1.
Just talked briefly with the infra team and checked our setup:
What is in Ubuntu Precise? I assume the package is not installed but if it's available, we can add rules to the gate machines to have it installed...
Shaun,
this is in precise: http://packages.ubuntu.com/precise/itstool
This is a python package, isn't it? Get 2.0.1 on pypi.python.org and we can install it from there...
itstool 2.0.2 is now on pypi as a source package. It's one executable pure python script, plus some data files. I'm almost positive the pip install will work everywhere, but if somebody could test on non-Linux systems, that would be great.
-- Shaun
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
-- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 06/03/2014 07:06 PM, Shaun McCance wrote:
On Fri, 2014-05-09 at 18:04 +0200, Andreas Jaeger wrote:
On 05/09/2014 05:57 PM, Andreas Jaeger wrote:
On 05/09/2014 05:47 PM, Shaun McCance wrote:
[...]
I think we need to ensure with the infra team that itstools are installed on our machines.
That's the big question I haven't been able to answer yet. Preferably at least version 2.0.1.
Just talked briefly with the infra team and checked our setup:
What is in Ubuntu Precise? I assume the package is not installed but if it's available, we can add rules to the gate machines to have it installed...
Shaun,
this is in precise: http://packages.ubuntu.com/precise/itstool
This is a python package, isn't it? Get 2.0.1 on pypi.python.org and we can install it from there...
itstool 2.0.2 is now on pypi as a source package. It's one executable pure python script, plus some data files. I'm almost positive the pip install will work everywhere, but if somebody could test on non-Linux systems, that would be great.
Shaun, it is not working in a virtual environment. To reproduce: * Install python virtualenv package * Run "virtualenv its" * Run "source its/bin/activate" to use the virtualenv * Run now in the virtualenv "pip install itstool" It fails with: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ error: could not create '/usr/share/itstool': Permission denied ---------------------------------------- Cleaning up... Command /tmp/its/bin/python -c "import setuptools;__file__='/tmp/itstools/build/itstool/setup.py';exec(compile(open(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-M39Dm9-record/install-record.txt --single-version-externally-managed --install-headers /tmp/itstools/include/site/python2.7 failed with error code 1 in /tmp/its/build/itstool ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I suggest to not use '/usr/share/itstool/its' in setup.py. Changing this to 'itstool/its' fixed it for me. But then it failed with a missing dependency on libxml2. It would be great if the tool could live without the dependency and use lxml instead, otherwise it needs to be setup using site-packages (--system-site-packages) We cannot move forward unless itstool can be executed in a virtual environment (using site packages is possible but not desired). Shaun, could you take care of uploading a fixed package, please? Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Wed, 2014-08-20 at 12:37 +0200, Andreas Jaeger wrote:
Shaun, it is not working in a virtual environment. To reproduce: * Install python virtualenv package * Run "virtualenv its" * Run "source its/bin/activate" to use the virtualenv * Run now in the virtualenv "pip install itstool"
It fails with: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ error: could not create '/usr/share/itstool': Permission denied
---------------------------------------- Cleaning up... Command /tmp/its/bin/python -c "import setuptools;__file__='/tmp/itstools/build/itstool/setup.py';exec(compile(open(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-M39Dm9-record/install-record.txt --single-version-externally-managed --install-headers /tmp/itstools/include/site/python2.7 failed with error code 1 in /tmp/its/build/itstool ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I suggest to not use '/usr/share/itstool/its' in setup.py. Changing this to 'itstool/its' fixed it for me.
It scares me a bit to have different versions of the same package putting files in different places (pypi package vs upstream tarball). But that's probably live-with-able.
But then it failed with a missing dependency on libxml2. It would be great if the tool could live without the dependency and use lxml instead, otherwise it needs to be setup using site-packages (--system-site-packages)
But this is a complete non-starter. itstool does rather intricate things with XML. It's quite a bit more than parse-and-forget. To change it to use lxml would require a complete rewrite, and I'm not even sure it can be done. Most XML libraries don't let you shoot yourself in the foot as easily as libxml2 does.
We cannot move forward unless itstool can be executed in a virtual environment (using site packages is possible but not desired).
Shaun, could you take care of uploading a fixed package, please?
It's unfortunate the servers don't just have >=2.0.1. It's been out for a while now. This isn't high on my list right now, and it's too late in the release cycle to switch anyway. I'll get back to it after Juno. -- Shaun
On 08/20/2014 03:12 PM, Shaun McCance wrote:
On Wed, 2014-08-20 at 12:37 +0200, Andreas Jaeger wrote:
Shaun, it is not working in a virtual environment. To reproduce: * Install python virtualenv package * Run "virtualenv its" * Run "source its/bin/activate" to use the virtualenv * Run now in the virtualenv "pip install itstool"
It fails with: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ error: could not create '/usr/share/itstool': Permission denied
---------------------------------------- Cleaning up... Command /tmp/its/bin/python -c "import setuptools;__file__='/tmp/itstools/build/itstool/setup.py';exec(compile(open(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-M39Dm9-record/install-record.txt --single-version-externally-managed --install-headers /tmp/itstools/include/site/python2.7 failed with error code 1 in /tmp/its/build/itstool ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I suggest to not use '/usr/share/itstool/its' in setup.py. Changing this to 'itstool/its' fixed it for me.
It scares me a bit to have different versions of the same package putting files in different places (pypi package vs upstream tarball). But that's probably live-with-able.
If you do this correctly, it will install them the same way! The difference is installing system wide to /usr/share and installing locally in a virtual environment. datadir will be set properly if you do not hardcare /usr/share
But then it failed with a missing dependency on libxml2. It would be great if the tool could live without the dependency and use lxml instead, otherwise it needs to be setup using site-packages (--system-site-packages)
But this is a complete non-starter. itstool does rather intricate things with XML. It's quite a bit more than parse-and-forget. To change it to use lxml would require a complete rewrite, and I'm not even sure it can be done. Most XML libraries don't let you shoot yourself in the foot as easily as libxml2 does.
Both python-libxml2 and xml use libxml2 - just two different ways. But if rewriting is too hard, then let's not change it for now. It's not a ship-stopper.
We cannot move forward unless itstool can be executed in a virtual environment (using site packages is possible but not desired).
Shaun, could you take care of uploading a fixed package, please?
It's unfortunate the servers don't just have >=2.0.1. It's been out for a while now. This isn't high on my list right now, and it's too late in the release cycle to switch anyway. I'll get back to it after Juno.
Since this only affects manuals, we can do it any time, the change itself is not that huge and would not block us. If you don't have time right now, this is another issue... Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Wed, Aug 20, 2014 at 8:23 AM, Andreas Jaeger <aj@suse.com> wrote:
On 08/20/2014 03:12 PM, Shaun McCance wrote:
On Wed, 2014-08-20 at 12:37 +0200, Andreas Jaeger wrote:
Shaun, it is not working in a virtual environment. To reproduce: * Install python virtualenv package * Run "virtualenv its" * Run "source its/bin/activate" to use the virtualenv * Run now in the virtualenv "pip install itstool"
It fails with: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ error: could not create '/usr/share/itstool': Permission denied
---------------------------------------- Cleaning up... Command /tmp/its/bin/python -c "import
setuptools;__file__='/tmp/itstools/build/itstool/setup.py';exec(compile(open(__file__).read().replace('\r\n',
'\n'), __file__, 'exec'))" install --record /tmp/pip-M39Dm9-record/install-record.txt --single-version-externally-managed --install-headers /tmp/itstools/include/site/python2.7 failed with error code 1 in /tmp/its/build/itstool ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I suggest to not use '/usr/share/itstool/its' in setup.py. Changing this to 'itstool/its' fixed it for me.
It scares me a bit to have different versions of the same package putting files in different places (pypi package vs upstream tarball). But that's probably live-with-able.
If you do this correctly, it will install them the same way! The difference is installing system wide to /usr/share and installing locally in a virtual environment. datadir will be set properly if you do not hardcare /usr/share
But then it failed with a missing dependency on libxml2. It would be great if the tool could live without the dependency and use lxml instead, otherwise it needs to be setup using site-packages (--system-site-packages)
But this is a complete non-starter. itstool does rather intricate things with XML. It's quite a bit more than parse-and-forget. To change it to use lxml would require a complete rewrite, and I'm not even sure it can be done. Most XML libraries don't let you shoot yourself in the foot as easily as libxml2 does.
Both python-libxml2 and xml use libxml2 - just two different ways.
But if rewriting is too hard, then let's not change it for now. It's not a ship-stopper.
We cannot move forward unless itstool can be executed in a virtual environment (using site packages is possible but not desired).
Shaun, could you take care of uploading a fixed package, please?
It's unfortunate the servers don't just have >=2.0.1. It's been out for a while now. This isn't high on my list right now, and it's too late in the release cycle to switch anyway. I'll get back to it after Juno.
Since this only affects manuals, we can do it any time, the change itself is not that huge and would not block us. If you don't have time right now, this is another issue...
I think it's okay to press pause on this project as we hadn't planned for it in this release. Plus, until the source is tagged appropriately, we don't see the benefit from the tool update. So I'd like to continue to keep this in a holding pattern. Thanks, Anne
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
_______________________________________________ Openstack-docs mailing list Openstack-docs@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
I discussed this a bit with Daisy and Akihiro at the summit and both need some more investigation on this. Let me re-share some pointers for all here. I suggest that some of you translators have a look at patch 90766 and this thread and figure out whether there are any problems. This move to itstools is a move to newer and maintained tools that will simplify our live on the tools side. It only affects docs translation - the manuals - and not the core projects. So, this is related to all the resources you find on transifex under openstack-manuals. I'd like to see this happen because of the improvements it brings, so please evaluate it and speak up if you see problems - a "go ahead" would be also appreciated. Note that Daisy needs to approve the blue print before this will go in. Patch set 1 of patch https://review.openstack.org/#/c/90766/ shows the changes to the locale files, for example: https://review.openstack.org/#/c/90766/1/doc/user-guide-admin/locale/en_AU.p... These patches show what can be done with the tools - marking some sections as non-translatable (and thus not show up in transifex) sounds like a great idea to me: https://review.openstack.org/#/c/91873/ https://review.openstack.org/#/c/91872/ The conversation of the code is shown here: https://review.openstack.org/#/c/91869/ Especially this patch is interesting, it shows how easy it is to filter out what gets translated and what not: https://review.openstack.org/#/c/91869/3/os_doc_tools/resources/openstack.it... https://blueprints.launchpad.net/openstack-manuals/+spec/itstool-for-docs Full specification: https://wiki.openstack.org/wiki/Documentation/Translation#ItsTool_Conversion Shaun, for using itstool on the infra machines, we really need to have it on pypi. Can you make this happen, please? Also, please add to the commit message of each of your patches: blueprint itstool-for-docs Thanks, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
participants (4)
-
Andreas Jaeger
-
Anne Gentle
-
Shaun McCance
-
Ying Chun Guo