Difference between revisions of "Translations"
(17 intermediate revisions by 10 users not shown) | |||
Line 1: | Line 1: | ||
− | + | {{Note| This article is not actively maintained, see the reference documentation for an up to date guide https://pve.proxmox.com/pve-docs/pve-admin-guide.html#translation|reminder}} | |
− | + | == Translation Flow == | |
− | |||
− | + | Language files are located in the [https://git.proxmox.com/?p=proxmox-i18n.git;a=tree git.proxmox.com proxmox-i18n] git repository, you can download them through the webinterface or clone the whole repository locally using git: | |
− | |||
− | |||
− | + | git clone git://git.proxmox.com/git/proxmox-i18n.git | |
− | |||
− | + | You can then create new translation with (replace <LANG> with the language ID) | |
− | |||
− | + | cd proxmox-i18n | |
+ | make init-<LANG>.po | ||
− | + | For testing your work in the web-interface you need to translate the PO files to a .js file by invoking script located at same directory. | |
− | + | First install all required dependencies for that script, for Ubuntu or Debian based system you would do that with: | |
− | + | apt install perl liblocale-po-perl libjson-perl | |
− | + | Then run the script: | |
+ | ./po2js.pl -t pve xy.po >pve-lang-xy.js | ||
− | + | The resulting file <code>pve-lang-xx.js</code> should be copied to the <code>/usr/share/pve-i18n/</code> directory on your Proxmox VE server. | |
− | |||
− | |||
− | |||
− | === | + | == How to Edit Translation Files == |
− | |||
− | |||
− | |||
− | + | The translations can be done by using [http://www.poedit.net/ poedit], an easy-to-use editor specialized for PO files. | |
− | |||
− | |||
− | |||
− | + | You can also use a common text editor, for example: <code>vim</code>, <code>Emacs</code> or <code>Notepad</code>. | |
− | |||
− | |||
− | + | There is no programming knowledge necessary to translate. | |
− | |||
− | |||
− | |||
− | === | + | == Submitting Updated or New Translations == |
− | |||
− | |||
− | |||
− | + | You can send finished translation to the Proxmox team by either using | |
− | * | + | * our git email patch work flow, see [[Developer Documentation#Preparing_Patches|Developer Documentation#Preparing_Patches]] |
− | + | : Note that large patch emails are automatically queued for moderation, so it may take a bit until it shows up. | |
− | * | + | * the full updated <code>xy.po</code> file office(at)proxmox.com email address. |
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | Remember to include a signed contributor license agreement if not already present, see [[Developer Documentation#Software License and Copyright]] for details. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
[[Category: HOWTO]] | [[Category: HOWTO]] | ||
− |
Latest revision as of 07:29, 5 December 2022
Note: This article is not actively maintained, see the reference documentation for an up to date guide https://pve.proxmox.com/pve-docs/pve-admin-guide.html#translation |
Translation Flow
Language files are located in the git.proxmox.com proxmox-i18n git repository, you can download them through the webinterface or clone the whole repository locally using git:
git clone git://git.proxmox.com/git/proxmox-i18n.git
You can then create new translation with (replace <LANG> with the language ID)
cd proxmox-i18n make init-<LANG>.po
For testing your work in the web-interface you need to translate the PO files to a .js file by invoking script located at same directory. First install all required dependencies for that script, for Ubuntu or Debian based system you would do that with:
apt install perl liblocale-po-perl libjson-perl
Then run the script:
./po2js.pl -t pve xy.po >pve-lang-xy.js
The resulting file pve-lang-xx.js
should be copied to the /usr/share/pve-i18n/
directory on your Proxmox VE server.
How to Edit Translation Files
The translations can be done by using poedit, an easy-to-use editor specialized for PO files.
You can also use a common text editor, for example: vim
, Emacs
or Notepad
.
There is no programming knowledge necessary to translate.
Submitting Updated or New Translations
You can send finished translation to the Proxmox team by either using
- our git email patch work flow, see Developer Documentation#Preparing_Patches
- Note that large patch emails are automatically queued for moderation, so it may take a bit until it shows up.
- the full updated
xy.po
file office(at)proxmox.com email address.
Remember to include a signed contributor license agreement if not already present, see Developer Documentation#Software License and Copyright for details.