unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Benno Schulenberg <coordinator@translationproject.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Benno Schulenberg <coordinator@translationproject.org>,
	guix-devel@gnu.org, web-translators@gnu.org
Subject: Re: Coordinating package meta-data translation
Date: Sun, 08 Jun 2014 10:30:59 +0200	[thread overview]
Message-ID: <53941F43.90600@translationproject.org> (raw)
In-Reply-To: <87k38tiwiv.fsf@gnu.org>


Hello Ludovic,

On 2014-06-06 23:00, Ludovic Courtès wrote:
> The GNU distribution provided by Guix contains package synopses 
> and descriptions that we would like to translate (see [0] to get 
> an idea.)

When I first looked at the POT file of guix, about a year ago, I
found it odd that it contained descriptions of some of the packages
that it could install.  To me those descriptions would seem not to
be part of the tool, but part of the things that the tool works on.
So I would have expected them to be in a different POT file, or in
some package database, but not in the POT file of guix.

> For GNU packages, synopses and descriptions are kept in sync with 
> files from the GNU womb, which are in turn used to generate a web 
> page [1]. Translation of this web page is already handled by the 
> www.gnu.org translators.

So these blurbs (package descriptions) are already being translated
into different languages?  Well, then it is clear: remove those
blurbs from the guix POT file, and, if you need them in guix, import
them from the web-translating effort.  If you wish instead the blurbs
to be translated at the TP, then make them into a separate POT file,
say guix-blurbs, not a part of the main guix POT file.  Any existing
translations I can import into the TP.

> Thus, some synchronization would be needed between the TP and the 
> www translators.
> 
> Any idea/preference on how to proceed?

As will be clear from the above, I would not want to synchronize but
draw a strict dividing line: decide who should translate what, and
use those translations everywhere where the strings occur.

> (Note that the distro also contains synopses and descriptions for
>  non-GNU packages, which are *not* translated elsewhere.)

Ehm... which distro do you mean?  Or did you mean to say "any distro"
or "most distros"?

Regards,

Benno

  reply	other threads:[~2014-06-08  8:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06 21:00 Coordinating package meta-data translation Ludovic Courtès
2014-06-08  8:30 ` Benno Schulenberg [this message]
2014-06-08 22:07   ` Ludovic Courtès
2014-06-12 20:14     ` Benno Schulenberg
2014-06-12 21:49       ` Ludovic Courtès
2014-06-14 15:52         ` Benno Schulenberg
2014-06-13 15:38       ` Ludovic Courtès
2014-06-14 15:49         ` Benno Schulenberg
2014-06-14 20:57           ` Ludovic Courtès
2014-06-15 20:10             ` Benno Schulenberg
2014-06-16 22:35               ` 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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=53941F43.90600@translationproject.org \
    --to=coordinator@translationproject.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=web-translators@gnu.org \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).