From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>,
Mathieu Othacehe <m.othacehe@gmail.com>,
julien lepiller <roptat@lepiller.eu>
Subject: Re: Update on 1.0.1
Date: Fri, 17 May 2019 11:55:08 +0200 [thread overview]
Message-ID: <20190517095507.d7q7rvykuuzo76ft@pelzflorian.localdomain> (raw)
In-Reply-To: <8736ldzbdp.fsf@gnu.org>
On Fri, May 17, 2019 at 11:19:30AM +0200, Ludovic Courtès wrote:
> Hi Florian,
>
> "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
>
> > Please include this updated German PO file:
> > https://pelzflorian.de/guix-manual.de.po
>
> Applied, thank you!
>
:)
> Perhaps in the future we should use a different workflow if the TP
> doesn’t work well for us. Thoughts?
>
In GNOME string freezes are introduced to give translators enough
time. I guess this is not necessary for Guix; by now the only
unstable part of the manual that is noticeable is the list of
languages in which the manual is available, because the Russian
translation appeared just before release.
Regards,
Florian
next prev parent reply other threads:[~2019-05-17 10:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 15:57 Update on 1.0.1 Ludovic Courtès
2019-05-09 16:35 ` znavko
2019-05-09 17:00 ` Giovanni Biscuolo
2019-05-14 11:57 ` Ludovic Courtès
2019-05-15 10:07 ` Giovanni Biscuolo
2019-05-09 17:45 ` Amin Bandali
2019-05-14 11:57 ` Ludovic Courtès
2019-05-15 13:16 ` Ludovic Courtès
2019-05-15 13:43 ` Mathieu Othacehe
2019-05-16 11:38 ` Ludovic Courtès
2019-05-16 12:13 ` pelzflorian (Florian Pelz)
2019-05-16 12:41 ` Miguel
2019-05-16 12:53 ` pelzflorian (Florian Pelz)
2019-05-16 13:02 ` Miguel
2019-05-16 22:41 ` pelzflorian (Florian Pelz)
2019-05-17 9:19 ` Ludovic Courtès
2019-05-17 9:55 ` pelzflorian (Florian Pelz) [this message]
2019-05-17 9:16 ` Ludovic Courtès
2019-05-17 13:02 ` Ricardo Wurmus
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=20190517095507.d7q7rvykuuzo76ft@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=m.othacehe@gmail.com \
--cc=roptat@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.