It seems there is a consensus that .tx/config should not be contained in the repo. I am okay with it. Perhaps folks who requires tx/config know the detail and there is no hurdle to configure it except time to check it :-) I have no idea there is a need to share it and where is a good place to share and keep it up-to-date. I am always frustrated with preparing tx/config though. On Wed, Mar 12, 2014 at 8:19 PM, Akihiro Motoki <amotoki@gmail.com> wrote:
At now, openstack-manuals, operations-guide and horizon have .tx/config in their repos. Most translation works are done for these projects and not for other projects.
"tx init" just prepares a minimum tx/config without any resource definitions We need to run "tx set ....." below or edit it manually per resource (i.e., per document). openstack-manuals has at least 12 resources (and horizon has 3). For other projects, each has only one resource.
tx set --auto-local -r openstack-manuals-i18n.${DOCNAME} \ "${DocFolder}/${DOCNAME}/locale/<lang>.po" --source-lang en \ --source-file ${DocFolder}/${DOCNAME}/locale/${DOCNAME}.pot \ -t PO --execute
I think this is the reason openstack-manuals and horizon have tx/config in their repos now.
On Wed, Mar 12, 2014 at 7:46 PM, Andreas Jaeger <aj@suse.com> wrote:
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