unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>, vincent@cloutier.co
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Translating package descriptions
Date: Mon, 28 Mar 2016 18:29:21 +0200	[thread overview]
Message-ID: <8760w6sh0e.fsf_-_@gnu.org> (raw)
In-Reply-To: <87lh539k6d.fsf@gmail.com> (Chris Marusich's message of "Sun, 27 Mar 2016 23:43:38 -0700")

Chris Marusich <cmmarusich@gmail.com> skribis:

> Ben Woodcroft <b.woodcroft@uq.edu.au> writes:
>
>>     5) I speak fluent French, can I add a description and summary in
>>     French?
>>     
>>
>> I'm not sure on this sorry.
>
> I think Guix uses GNU Gettext [1] to localize strings, including those
> used in package descriptions, but I don't know very much about it.
> Since Ludo has committed over 80% of the commits involving the guix/po
> directory, he's probably the one who can answer your questions about how
> to add a translation.

Translations are handled by the Translation Project; all I do is to
commit the updates we receive.  :-)

  http://translationproject.org/domain/guix-packages.html

Vincent, if you’d like to help with the translation of package
descriptions and synopses, please see:

  http://translationproject.org/html/translators.html

We need more people on this, so your help would be most welcome!

Thanks,
Ludo’.

  reply	other threads:[~2016-03-28 16:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-26 22:49 On my way to my first patch, need review vincent
2016-03-27 20:29 ` rain1
2016-03-28  0:37   ` vincent
2016-03-28  6:47     ` Ricardo Wurmus
2016-03-28  5:11 ` Ben Woodcroft
2016-03-28  6:43   ` Chris Marusich
2016-03-28 16:29     ` Ludovic Courtès [this message]
2016-03-30 16:01       ` Translating package descriptions vincent
2016-03-30 21:30         ` 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=8760w6sh0e.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=cmmarusich@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=vincent@cloutier.co \
    /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).