public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Claudio Ferreira <filhocf@gmail.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] Flow for i18n
Date: Wed, 18 Aug 2021 07:46:54 -0300	[thread overview]
Message-ID: <CAC=mJXf1GtqFYWiUb6Euu6xW8zB2YSNLkQxGhm82z5susr1Gww@mail.gmail.com> (raw)

Hi for all

My name is Claudio and I did some translations for many open source
projects, and I want to help in ProxMox for Brazilian Portuguese (pt-BR)
language. I saw your docs for translators and tried to understand your flow
for i18n. It is simple using gettext, but without a tool for optimization,
if I saw correctly.

In some project translations, like Debian Handbook, they use Weblate[1], a
web translation system developed by a Debian Developer, just to help open
source projects to have an easy system to maintain your translations, so I
think that ProxMox could use it too.

Weblate have integration with git, so you can integrate it with your
repository. You maintain the original po/pot file(s) and publish in git.
Import to weblate (via git), generate lang files or import the existing
files, and translation volunteers enter in weblate and fastly translate
your respective files. After, reimport (as a PR) in your git.

What do you think? Is interesting for Promox project use a tool to turn
more easy maintain i18n flow?

Regards,
Claudio Ferreira


             reply	other threads:[~2021-08-18 10:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18 10:46 Claudio Ferreira [this message]
2021-08-19  4:51 Dietmar Maurer
2021-08-19 11:42 ` Claudio Ferreira
2021-08-19 18:28   ` Claudio Ferreira
2021-08-20 21:16     ` Claudio Ferreira

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAC=mJXf1GtqFYWiUb6Euu6xW8zB2YSNLkQxGhm82z5susr1Gww@mail.gmail.com' \
    --to=filhocf@gmail.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal