[OpenStack-I18n] pot files in git trees?

Akihiro Motoki amotoki at gmail.com
Thu Apr 21 12:11:40 UTC 2016

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 at 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 at 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 at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

More information about the OpenStack-I18n mailing list