From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id E955968B7D for ; Fri, 28 Aug 2020 11:34:54 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D4C981FCC2 for ; Fri, 28 Aug 2020 11:34:24 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [212.186.127.180]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id A92C01FCB4 for ; Fri, 28 Aug 2020 11:34:23 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 79D7143EE1 for ; Fri, 28 Aug 2020 11:34:23 +0200 (CEST) To: Proxmox VE development discussion , Dylan Whyte References: <20200828082503.11773-1-d.whyte@proxmox.com> From: Thomas Lamprecht Message-ID: <96dcc670-57f3-8902-6c1e-7852526e8841@proxmox.com> Date: Fri, 28 Aug 2020 11:34:17 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:80.0) Gecko/20100101 Thunderbird/80.0 MIME-Version: 1.0 In-Reply-To: <20200828082503.11773-1-d.whyte@proxmox.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.791 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_SHORT 0.001 Use of a URL Shortener for very short URL NICE_REPLY_A -1.782 Looks like a legit reply (A) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com, gnu.org, po2js.pl, poedit.net] Subject: Re: [pve-devel] [PATCH pve-docs] translation: combine old and current wikis X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2020 09:34:55 -0000 Please switch over your mails "To" address from the old to the new On 8/28/20 10:25 AM, Dylan Whyte wrote: > This takes all of the relevant information from > an old wiki site (https://pve.proxmox.com/wiki/Translations) > and merges it into the document that is used in generating the > admin guide and current wiki > (https://pve.proxmox.com/wiki/Translating_Proxmox_VE) entry. > > Also contains some rewording for better readability. > > Signed-off-by: Dylan Whyte > --- > translation.adoc | 50 +++++++++++++++++++++++++++++++++++++++--------- > 1 file changed, 41 insertions(+), 9 deletions(-) > > diff --git a/translation.adoc b/translation.adoc > index 2dc156b..fcb0f99 100644 > --- a/translation.adoc > +++ b/translation.adoc > @@ -6,10 +6,10 @@ ifdef::wiki[] > endif::wiki[] > > > -The {pve} user interface is in English by default. Thanks to contributions by > -the community, translations to other languages are available. We welcome help to > -add new languages, translate the newest features, and improve incomplete or > -inconsistent translations. > +The {pve} user interface is in English by default. However, thanks to the > +contributions of the community, translations to other languages are also available. > +We welcome any support in adding new languages, translating the latest features, and > +improving incomplete or inconsistent translations. > > The language files are available as a > https://git.proxmox.com/?p=proxmox-i18n.git[git repository]. If you are familiar > @@ -17,14 +17,46 @@ with git, please contribute according to our > {webwiki-url}Developer_Documentation[Developer Documentation]. > > Even if you are not familiar with git, you can help with translating {pve}. > -Download the language files > -https://git.proxmox.com/?p=proxmox-i18n.git;a=tree[here]. Then choose the > -language you want to improve. Right click on the "raw" link of this language > -file, and select 'Save Link As...'. Make your changes to the file, and then why isn't the "How to Translate" heading here? I mean, the whole sections reads a bit strange to me, maybe we want to group this in two how-to sections. "How to Translate simple" and "How to Translate with git clone" (better titles obviously needed ^^) > +To start, you can download the language files > +https://git.proxmox.com/?p=proxmox-i18n.git;a=tree[here]. Find the > +language you want to improve, then right click on the "raw" link of this language > +file and select 'Save Link As...'. Make your changes to the file, and then > send your final translation directly to office(at)proxmox.com together with a > signed > {webwiki-url}Developer_Documentation#Software_License_and_Copyright[contributor license agreement]. > > We use https://www.gnu.org/software/gettext/[gettext] for the management of the > translation files. Tools like https://poedit.net/[Poedit] offer a nice user > -interface to edit the translation files. > +interface to edit the translation files, but you can use whatever editor you're > +comfortable with. No programming knowledge is required for translating. > + > + > +How to Translate > +~~~~~~~~~~~~~~~~ > + > +After cloning the git repository, you can create a new translation by doing the > +following (replace with the language ID): > + > + # cd proxmox-i18n > + # make init-.po > + > +Or you can edit an existing translation, using the editor of your choice: > + > + # poedit .po > + > +The po file must be translated to a .js file by invoking the script located in > +the same directory: > + This step is a bit confusing, it lacks a reason, i.e., something like "If you want to try your changes, you can either build a deb package, or apply them manually by translating the po file to a .js..." > + # ./po2js.pl -t pve xx.po >pve-lang-xx.js > + > +IMPORTANT: For this to work, you need to have the following perl packages installed > +on your system. For Debian/Ubuntu: > + > + # apt-get install perl liblocale-po-perl libjson-perl > + > +The resulting file 'pve-lang-xx.js' can then be copied to the directory > +'/usr/share/pve-i18n', on your proxmox server, in order to test it out. > + > +You can send the finished translation to the proxmox team at the address > +office(at)proxmox.com, along with a signed contributor licence agreement. > +See [[Developer Documentation]] > Maybe add something like: "Alternatively, if you have some developer experience you can send them also as patch to the development mailing list."