[pve-devel] Can Proxmox use Weblate? (Was: Re: [PATCH i18n 1/1] Currently translated at 98.2% (1800 of 1832 strings))

Claudio Ferreira filhocf at gmail.com
Sat Aug 28 02:11:11 CEST 2021


Em sex., 27 de ago. de 2021 às 11:08, Thomas Lamprecht <
t.lamprecht at proxmox.com> escreveu:

> I am a bit wary of such tool, as they are centralized and often just not as
> simple as a plain text editor or POEdit, but that aside, for German or
> Italian
> I actually like to ensure that the translation fits and that's not always
> true
> for Proxmox VE if one is taking a, possible too generic, translation from a
> big translation pool.
>

I understand your POV, Thomas, but it is also interesting to find people
that start a translation as his need. I'm an example of this filosofy.  I
started software translation for my needs and have already translated more
than 10 open source projects for my language. In places like Weblate,
generally have people from open source communities and when they see an
interesting project, start his contribution translating and, according to
his skills, help in other places too. In my case, unhappily, is translation
and (very) small things in code.


> That depends on preference, I'm very used to VIM and I'm nowhere as fast as
> there, also learning the knacks of yet another web-tool, even if easy seems
> a bit weird to me - especially as this is just editing text; but to each
> their own.
>

Lol! I am also a fan of vim. About tools, who are translating have more
options and tools using Weblate. An example is that when I use poEdit, I
see both strings, original and in my language (or space to fill with). In
Weblate, I can see other languages (in my case, french, spanish and
galician, plus the original in english), that in some cases (galician by
example) is the same string. In this case, I can only copy from one of
these languages. Another example is to understand the context, that in some
cases, can be more of one translation (word with multiple meanings). Some
translator have already done a research and found a better meaning.

While I can see some benefits of using a central translation site, i.e.,
> mostly
> the bigger exposure that comes with it, I (and here I'm speaking a bit
> with my
> PVE project lead hat on) like to keep it simple and flexible in terms of
> tool
> choice.


I understand and respect it. I'm speaking about this because I wait to
continue helping in the project and wait more yet to be more productive
posible. I understand that each project have its flow and, in some
cases, don't know about other tools. And I think that a good talk about
translation can be healthy for us.


> The extraction and update tools are not necessary for most translator, as
> we
> frequently commit an update of the extracted PO files anyway.
>

This is exactly what the flow requires.

I'm also very flexible in how to take a translation, some frequent
> translators
> of Chinese (both, Traditional and Simplified) just send me the whole
> updated
> PO file and I check it, look over the changes to ensure no format mistake
> or
> the like happened and commit that for them, works quite good in general
> from
> my experience.
>

You can do it too, without problem. Have some languages in the Debian
Handbook project that do it. Generally a solitaire guy... with poEdit. In
Brazilian Portuguese, for example, there were 10 people translating
intensively. So, we builded a glossary (also provided by tool) and some
guidelines to do this work. I couldn't translate all the strings because
there are many strings that aren't common for me. I need a lot more of use
of Proxmox to see better translation for.


> Thanks for your thoughts about that topic, I'll certainly try to take a
> closer
> look at weblate. But, if we add it to our workflow I'd like to only
> include it
> as optional way, keeping the extremely simple "download PO edit with any
> text
> editor" way.


I agree! Thank you for your time and disposition to talk about. I think
that this can be the first step, the interface. I am already seeing how to
translate the PVE docs using po4a to get po files, and after to use weblate
to translate all documentation.

Regards,
Claudio Ferreira



More information about the pve-devel mailing list