all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org
Subject: Re: Improving the translation process
Date: Thu, 6 Feb 2020 22:41:04 +0100	[thread overview]
Message-ID: <20200206214104.bxkaqkd2oiyf3npz@pelzflorian.localdomain> (raw)
In-Reply-To: <5C0BF556-0087-41D9-AFF1-A48F3762CC04@lepiller.eu>

I think the Translation Project mailing lists are a good place to
discuss translations and they should be recommended.  I am thankful to
the German TP team’s Mario Blättermann for introducing me to the TP’s
way of working and giving help.  Also it is good to look at the PO
files collection at the TP to see how some word was translated in
other software.

However, this does not mean Guix needs to use the TP services for
translation.  To me, the need to upload a tarball to the TP seems
pointless.  Automated, regular upload of POT files would be very
welcome.

If Guix or Savannah decides on Weblate, the reason should be easier
maintenance for the maintainers, which I cannot comment on.  Opinions
on that would be interesting.

I had never heard of Weblate, so I watched:

https://www.youtube.com/watch?v=IVlXt6QdgdA

Most things I don’t care about.  The speaker talks about non-technical
people not downloading PO files.  I believe Guix translators need
technical knowledge anyway to understand what they translate.  I do
not believe sending emails is a problem for translators.  In my
opinion, downloading PO files is the best way to search, diff and
proofread.  I do not like that Javascript seems to be required to
download and upload PO files via Weblate.  Adding automated checking
for valid Texinfo would in a few cases be helpful, but is really
needed only if Weblate were to commit automatically.

I don’t think full machine translation is useful, in contrast to
machine-aided dictionaries like:

https://www.linguee.com/english-german/translation/proofread.html


Thank you for all your efforts in improving translations!

Regards,
Florian

  parent reply	other threads:[~2020-02-06 21:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06 17:01 Improving the translation process Julien Lepiller
2020-02-06 19:20 ` Julien Lepiller
2020-02-06 21:41 ` pelzflorian (Florian Pelz) [this message]
2020-02-07 13:00   ` Julien Lepiller
2020-02-07 13:46     ` pelzflorian (Florian Pelz)
2020-02-07 21:50 ` Ludovic Courtès
2020-02-09 23:55   ` zimoun
2020-02-10  0:03     ` Julien Lepiller
2020-02-11 14:23       ` Ludovic Courtès
2020-02-11 16:08         ` Julien Lepiller
2020-02-24 16:23           ` Ludovic Courtès

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=20200206214104.bxkaqkd2oiyf3npz@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=guix-devel@gnu.org \
    --cc=julien@lepiller.eu \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.