From: ng0 <ng0@we.make.ritual.n0.is>
To: Tobias Geerinckx-Rice <me@tobias.gr>,
Vincent Legoll <vincent.legoll@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: translation intermediate files
Date: Thu, 28 Jul 2016 08:37:20 +0000 [thread overview]
Message-ID: <87mvl2p39b.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <3029013f-4c3b-f7a9-d16c-dd34bec4e8c6@tobias.gr>
Tobias Geerinckx-Rice <me@tobias.gr> writes:
> Vincent,
>
> On 27/07/2016 19:42, Vincent Legoll wrote:
>> My bad, I was asking because they appeared after a build, so I thought
>> they were generated...
>
> No, you're (also) right. They're a bit of both.
>
> The English source lines can be auto-updated when building, but the
> translated lines come from hard-working humans at the Translation
> Project, so we can't just .gitignore the whole file.
>
> I'm sure someone will correct me if I'm wrong.
>
> If modified .po files are stopping you from performing certain git
> operations, running ‘git reset --hard’ should get rid of them and touch
> the files so they don't get updated again. Only do this after committing
> any changes you may have made by hand, if any.
>
> Kind regards,
>
> T G-R
>
Yesterday I thought if we chould make it more clear in the manual
developer part what these files are, how to deal with them, where they
originate and that they should not be included in the patches.
There might already be a "translating Guix" section, so we could just
extend that and add a few lines wrapped around the link. I can imagine
it to be in the 8.3 (?) section where you are advised to check things
before sending in the patch.
This applies to any model we might or might not adapt in the future,
wether email or not, the translation files will be there and some people
might not know what to do with them.
--
♥Ⓐ ng0
Current Keys: https://we.make.ritual.n0.is/ng0.txt
For non-prism friendly talk find me on http://www.psyced.org
next prev parent reply other threads:[~2016-07-28 8:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 17:25 translation intermediate files Vincent Legoll
2016-07-27 17:35 ` Tobias Geerinckx-Rice
2016-07-27 17:42 ` Vincent Legoll
2016-07-27 17:53 ` Tobias Geerinckx-Rice
2016-07-28 8:37 ` ng0 [this message]
2016-07-28 8:44 ` Vincent Legoll
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=87mvl2p39b.fsf@we.make.ritual.n0.is \
--to=ng0@we.make.ritual.n0.is \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
--cc=vincent.legoll@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).