Translations: Difference between revisions

From Proxmox VE
Jump to navigation Jump to search
No edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
== Version 6.x ==
{{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}}


Language files are located at git repository:
== Translation Flow ==
[https://git.proxmox.com/?p=proxmox-i18n.git;a=tree git.proxmox.com pve-i18n]


* You can create new translation with (replace <LANG> with the language ID)
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:


  # cd proxmox-i18n
  git clone git://git.proxmox.com/git/proxmox-i18n.git
# make init-<LANG>.po


* Po file need to be translated to .js file by invoking script located at same directory:
You can then create new translation with (replace <LANG> with the language ID)
<pre>./po2js.pl -t pve xx.po >pve-lang-xx.js</pre>


* You need to have installed some perl packages in your system. For Ubuntu:
cd proxmox-i18n
<pre>apt-get install perl liblocale-po-perl libjson-perl</pre>
make init-<LANG>.po


* Resulted file '''pve-lang-xx.js''' copy to directory '''/usr/share/pve-i18n''' on your proxmox server.
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


* You can send finished translation to proxmox team to office(at)proxmox.com with signed contributor licence agreement. See [[Developer Documentation]]
Then run the script:
./po2js.pl -t pve xy.po >pve-lang-xy.js


Proxmox VE 6.x management interface is available in the following languages.
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.


* Arabic (ar)
== How to Edit Translation Files ==
* Catalan (ca)
* Danish (da)
* German (de)
* English (en)
* Spanish (es)
* Euskera (Basque) (eu)
* Persian (Farsi) (fa)
* French (fr)
* Hebrew (he)
* Italian (it)
* Japanese (ja)
* Norwegian (Bokmal) (nb)
* Norwegian (Nynorsk) (nn)
* Polish (pl)
* Portuguese (Brazil) (pt_BR)
* Russian (ru)
* Slovenian (sl)
* Swedish (sv)
* Turkish (tr)
* Chinese (Simplified) (zh_CN)
* Chinese (Traditional) (zh_TW)


Note that most of above translations are contributed by users and English is the original language the interface is written in.
The translations can be done by using [http://www.poedit.net/ poedit], an easy-to-use editor specialized for PO files.
Our contributors try their best to translate it in the languages they know themselves, thus, at time of writing, German, Italian, Turkish and French have good translations.


== How to translate into different languages ==
You can also use a common text editor, for example: <code>vim</code>, <code>Emacs</code> or <code>Notepad</code>.
The translations can be done by using [http://www.poedit.net/ poedit], an easy to use editor or any other editor you prefer, e.g. Emacs. There is no programming knowledge necessary to translate. If you want to translate, just contact office(at)proxmox.com.


== PO files ==
There is no programming knowledge necessary to translate.
All released translation file are available. All maintainers can pick these file if the translation needs rework.


* [ftp://download.proxmox.com/sources/po-files/ Proxmox VE translations]
== 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

Yellowpin.svg 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

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.