[Openstack-i18n] [Openstack-docs] Track .tx in git or not?
Andreas Jaeger
aj at suse.com
Wed Mar 12 10:46:20 UTC 2014
On 03/12/2014 11:37 AM, Akihiro Motoki wrote:
> Hi,
>
> I have one thoing I would like to mention.
>
> Having .tx/config file in openstack-manuals repository is useful for
> translators who
> generate translated version of documents. If we remove .tx/config from
> the repository,
> such translators needs to check the transifex repository and create
> .tx/config manually.
> It is not convenient. We can have .tx/config in the documentation I18N page, but
> it requires some additional steps every time to prepare new git clone.
> The merit to have .tx/config in the repo helps us keep .tx/config up-to-date and
> we can share it. Translators can maintain .tx/config privately but
> there is no place to share it.
>
> Though transifex configruation file .tx/config is not related and I understand
> such translators is very limited, it is worth considered.
> Even if we can get the command line example from openstack-infra/config,
> it doesn't make sense because transifex config and jenkins script are
> not related.
>
> I don't have a strong opinion on it, but I don't feel it comfortable.
> If it is remove, I will just fork openstack-manuals repository to have
> .tx/config
> and sync it with the upstream by cron.
Isn't it just running "tx --init..." to create the file?
I just looked at my checked out OpenStack repositories, so
openstack-manuals and operations-guide are the only two repos that have
this - but many more are translated. So, how are you handling other repos?
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
More information about the Openstack-i18n
mailing list