From: Claudio Ferreira <filhocf@gmail.com>
To: Dietmar Maurer <dietmar@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] Flow for i18n
Date: Thu, 19 Aug 2021 08:42:13 -0300 [thread overview]
Message-ID: <CAC=mJXe76s0dzSDZHa1pAJXg4YnV+JsxRx6be606ncADr2_bmw@mail.gmail.com> (raw)
In-Reply-To: <66113536.1246.1629348701690@webmail.proxmox.com>
We have some additional tools to maintain a localization in tools like
glossary, common terms, automated translation, copy/paste, other languages
in the same frame (very useful when we do not find a good word), etc.
On the other hand, I'm volunteering to study it and to help in this
process, Dietmar. Since I'm a new user of ProxMox and in its community, I
think first to present myself and ask about how to help. If you haven't
objections, I wait to help with Weblate integration, translate to pt-BR and
help other translators to use this tool.
And, absolutely, I agree with you about new tools, setups and maintenance.
I only suggested it because I saw its value.
Regards,
Claudio Ferreira
Em qui., 19 de ago. de 2021 às 01:52, Dietmar Maurer <dietmar@proxmox.com>
escreveu:
> Isn't it easy enough to edit a po file?
>
> I am not particularly keen to setup and maintain another tool/service.
>
> > On 08/18/2021 12:46 PM Claudio Ferreira <filhocf@gmail.com> wrote:
> >
> >
> > 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
> > _______________________________________________
> > pve-devel mailing list
> > pve-devel@lists.proxmox.com
> > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
>
next prev parent reply other threads:[~2021-08-19 11:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 4:51 Dietmar Maurer
2021-08-19 11:42 ` Claudio Ferreira [this message]
2021-08-19 18:28 ` Claudio Ferreira
2021-08-20 21:16 ` Claudio Ferreira
-- strict thread matches above, loose matches on Subject: below --
2021-08-18 10:46 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=mJXe76s0dzSDZHa1pAJXg4YnV+JsxRx6be606ncADr2_bmw@mail.gmail.com' \
--to=filhocf@gmail.com \
--cc=dietmar@proxmox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.