Translations: Difference between revisions

From Proxmox VE
Jump to navigation Jump to search
No edit summary
 
(19 intermediate revisions by 10 users not shown)
Line 1: Line 1:
=Available languages=
{{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}}
Proxmox VE management interface is available in the following languages.


Where should the '''po''' files (or the compiled '''mo''' files) be placed?
== Translation Flow ==


==English==
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:
*Maintainer: Proxmox support team
*Email: support(at)proxmox.com
*Web: [http://www.proxmox.com Proxmox]


==German==
git clone git://git.proxmox.com/git/proxmox-i18n.git
*Maintainer: Proxmox support team
*Email: support(at)proxmox.com
*Web: [http://www.proxmox.com Proxmox]


==French==
You can then create new translation with (replace <LANG> with the language ID)
*Maintainer: Yacine Kheddache
*Email: support(at)alyseo.com
*Web: [http://www.alyseo.com Alyseo]


==Italian==
cd proxmox-i18n
*Maintainer: Angelo Volpato
make init-<LANG>.po
*Email: angelov72(at)yahoo.it


==Hungarian==
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.
*Maintainer: Pongracz Istvan
First install all required dependencies for that script, for Ubuntu or Debian based system you would do that with:
*Email: pongracz.istvan(at)startit.hu
apt install perl liblocale-po-perl libjson-perl
*Web: [http://www.startit.hu StartIT]


==Dutch==
Then run the script:
*Maintainer: Erwin de Brueijs
./po2js.pl -t pve xy.po >pve-lang-xy.js
*Email: erwin(at)123xs.com
*Web: [http://www.123xs.com 123xs]


==Romanian==
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.
*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==
== How to Edit Translation Files ==
*Maintainer: Bruno Cacheira
*Email: bruno.cacheira(at)neoscopio.com
*Web: [http://www.neoscopio.com Neoscopio]


==Portuguese (br)==
The translations can be done by using [http://www.poedit.net/ poedit], an easy-to-use editor specialized for PO files.
*Maintainer: Fabio Vasco Gomes
*Email: fvasco(at)gmail.com
*Web:


==Russian==
You can also use a common text editor, for example: <code>vim</code>, <code>Emacs</code> or <code>Notepad</code>.
*Maintainer: Antipov Dima
*Email: tdcmystere(at)gmail.com
*Web: [http://www.streamhost.biz Streamhost]


==Turkish==
There is no programming knowledge necessary to translate.
*Maintainer: Sukru Emre Erim
*Email: emre(at)medyabim.com
*Web: [http://www.medyabim.com.tr Medyabim]


==Czech==
== Submitting Updated or New Translations ==
*Maintainer: Chronos
*Email: robie(at)centrum.cz
*Web:


==Japanese==
You can send finished translation to the Proxmox team by either using
*Maintainer: Koichi MATSUMOTO
* our git email patch work flow, see [[Developer Documentation#Preparing_Patches|Developer Documentation#Preparing_Patches]]
*Email: mzch(at)me.com
: Note that large patch emails are automatically queued for moderation, so it may take a bit until it shows up.
*Web: [http://maccoterie.com MacCoterie]
* the full updated <code>xy.po</code> file office(at)proxmox.com email address.


=HowTo translate to different languages=
Remember to include a signed contributor license agreement if not already present, see [[Developer Documentation#Software License and Copyright]] for details.
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://pve.proxmox.com/sources/po-files/ Proxmox VE translations]


[[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.