Looking at the daily imports we do for our translations, a lot of that is importing pot files (translation source). Do we really need these for anything in the git trees? We've stopped importing those pot files which are not translated at all but import pot files that have translations and update them daily (only if there are real translations as well). I really wonder whether we need these pot files in our git repositories at all, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
As a translator, I usually use POT files to locate where a particular source string is defined in a source code. At the moment, Zanata provides no way that translators can identify a location in a source code of a particular string, so POT files are really useful for translators without development environments. I wrote translator tips to use POT files at [1] . In addition, even if a translator has an environment to generate POT files, most git repo does not provide a convenient way to extract strings. The infra script has it own functions of message extraction and there is no convenient way to do the same thing. If this issue is over, I don't think we need to have POT files in our tree. All of my comment above are from the point of view of translators. Akihiro [1] http://docs.openstack.org/developer/i18n/translation_tips.html 2016-04-21 20:54 GMT+09:00 Andreas Jaeger <aj@suse.com>:
Looking at the daily imports we do for our translations, a lot of that is importing pot files (translation source).
Do we really need these for anything in the git trees?
We've stopped importing those pot files which are not translated at all but import pot files that have translations and update them daily (only if there are real translations as well).
I really wonder whether we need these pot files in our git repositories at all,
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
One thing to note. If we have another place where we can view generated POT files, I am okay to drop POT files from our git repos. I don't think it is helpful to dowload POT files from Zanata because we need to download them every time we want to check locations of strings. 2016-04-21 21:09 GMT+09:00 Akihiro Motoki <amotoki@gmail.com>:
As a translator, I usually use POT files to locate where a particular source string is defined in a source code. At the moment, Zanata provides no way that translators can identify a location in a source code of a particular string, so POT files are really useful for translators without development environments. I wrote translator tips to use POT files at [1] .
In addition, even if a translator has an environment to generate POT files, most git repo does not provide a convenient way to extract strings. The infra script has it own functions of message extraction and there is no convenient way to do the same thing.
If this issue is over, I don't think we need to have POT files in our tree.
All of my comment above are from the point of view of translators.
Akihiro
[1] http://docs.openstack.org/developer/i18n/translation_tips.html
2016-04-21 20:54 GMT+09:00 Andreas Jaeger <aj@suse.com>:
Looking at the daily imports we do for our translations, a lot of that is importing pot files (translation source).
Do we really need these for anything in the git trees?
We've stopped importing those pot files which are not translated at all but import pot files that have translations and update them daily (only if there are real translations as well).
I really wonder whether we need these pot files in our git repositories at all,
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
On 2016-04-21 14:11, Akihiro Motoki wrote:
One thing to note.
If we have another place where we can view generated POT files, I am okay to drop POT files from our git repos.
I don't think it is helpful to dowload POT files from Zanata because we need to download them every time we want to check locations of strings.
We generate all POT files when we push to Zanata. As part of that we could push them to something like http://tarballs.openstack.org/$project/$branch/$file.pot as well. Advantage would be that those pot files are the exact same content as in Zanata - the in-tree is always lagging behind. Would that make life easier for translators? Any other ideas? Otherwise, I'm fine with keeping status quo if that's the best solution ;) Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
2016-04-21 21:17 GMT+09:00 Andreas Jaeger <aj@suse.com>:
On 2016-04-21 14:11, Akihiro Motoki wrote:
One thing to note.
If we have another place where we can view generated POT files, I am okay to drop POT files from our git repos.
I don't think it is helpful to dowload POT files from Zanata because we need to download them every time we want to check locations of strings.
We generate all POT files when we push to Zanata. As part of that we could push them to something like http://tarballs.openstack.org/$project/$branch/$file.pot as well.
Advantage would be that those pot files are the exact same content as in Zanata - the in-tree is always lagging behind.
Would that make life easier for translators?
I like this approach. We can share the URL at the top page of Zanata. In addition, as a reviewer, we would like to see less translation patches :-)
Any other ideas? Otherwise, I'm fine with keeping status quo if that's the best solution ;)
I would like to see opinions from others :) Akihiro
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 2016-04-21 14:25, Akihiro Motoki wrote:
2016-04-21 21:17 GMT+09:00 Andreas Jaeger <aj@suse.com>:
On 2016-04-21 14:11, Akihiro Motoki wrote:
One thing to note.
If we have another place where we can view generated POT files, I am okay to drop POT files from our git repos.
I don't think it is helpful to dowload POT files from Zanata because we need to download them every time we want to check locations of strings.
We generate all POT files when we push to Zanata. As part of that we could push them to something like http://tarballs.openstack.org/$project/$branch/$file.pot as well.
Advantage would be that those pot files are the exact same content as in Zanata - the in-tree is always lagging behind.
Would that make life easier for translators?
I like this approach. We can share the URL at the top page of Zanata.
Yes, that's an option.
In addition, as a reviewer, we would like to see less translation patches :-)
Right now, a translation import should only happen if at least one po file changes. So, the frequency of imports will not change - just the size of it. And the size will change dramatically.
Any other ideas? Otherwise, I'm fine with keeping status quo if that's the best solution ;)
I would like to see opinions from others :)
;) Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 2016-04-21 14:25, Akihiro Motoki wrote:
2016-04-21 21:17 GMT+09:00 Andreas Jaeger <aj@suse.com>:
On 2016-04-21 14:11, Akihiro Motoki wrote:
One thing to note.
If we have another place where we can view generated POT files, I am okay to drop POT files from our git repos.
I don't think it is helpful to dowload POT files from Zanata because we need to download them every time we want to check locations of strings.
We generate all POT files when we push to Zanata. As part of that we could push them to something like http://tarballs.openstack.org/$project/$branch/$file.pot as well.
Advantage would be that those pot files are the exact same content as in Zanata - the in-tree is always lagging behind.
Would that make life easier for translators?
I like this approach. We can share the URL at the top page of Zanata.
Yes, that's an option.
+1
In addition, as a reviewer, we would like to see less translation patches :-)
Right now, a translation import should only happen if at least one po file changes. So, the frequency of imports will not change - just the size of it. And the size will change dramatically.
+1 It's good the size will change dramatically. Kato
Any other ideas? Otherwise, I'm fine with keeping status quo if that's the best solution ;)
I would like to see opinions from others :)
;)
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
On 2016-04-21 14:09, Akihiro Motoki wrote:
As a translator, I usually use POT files to locate where a particular source string is defined in a source code. At the moment, Zanata provides no way that translators can identify a location in a source code of a particular string, so POT files are really useful for translators without development environments. I wrote translator tips to use POT files at [1] .
In addition, even if a translator has an environment to generate POT files, most git repo does not provide a convenient way to extract strings. The infra script has it own functions of message extraction and there is no convenient way to do the same thing.
If this issue is over, I don't think we need to have POT files in our tree.
All of my comment above are from the point of view of translators.
Thanks, this helps. So, let's keep these POT files in for now and once Zanata offers the functionality, let's revisit. Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
In practice, its always good to keep the pot files in repo just for reference and backup even you can download from Zanata. But it doesnt need to be in the master branch. Could be in string freeze branch. --------------------------------------------- Alex Eng Senior Software Engineer Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457> Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com On Thu, Apr 21, 2016 at 9:54 PM, Andreas Jaeger <aj@suse.com> wrote:
Looking at the daily imports we do for our translations, a lot of that is importing pot files (translation source).
Do we really need these for anything in the git trees?
We've stopped importing those pot files which are not translated at all but import pot files that have translations and update them daily (only if there are real translations as well).
I really wonder whether we need these pot files in our git repositories at all,
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
You can find always current pot files now at: http://tarballs.openstack.org/translation-source/ Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
You can find always current pot files now at: http://tarballs.openstack.org/translation-source/
Andreas
Thans! It's useful. Kato
Thanks, but it looks not perfect. http://tarballs.openstack.org/translation-source/horizon/master/ Horizon repo has two django.pot and two djangojs.pot, but I see only one django.pot and djangojs.pot. We need to keep the full paths from the top of the repository. Akihiro 2016-05-06 15:30 GMT+09:00 Andreas Jaeger <aj@suse.com>:
You can find always current pot files now at: http://tarballs.openstack.org/translation-source/
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
On 05/06/2016 07:57 PM, Akihiro Motoki wrote:
Thanks, but it looks not perfect.
http://tarballs.openstack.org/translation-source/horizon/master/ Horizon repo has two django.pot and two djangojs.pot, but I see only one django.pot and djangojs.pot. We need to keep the full paths from the top of the repository.
Oops, I missed that. Thanks for telling me. Fixed with: https://review.openstack.org/313698 Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
2016-05-07 5:55 GMT+09:00 Andreas Jaeger <aj@suse.com>:
On 05/06/2016 07:57 PM, Akihiro Motoki wrote:
Thanks, but it looks not perfect.
http://tarballs.openstack.org/translation-source/horizon/master/ Horizon repo has two django.pot and two djangojs.pot, but I see only one django.pot and djangojs.pot. We need to keep the full paths from the top of the repository.
Oops, I missed that. Thanks for telling me.
Fixed with: https://review.openstack.org/313698
Thanks! The patch has been merged and it works well for neutron. I noticed 'glance' directory [1] contains the old format. Do we need to clean them up manually or is it cleanup when a new merge for glance happens? [1] http://tarballs.openstack.org/translation-source/glance/master/ Akihiro
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 05/07/2016 01:09 AM, Akihiro Motoki wrote:
2016-05-07 5:55 GMT+09:00 Andreas Jaeger <aj@suse.com>:
On 05/06/2016 07:57 PM, Akihiro Motoki wrote:
Thanks, but it looks not perfect.
http://tarballs.openstack.org/translation-source/horizon/master/ Horizon repo has two django.pot and two djangojs.pot, but I see only one django.pot and djangojs.pot. We need to keep the full paths from the top of the repository.
Oops, I missed that. Thanks for telling me.
Fixed with: https://review.openstack.org/313698
Thanks! The patch has been merged and it works well for neutron.
I noticed 'glance' directory [1] contains the old format. Do we need to clean them up manually or is it cleanup when a new merge for glance happens?
I'll get these cleaned up... Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
participants (5)
-
Akihiro Motoki
-
Alex Eng
-
Andreas Jaeger
-
KATO Tomoyuki
-
Kato, Tomoyuki