You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by milamberspace <gi...@git.apache.org> on 2015/08/14 13:37:47 UTC
[GitHub] cloudstack pull request: Update L10N resource files on 4.5 branch ...
GitHub user milamberspace opened a pull request:
https://github.com/apache/cloudstack/pull/697
Update L10N resource files on 4.5 branch with 4.5 translation strings…
… from Transifex (20150814)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/milamberspace/cloudstack update-4.5-20150814
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/697.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #697
----
commit 35d522653f1c2ed2a00e9b35490c3f7de3bc38d8
Author: Milamber <mi...@apache.org>
Date: 2015-08-14T09:40:21Z
Update L10N resource files on 4.5 branch with 4.5 translation strings from Transifex (20150814)
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cloudstack pull request: Update L10N resource files on 4.5 branch ...
Posted by milamberspace <gi...@git.apache.org>.
Github user milamberspace commented on the pull request:
https://github.com/apache/cloudstack/pull/697#issuecomment-132515960
Thanks for the merge.
yes not necessary, the PR #699 make the works for master branch.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cloudstack pull request: Update L10N resource files on 4.5 branch ...
Posted by karuturi <gi...@git.apache.org>.
Github user karuturi commented on the pull request:
https://github.com/apache/cloudstack/pull/697#issuecomment-132494328
I merged this only to 4.5. I though merge to master is not required based on #699. Let me know if this needs to go to master as well.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cloudstack pull request: Update L10N resource files on 4.5 branch ...
Posted by milamberspace <gi...@git.apache.org>.
Github user milamberspace commented on the pull request:
https://github.com/apache/cloudstack/pull/697#issuecomment-131126574
Yes it's right, the original string has been changed, so the (old) translation has been removed on Transifer.
Long version:
* Cloudstack has now 2 new options on wizard for the local storage (one for user vm and one for system vm)
* The primary language words for label.local.storage.enabled has been changed (old version was more shorter that the new, i.e. the mention to "user vm")
* So, when I have uploaded the source language to transifex, this last has removed all translations of this key.
* Fr or pt_BR (here) translators has (re)translated the key since the upload, so, you have a new string for theses languages
* But currently, the others languages doesn't have been (re)translated to bring the new version with the user vm mention.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cloudstack pull request: Update L10N resource files on 4.5 branch ...
Posted by runseb <gi...@git.apache.org>.
Github user runseb commented on the pull request:
https://github.com/apache/cloudstack/pull/697#issuecomment-132253810
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cloudstack pull request: Update L10N resource files on 4.5 branch ...
Posted by terbolous <gi...@git.apache.org>.
Github user terbolous commented on the pull request:
https://github.com/apache/cloudstack/pull/697#issuecomment-131095612
label.local.storage.enabled is removed from multiple languages, but added to one. Is that right?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cloudstack pull request: Update L10N resource files on 4.5 branch ...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/697
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cloudstack pull request: Update L10N resource files on 4.5 branch ...
Posted by terbolous <gi...@git.apache.org>.
Github user terbolous commented on the pull request:
https://github.com/apache/cloudstack/pull/697#issuecomment-132484646
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---