From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org,zimoun <zimon.toutoune@gmail.com>
Subject: Re: Release v1.2 and Translation
Date: Fri, 09 Oct 2020 08:04:37 -0400 [thread overview]
Message-ID: <FD812947-EAA0-4F56-A907-744036FA82DB@lepiller.eu> (raw)
In-Reply-To: <867drz92hq.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1855 bytes --]
If you're not an emacs user, poedit is a very good tool. I personally use offlate, my own tool, for the translations. It's especially useful for interacting with the translation platform (here the TP but I support others). Both tools are available in guix.
Le 9 octobre 2020 05:23:45 GMT-04:00, zimoun <zimon.toutoune@gmail.com> a écrit :
>Dear Translators,
>
>The target for the release v1.2 is Oct. 29th.
>
>The POT files have been updated if I read correctly. Since there are
>new materials or revamped ones, help is needed. :-)
>
>Well Guixer, if you would like to contribute and do not know how,
>translation is a really good mean. Fix typos, bad wording, new
>translations, etc. Do not hesitate to raise your hand if you need
>help to start.
>
>
>Currently, an .po entry looks like…
>
>--8<---------------cut here---------------start------------->8---
>#. type: Plain text
>#: doc/contributing.texi:58
>msgid "The easiest way to set up a development environment for Guix is,
>of course, by using Guix! The following command starts a new shell
>where all the dependencies and appropriate environment variables are
>set up to hack on Guix:"
>msgstr "La manière la plus simple de configurer un environnement de
>développement pour Guix est, bien sûr, d'utiliser Guix ! La commande
>suivante démarre un nouveau shell où toutes les dépendances et les
>variables d'environnements appropriées sont configurés pour travailler
>sur Guix :"
>--8<---------------cut here---------------end--------------->8---
>
>…here translated, but sometimes untranslated ones ’msgstr ""’. Tooling
>helps to manipulate such files. For example:
>
> guix environment --ad-hoc emacs gettext \
> -- emacs path/to/file.po
>
>And I am sure non-Emacs users have good other tools.
>
>
>Happy translation :-)
>simon
[-- Attachment #2: Type: text/html, Size: 2142 bytes --]
next prev parent reply other threads:[~2020-10-09 12:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 9:23 Release v1.2 and Translation zimoun
2020-10-09 12:04 ` Julien Lepiller [this message]
2020-10-11 19:20 ` Miguel Ángel Arruga Vivas
2020-10-12 12:28 ` Ludovic Courtès
2020-10-12 13:05 ` zimoun
2020-10-12 16:15 ` Miguel Ángel Arruga Vivas
2020-10-12 19:49 ` zimoun
2020-10-12 21:26 ` Miguel Ángel Arruga Vivas
2020-10-19 16:23 ` zimoun
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=FD812947-EAA0-4F56-A907-744036FA82DB@lepiller.eu \
--to=julien@lepiller.eu \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.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.
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).