|
|
| (4 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| == Version 5.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 |
|
| |
|
| == Version 4.x ==
| | 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. |
|
| |
|
| Language files are located at git repository:
| | == How to Edit Translation Files == |
| [https://git.proxmox.com/?p=pve-manager.git;a=tree;f=po;h=d5a14531b7b572c0c79c3a70aafa8a3fac933dd4;hb=HEAD git.proxmox.com pve-manager]
| |
|
| |
|
| * You can create new translation by coping messages.pot template file to new file named according your language code. Then use some gettext translation tool like Poedit, Lokalize, Gtranslator.
| | The translations can be done by using [http://www.poedit.net/ poedit], an easy-to-use editor specialized for PO files. |
| * Po file need to be translated to .js file by invoking script located at same directory:
| |
| <pre>./po2js.pl xx.po >pve-lang-xx.js</pre>
| |
|
| |
|
| * You need to have installed some perl packages in your system. For Ubuntu:
| | You can also use a common text editor, for example: <code>vim</code>, <code>Emacs</code> or <code>Notepad</code>. |
| <pre>apt-get install perl liblocale-po-perl libjson-perl</pre> | |
|
| |
|
| * Resulted file '''pve-lang-xx.js''' copy to directory '''/usr/share/pve-manager/locale''' on your proxmox server.
| | There is no programming knowledge necessary to translate. |
| Then you need to add your new language to '''/usr/share/pve-manager/ext4/pvemanagerlib.js''' to '''language_map''' array and logout and login back to server web administration interface to reload available language list.
| |
|
| |
|
| * You can send finished translation to proxmox team to office(at)proxmox.com with signed contributor licence agreement. See [[Developer Documentation]]
| | == Submitting Updated or New Translations == |
|
| |
|
| == Version 3.x ==
| | 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. |
|
| |
|
| Language files are located at git repository:
| | Remember to include a signed contributor license agreement if not already present, see [[Developer Documentation#Software License and Copyright]] for details. |
| [https://git.proxmox.com/?p=pve-manager.git;a=tree;f=po;h=d5a14531b7b572c0c79c3a70aafa8a3fac933dd4;hb=HEAD git.proxmox.com pve-manager]
| |
| | |
| * You can create new translation by coping messages.pot template file to new file named according your language code. Then use some gettext translation tool like Poedit, Lokalize, Gtranslator.
| |
| * Po file can be translated to .js file by invoking script located at same directory:
| |
| <pre>./po_po2js.pl lang.po>lang.js</pre>
| |
| | |
| * You need to have installed perl packaged in your system:
| |
| <pre>apt-get install perl liblocale-po-perl libjson-perl</pre>
| |
| | |
| * Resulted file lang.js move directory /usr/share/pve-manager/root on your proxmox server.
| |
| Then you need to add your new language to /usr/share/pve-manager/ext4/pvemanagerlib.js to language_map array and logout and login back to server web administration interface to reload refresh available language list.
| |
| | |
| * You can send finished translation to proxmox team to office(at)proxmox.com
| |
| | |
| Proxmox VE 2.x management interface is also available in the following languages.
| |
| | |
| === Basque ===
| |
| *Maintainer: Xabier Isla
| |
| *Email: garapen(at)uharte.com
| |
| *Web: [http://www.uharte.com Uharte]
| |
| | |
| == Version 1.x ==
| |
| | |
| Proxmox VE 1.x management interface is available in the following languages.
| |
| | |
| Where should the '''po''' files (or the compiled '''mo''' files) be placed?
| |
| | |
| ===English===
| |
| *Maintainer: Proxmox support team
| |
| *Email: support(at)proxmox.com
| |
| *Web: [http://www.proxmox.com Proxmox]
| |
| | |
| ===German===
| |
| *Maintainer: Proxmox support team
| |
| *Email: support(at)proxmox.com
| |
| *Web: [http://www.proxmox.com Proxmox]
| |
| | |
| ===French===
| |
| *Maintainer: Yacine Kheddache
| |
| *Email: support(at)alyseo.com
| |
| *Web: [http://www.alyseo.com Alyseo]
| |
| | |
| ===Italian===
| |
| *Maintainer: Angelo Volpato
| |
| *Email: angelov72(at)yahoo.it
| |
| | |
| ===Hungarian===
| |
| *Maintainer: Pongracz Istvan
| |
| *Email: pongracz.istvan(at)startit.hu
| |
| *Web: [http://www.startit.hu StartIT]
| |
| | |
| ===Dutch===
| |
| *Maintainer: Erwin de Brueijs
| |
| *Email: erwin(at)123xs.com
| |
| *Web: [http://www.123xs.com 123xs]
| |
| | |
| ===Romanian===
| |
| *Maintainer: Nick Tiloi
| |
| *Email: nick.tiloi(at)gmail.com
| |
| *Web: [http://www.magica.ro MagicaIT]
| |
|
| |
| ===Spanish===
| |
| *Maintainer: Fabio Vasco Gomes
| |
| *Email: fvasco(at)gmail.com
| |
| *Web:
| |
| | |
| ===Portuguese===
| |
| *Maintainer: Bruno Cacheira
| |
| *Email: bruno.cacheira(at)neoscopio.com
| |
| *Web: [http://www.neoscopio.com Neoscopio]
| |
| | |
| ===Portuguese (br)===
| |
| *Maintainer: Fabio Vasco Gomes
| |
| *Email: fvasco(at)gmail.com
| |
| *Web:
| |
| | |
| ===Russian===
| |
| *Maintainer: Antipov Dima
| |
| *Email: tdcmystere(at)gmail.com
| |
| *Web: [http://www.streamhost.biz Streamhost]
| |
| | |
| ===Turkish===
| |
| *Maintainer: Sukru Emre Erim
| |
| *Email: emre(at)medyabim.com
| |
| *Web: [http://www.medyabim.com.tr Medyabim]
| |
| | |
| ===Czech===
| |
| *Maintainer: Chronos
| |
| *Email: robie(at)centrum.cz
| |
| *Web:
| |
| | |
| ===Japanese===
| |
| *Maintainer: Koichi MATSUMOTO
| |
| *Email: mzch(at)me.com
| |
| *Web: [http://maccoterie.com MacCoterie]
| |
| | |
| == How to translate into different languages ==
| |
| 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 ==
| |
| 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]
| |
|
| |
|
| [[Category: HOWTO]] | | [[Category: HOWTO]] |
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.
