Review inconsistent capitalization across translation strings

[t1m0thyj]

Is your feature request related to a problem? Please describe.

We would like to investigate automatic AI translation for Zowe Explorer, but need to review our English strings first. Thanks @phaumer for reporting this:

One thing I observe is that the English strings need a review first. If the English is not clear then the translation might be wrong as well. When it comes to terminology, consistency in the English strings is very important. Things like capitalization have a huge impact. For example, there are cases were credentials manager is written in lower case and other cases where it is like a name in uppercase. In the former case it is translated to the German equivalent and in the later case it keeps the English term as it assumes a name. So we need to either capitalize everywhere or nowhere. Same with data set and other terms.

I am not sure if we should use these files now, though, before the English review, as I can see several things now inconsistent in the German translation, e.g. because of inconsistent capitalization. It could cause confusion. Could the Zowe doc writers have a go at the Zowe strings first?

Describe the solution you'd like

Someone on the team should review the strings to make them consistent, and send them to @anaxceron for final review.

Describe alternatives you've considered

We could leave the translations strings as they are now, but the inconsistencies will yield inaccurate translations.

Additional context

All the translation strings can be found in these 2 files:

• package.nls.json - strings for commands in package.json, maintained manually
• bundle.l10n.json - strings throughout the code, generated automatically

[github-actions]

Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 10 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.