]> git.proxmox.com Git - pve-docs.git/blame - translation.adoc
backup: clarify that CLI means FS-level and highlight retention-note
[pve-docs.git] / translation.adoc
CommitLineData
8d7b6807
DJ
1[[translation]]
2Translating {pve}
3-----------------
4ifdef::wiki[]
5:pve-toplevel:
6endif::wiki[]
7
8
06fd1d0f
DW
9
10The {pve} user interface is in English by default. However, thanks to the
11contributions of the community, translations to other languages are also available.
12We welcome any support in adding new languages, translating the latest features, and
13improving incomplete or inconsistent translations.
14
15We use https://www.gnu.org/software/gettext/[gettext] for the management of the
16translation files. Tools like https://poedit.net/[Poedit] offer a nice user
17interface to edit the translation files, but you can use whatever editor you're
18comfortable with. No programming knowledge is required for translating.
19
20Translating with git
21~~~~~~~~~~~~~~~~~~~~
8d7b6807 22
e63e47fb
AL
23The language files are available as a
24https://git.proxmox.com/?p=proxmox-i18n.git[git repository]. If you are familiar
25with git, please contribute according to our
26{webwiki-url}Developer_Documentation[Developer Documentation].
8d7b6807 27
06fd1d0f
DW
28You can create a new translation by doing the following (replace <LANG> with the
29language ID):
30
31 # git clone git://git.proxmox.com/git/proxmox-i18n.git
32 # cd proxmox-i18n
33 # make init-<LANG>.po
34
35Or you can edit an existing translation, using the editor of your choice:
36
37 # poedit <LANG>.po
38
39
40Translating without git
41~~~~~~~~~~~~~~~~~~~~~~~
42
43Even if you are not familiar with git, you can help translate {pve}.
44To start, you can download the language files
45https://git.proxmox.com/?p=proxmox-i18n.git;a=tree[here]. Find the
46language you want to improve, then right click on the "raw" link of this language
47file and select 'Save Link As...'. Make your changes to the file, and then
48send your final translation directly to office(at)proxmox.com, together with a
e63e47fb
AL
49signed
50{webwiki-url}Developer_Documentation#Software_License_and_Copyright[contributor license agreement].
8d7b6807 51
06fd1d0f
DW
52
53Testing the Translation
54~~~~~~~~~~~~~~~~~~~~~~~
55
56In order for the translation to be used in {pve}, you must first translate
57the `.po` file into a `.js` file. You can do this by invoking the following script,
58which is located in the same repository:
59
60 # ./po2js.pl -t pve xx.po >pve-lang-xx.js
61
62The resulting file `pve-lang-xx.js` can then be copied to the directory
63`/usr/share/pve-i18n`, on your proxmox server, in order to test it out.
64
65Alternatively, you can build a deb package by running the following command from
66the root of the repository:
67
68 # make deb
69
70IMPORTANT: For either of these methods to work, you need to have the following
71perl packages installed on your system. For Debian/Ubuntu:
72
73 # apt-get install perl liblocale-po-perl libjson-perl
74
75
76Sending the Translation
77~~~~~~~~~~~~~~~~~~~~~~~
78You can send the finished translation (`.po` file) to the Proxmox team at the address
3a433e9b 79office(at)proxmox.com, along with a signed contributor license agreement.
06fd1d0f 80Alternatively, if you have some developer experience, you can send it as a
65eb814d
TL
81patch to the {pve} development mailing list. See
82{webwiki-url}Developer_Documentation[Developer Documentation].