github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
k3s/translations
History
Kubernetes Submit Queue 018f8cfd54 Merge pull request #46339 from xilabao/fix-kubectl 
Automatic merge from submit-queue (batch tested with PRs 46782, 46719, 46339, 46609, 46494)

update default translation of annotations

**What this PR does / why we need it**:
```
using the local cluster. the help of kubectl is not corrent
# ./cluster/kubectl.sh
.......
Settings Commands:
  label          Update the labels on a resource
  annotate       Update the annotations on a resourcewatch is only supported on individual resources and resource
collections - %d resources were found
  completion     Output shell completion code for the specified shell (bash or zsh)

Other Commands:
  api-versions   Print the supported API versions on the server, in the form of "group/version"
  config         Modify kubeconfig files
  help           Help about any command
  plugin         Runs a command-line plugin
  version        Print the client and server version information

Use "kubectl <command> --help" for more information about a given command.
Use "kubectl options" for a list of global command-line options (applies to all commands).

```
**Which issue this PR fixes**:

**Special notes for your reviewer**:

**Release note**:

```release-note
NONE
```
 		2017-06-03 12:32:39 -07:00
..
kubectl Merge pull request #46339 from xilabao/fix-kubectl 2017-06-03 12:32:39 -07:00
test Update extraction script, sort messages, add .pot file. 2017-02-23 18:53:00 +00:00
README.md Fix go-xgettext (go get) reference on translations README 2017-05-27 21:24:13 +02:00
extract.py Extract a bunch more strings from kubectl 2017-04-06 20:12:50 -07:00

README.md

Translations README

This is a basic sketch of the workflow needed to add translations:

Adding/Updating Translations

New languages

Create translations/kubectl/<language>/LC_MESSAGES/k8s.po. There's no need to update translations/test/... which is only used for unit tests.

There is an example PR here which adds support for French.

Once you've added a new language, you'll need to register it in pkg/util/i18n/i18n.go by adding it to the knownTranslations map.

Wrapping strings

There is a simple script in translations/extract.py that performs simple regular expression based wrapping of strings. It can always use improvements to understand additional strings.

Extracting strings

Once the strings are wrapped, you can extract strings from go files using the go-xgettext command which can be installed with:

go get github.com/gosexy/gettext/go-xgettext

Once that's installed you can run hack/update-translations.sh, which will extract and sort any new strings.

Adding new translations

Edit the appropriate k8s.po file, poedit is a popular open source tool for translations. You can load the translations/kubectl/template.pot file to find messages that might be missing.

Once you are done with your .po file, generate the corresponding k8s.mo file. poedit does this automatically on save, but you can also use hack/update-translations.sh to perform the po to mo translation.

We use the English translation as the msgid.

Regenerating the bindata file

Run `./hack/generate-bindata.sh, this will turn the translation files into generated code which will in turn be packaged into the Kubernetes binaries.

Extracting strings

There is a script in translations/extract.py that knows how to do some simple extraction. It needs a lot of work.

Using translations

To use translations, you simply need to add:

import pkg/i18n
...
// Get a translated string
translated := i18n.T("Your message in english here")

// Get a translated plural string
translated := i18n.T("You had % items", items)

// Translated error
return i18n.Error("Something bad happened")

// Translated plural error
return i18n.Error("%d bad things happened")

Analytics