Track .tx in git or not?
Hello, The folder .tx is used to save the configuration of Transifex Client, which supports our translation process. The folder .tx in openstack-manuals is in managed by git index and tracked changes by git. The file .tx/config saves the mapping information between local po files and the resources in Transifex. If a new po file is added, the file .tx/config will be changed. Now the changes of folder .tx will cause a failure of the job propose_translation_update_manuals. I'm going to fix it. Both of below two ways work: removing .tx from git tree and index, or changing propose_translation_update_manuals.sh to track changes in .tx. I just don't know which one is the better choice. Removing .tx from git because: .tx has no relationship with openstack-manuals. The scripts propose_translation_update_manuals.sh and upstream_translation_update_manuals.sh can use command lines to create and edit the configurations. Tracking .tx in git because: when some people want to use Transifex Client to manage po files, with .tx, they can use simple Transifex Client command line to pull the translations, and don't need to understand the complex mapping information. There is no consensus in OpenStack projects. Some projects don't track and some projects track. I think we need a consensus at least within all documentation projects. I prefer the first opinion - removing .tx from git Please let me know your thoughts to this question. Thank you. Best regards Ying Chun Guo (Daisy)
On 03/12/2014 04:35 AM, Ying Chun Guo wrote:
Hello,
The folder .tx is used to save the configuration of Transifex Client, which supports our translation process. The folder .tx in openstack-manuals is in managed by git index and tracked changes by git. The file .tx/config saves the mapping information between local po files and the resources in Transifex. If a new po file is added, the file .tx/config will be changed.
Now the changes of folder .tx will cause a failure of the job propose_translation_update_manuals. I'm going to fix it.
Thanks for fixing this for good, Daisy!
Both of below two ways work: removing .tx from git tree and index, or changing propose_translation_update_manuals.sh to track changes in .tx. I just don't know which one is the better choice.
Removing .tx from git because: .tx has no relationship with openstack-manuals. The scripts propose_translation_update_manuals.sh and upstream_translation_update_manuals.sh can use command lines to create and edit the configurations.
Tracking .tx in git because: when some people want to use Transifex Client to manage po files, with .tx, they can use simple Transifex Client command line to pull the translations, and don't need to understand the complex mapping information.
There is no consensus in OpenStack projects. Some projects don't track and some projects track. I think we need a consensus at least within all documentation projects. I prefer the first opinion - removing .tx from git Please let me know your thoughts to this question.
I'm fine with removing .tx from git. Thanks for your patch for that - this needs changes in config as well, please review my patch https://review.openstack.org/79866 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
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. Thanks, Akihiro On Wed, Mar 12, 2014 at 4:21 PM, Andreas Jaeger <aj@suse.com> wrote:
On 03/12/2014 04:35 AM, Ying Chun Guo wrote:
Hello,
The folder .tx is used to save the configuration of Transifex Client, which supports our translation process. The folder .tx in openstack-manuals is in managed by git index and tracked changes by git. The file .tx/config saves the mapping information between local po files and the resources in Transifex. If a new po file is added, the file .tx/config will be changed.
Now the changes of folder .tx will cause a failure of the job propose_translation_update_manuals. I'm going to fix it.
Thanks for fixing this for good, Daisy!
Both of below two ways work: removing .tx from git tree and index, or changing propose_translation_update_manuals.sh to track changes in .tx. I just don't know which one is the better choice.
Removing .tx from git because: .tx has no relationship with openstack-manuals. The scripts propose_translation_update_manuals.sh and upstream_translation_update_manuals.sh can use command lines to create and edit the configurations.
Tracking .tx in git because: when some people want to use Transifex Client to manage po files, with .tx, they can use simple Transifex Client command line to pull the translations, and don't need to understand the complex mapping information.
There is no consensus in OpenStack projects. Some projects don't track and some projects track. I think we need a consensus at least within all documentation projects. I prefer the first opinion - removing .tx from git Please let me know your thoughts to this question.
I'm fine with removing .tx from git. Thanks for your patch for that - this needs changes in config as well, please review my patch https://review.openstack.org/79866
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
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
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
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
On 03/12/2014 04:35 AM, Ying Chun Guo wrote:
Hello,
The folder .tx is used to save the configuration of Transifex Client, which supports our translation process. The folder .tx in openstack-manuals is in managed by git index and tracked changes by git. The file .tx/config saves the mapping information between local po files and the resources in Transifex. If a new po file is added, the file .tx/config will be changed.
Now the changes of folder .tx will cause a failure of the job propose_translation_update_manuals. I'm going to fix it. Both of below two ways work: removing .tx from git tree and index, or changing propose_translation_update_manuals.sh to track changes in .tx. I just don't know which one is the better choice.
Removing .tx from git because: .tx has no relationship with openstack-manuals. The scripts propose_translation_update_manuals.sh and upstream_translation_update_manuals.sh can use command lines to create and edit the configurations.
Tracking .tx in git because: when some people want to use Transifex Client to manage po files, with .tx, they can use simple Transifex Client command line to pull the translations, and don't need to understand the complex mapping information.
There is no consensus in OpenStack projects. Some projects don't track and some projects track. I think we need a consensus at least within all documentation projects. I prefer the first opinion - removing .tx from git Please let me know your thoughts to this question.
Daisy, could you send a patch for operations-guide as well, 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
Done. Please review: https://review.openstack.org/#/c/80162 Best regards Ying Chun Guo (Daisy) Andreas Jaeger <aj@suse.com> wrote on 2014/03/12 18:41:23:
Andreas Jaeger <aj@suse.com> 2014/03/12 18:41
To
Ying Chun Guo/China/IBM@IBMCN, openstack-docs@lists.openstack.org,
cc
openstack-i18n@lists.openstack.org
Subject
Re: [Openstack-docs] Track .tx in git or not?
On 03/12/2014 04:35 AM, Ying Chun Guo wrote:
Hello,
The folder .tx is used to save the configuration of Transifex Client, which supports our translation process. The folder .tx in openstack-manuals is in managed by git index and tracked changes by git. The file .tx/config saves the mapping information between local po files and the resources in Transifex. If a new po file is added, the file .tx/config will be changed.
Now the changes of folder .tx will cause a failure of the job propose_translation_update_manuals. I'm going to fix it. Both of below two ways work: removing .tx from git tree and index, or changing propose_translation_update_manuals.sh to track changes in .tx. I just don't know which one is the better choice.
Removing .tx from git because: .tx has no relationship with openstack-manuals. The scripts propose_translation_update_manuals.sh and upstream_translation_update_manuals.sh can use command lines to create and edit the configurations.
Tracking .tx in git because: when some people want to use Transifex Client to manage po files, with .tx, they can use simple Transifex Client command line to pull the translations, and don't need to understand the complex mapping information.
There is no consensus in OpenStack projects. Some projects don't track and some projects track. I think we need a consensus at least within all documentation projects. I prefer the first opinion - removing .tx from git Please let me know your thoughts to this question.
Daisy, could you send a patch for operations-guide as well, 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
participants (3)
-
Akihiro Motoki
-
Andreas Jaeger
-
Ying Chun Guo