Support i18n in the errors project

[xingzhou]

Add the translation files and the translation process description under
the newly created i18n folder.

The translation is used for the CC i18n enablement work, here is the first patchfor CC i18n enablement: cloudfoundry/cloud_controller_ng#267

Please refer to the README.md included in this patch for more information.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/74283818.

[ghost]

@xingzhou Hey looks good! Could you please remove the .DS_Store file?

Thanks

@leoRoss & @DanLavine
CF Community Pair

[xingzhou]

@leoRoss & @DanLavine , thanks for the review, have removed the .DS_Store file from the PR.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/74354826.

[ghost]

@MarkKropf Should we move this PR to Runtime's Tracker?

CF Community Pair
@leoRoss & @DanLavine

[MarkKropf]

Yes, let's pull this in

[jpalermo]

@xingzhou We don't think it is a good idea to copy all of the english language translations into the other language files. While it gives translators a point to start from, it is unlikely that all translation files will be updated correctly. Having 11 files that all diverge from each other would be confusing and hard to keep in sync.

We think it would be best to have empty files for translations that do not yet exist (or even no files at all).

The I18N library (in the Cloud Controller pull request) should be configured with a fall back to the english locale so if a translation does not exist, it will simply use the english.

Also, it is confusing to have errors in both the english localization files and also in v2.yml. Since the messages in v2.yml are no longer used, it would make sense to remove them from there.

And finally if you could squash any commits into a single one so the .DS_Store file and any other file histories don't make it into the repo.

[xingzhou]

Hi @jpalermo, thanks for your comments!
Here is what I'm thinking, for our discussion:

1. It's ok for using empty message files for those languages not finish translation yet, but I use those file to keep it consistent with the original CLI I18n solution. If you think that we need to use the empty files, that would be fine to me.
2. For the reason for keeping messages in v2.yml, as I'm thinking this vendor/erros messages are shared during different CF components, for those projects who is not i18n enabled, they are still using the origin messages, so I keep the messages in v2.yml in case they are still working. A second reason for doing this is that, when we add new error message or the error message translation is missing in both English and the target language locale, we can still ensure that we can find it in the v2.yml.
3. for the .DS_Store file, I think I've removed it in the second commit, do we need to only submit only one commit per PR? thanks for your information!

[MarkKropf]

@xingzhou yes, we're trying to avoid having to update more than one english translation every time a change is needed to keep the other files in sync.

[xingzhou]

Ok, I can change to use an empty file, and according to the conversation in cloudfoundry/cloud_controller_ng#267, the message file structure will also be changed, will make new patch later

[dieucao]

@xingzhou Closing this PR as it's been a while with no activity. If you have a chance to make the requested changes and resubmit the PR we'll pull it in then.