cleanup translations and fix update-translations.sh

[atiratree]

What type of PR is this?

/kind cleanup
/sig cli

What this PR does / why we need it:

• the script hack/update-translations.sh stopped working
• translations include old currently unused msgids and do not include new msgids

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

• I added a new option to the update-translations.sh script to fix old/new msgids. I am not sure if we should include this logic with already present -g option or have it as a new standalone option -k.
• I am deprecating old msgids but keeping them in the file as obsolete (#~). It is like that, because it is nice to run this script automatically, but to keep the old unused translations in the file. So the translators can easily copy changed translation when for example only one letter changed. The obsoleted translations need to be removed manually, which is easy since they are at the end of the file.
• I am not sure if I should split this PR into multiple ones? The first commit is fixing/adding new logic to update-translations.sh and the rest are various generated changes

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

NONE

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: login-issues@jira.linuxfoundation.org

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[k8s-ci-robot]

Welcome @atiratree!

It looks like this is your first PR to kubernetes/kubernetes 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kubernetes has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @atiratree. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[atiratree]

/check-cla

[atiratree]

/assign @soltysh

[dougsland]

@atiratree could you please squash your patches so would be easier to review it?

[atiratree]

@dougsland I have squashed all the generated changes to one commit, but kept the features commits for better clarity

[atiratree]

rebased

[soltysh]

/ok-to-test
/triage accepted

[soltysh]

/priority backlog

[soltysh]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: atiratree, soltysh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• hack/OWNERS [soltysh]
• staging/src/k8s.io/kubectl/OWNERS [soltysh]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[hwdef]

I'm a bit confused about this pr, if an English language is not translated and it needs to be translated, it won't be added to the corresponding language's po file after running this script with -k.

The result now is that the en_US file has 6,000+ lines but the other languages have only a few lines. For example, zh_CN has only 3000+ lines and ko_KR has less than a hundred lines.

@atiratree
Can you help me with something?

[atiratree]

@hwdef We are only storing the translated parts. The rest will be defaulted to english. If you want to add new translations. you need to first generate the template.pot file, then you can open the k8s.po file for each language in poedit where you can import the empty lines from the template.pot. Then you can manually translate and edit in poedit. You may find some of the commented out translations good for reuse if only for an example a punctuation changed in the source text

Nevertheless, the translations and the script are not really well maintained. So, if you want to help with this effort , I suggest to visit sig-cli call and ask there first.

Useful resource is also the gettext documentation: https://www.gnu.org/software/gettext/manual/gettext.html#Template

[hwdef]

Thank you! I wil try what you said.

[hwdef]

 then you can open the k8s.po file for each language in poedit where you can import the empty lines from the template.pot

Do you mean this?

[atiratree]

yes, although for some finer tuning, you may need to consult the gettext CLI tools/documentation or do it manually

[hwdef]

Thank you very much!