From: karl@freefriends.org (Karl Berry)
To: ludo@gnu.org
Cc: guix-devel@gnu.org, bug-gsrc@gnu.org
Subject: Re: Translation of package descriptions and synopses
Date: Wed, 9 Oct 2013 21:48:00 GMT [thread overview]
Message-ID: <201310092148.r99Lm0tP004327@freefriends.org> (raw)
In-Reply-To: <87iox6wy1q.fsf@gnu.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 634 bytes --]
œôòùd have to make
sure Guix can have .po files in the end
I believe that is what you'll get with GNUN (the web translators). What
I imagine is that you would be getting the .po from www instead of tp,
with no other difference in the process.
We'll have to talk with Ineiev about the details. Before that I have to
put the pkgdescrs (which, BTW, I'm tempted to rename to "blurbs", which
seems somehow more descriptive than "descriptions") into www so there is
something tangible to talk about. And before that I want to review the
text. And before that I want to finish getting through today's email.
More later,
Karl
next prev parent reply other threads:[~2013-10-09 21:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 20:52 Synchronizing descriptions with GSRC? Ludovic Courtès
2013-07-10 21:28 ` Brandon Invergo
2013-07-10 22:03 ` Ludovic Courtès
2013-07-15 21:44 ` Brandon Invergo
2013-07-15 22:45 ` Nikita Karetnikov
2013-07-16 14:06 ` Ludovic Courtès
2013-07-16 22:54 ` Nikita Karetnikov
2013-10-08 21:44 ` Brandon Invergo
2013-10-08 22:16 ` Karl Berry
2013-10-09 10:14 ` Translation of package descriptions and synopses Ludovic Courtès
2013-10-09 21:48 ` Karl Berry [this message]
2013-10-08 21:45 ` Synchronizing descriptions with GSRC? Brandon Invergo
2013-10-09 11:19 ` Ludovic Courtès
2013-10-09 13:55 ` Brandon Invergo
2013-10-09 14:21 ` 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=201310092148.r99Lm0tP004327@freefriends.org \
--to=karl@freefriends.org \
--cc=bug-gsrc@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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).