[pve-devel] [PATCH v3 docs 03/10] Overhaul Translation

Thomas Lamprecht t.lamprecht at proxmox.com
Fri Feb 7 17:27:54 CET 2020


On 2/5/20 3:16 PM, Aaron Lauterer wrote:
> improve phrasing
> 
> Signed-off-by: Aaron Lauterer <a.lauterer at proxmox.com>
> ---
> v2 -> v3:
> rebased on current master
> 
> v1 -> v2:
> applied suggestion from oguz [0]
> 
> [0] https://pve.proxmox.com/pipermail/pve-devel/2019-September/038952.html
> 
> translation.adoc | 37 +++++++++++++++++++------------------
>  1 file changed, 19 insertions(+), 18 deletions(-)
> 
> diff --git a/translation.adoc b/translation.adoc
> index ff99296..cf627f1 100644
> --- a/translation.adoc
> +++ b/translation.adoc
> @@ -6,24 +6,25 @@ ifdef::wiki[]
>  endif::wiki[]
>  
>  
> -A lot of users speak a language other than English and we depend on contributions
> -to make {pve} available to users all over the world.
> -We are always happy to welcome new localizers and invite you to help shape
> -{pve}.
> +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.
>  
> -Our language files are available as https://git.proxmox.com/?p=proxmox-i18n.git[git repository].
> -If you are familiar with git we would be glad to see your contribution according
> -to our {webwiki-url}Developer_Documentation[Developer Documentation].
> +The language files are available as a
> +https://git.proxmox.com/?p=proxmox-i18n.git[git repository]. If you are familiar
> +with git, please contribute according to our
> +{webwiki-url}Developer_Documentation[Developer Documentation].
>  
> -Nonetheless, translating does not require special technical skills.
> -You can get the language files without setting up a development environment
> -https://git.proxmox.com/?p=proxmox-i18n.git;a=tree[here].
> -Right click on the "raw" link of your language and choose "Save Link As...".
> -Do not hesitate to send your translation directly to office(at)proxmox.com with
> -your signed {webwiki-url}Developer_Documentation#Software_License_and_Copyright[contributor license agreement].
> +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

you replace the previous "...", which asciidoc knows to translate to ellipsis in
the respective rendering output[0], with the unicode code point for horizontal
ellipsis (U+2026) plus a zero width space (U+200B). asciidoc doesn't includes
the word "ascii" in it's name by chance ;-P As long as it's avoidable I'd like
to "keep it ASCII", for some things that isn't always possible (say, if we need
to reference to a name in a foreign language which requires unicode character
for sensible spelling) but for ellipsis it is. And zero width space shouldn't
be required at all.

[0]: https://www.methods.co.nz/asciidoc/chunked/ch10.html#_replacements

> +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] to translate {pve}.
> -As a result, the actual translation task is to write a translation of the
> -`msgid` into the `msgstr` below it.
> -Tools like https://poedit.net/[Poedit] make this process more convenient,
> -especially for contributors who are not programmers.
> +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.
> 





More information about the pve-devel mailing list