unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Miguel Ángel Arruga Vivas" <rosen644835@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org
Subject: Re: Fixing Zabbix db-secret-file documentation.
Date: Mon, 09 Nov 2020 12:54:54 +0100	[thread overview]
Message-ID: <87v9eebv8x.fsf@gmail.com> (raw)
In-Reply-To: <874klzv381.fsf@nckx> (Tobias Geerinckx-Rice's message of "Mon, 09 Nov 2020 00:27:42 +0100")

[-- Attachment #1: Type: text/plain, Size: 2244 bytes --]

Hi!

Tobias Geerinckx-Rice <me@tobias.gr> writes:
> Miguel,
>
> Thank you, and everyone else, for all your translation efforts. I've
> translated before.  It's ruddy hard work.

You're welcome, and thank you too: we had nothing to translate if nobody
pushed changes to make Guix even more awesome than it currently is. :-)

> Miguel Ángel Arruga Vivas 写道:
>> Tobias Geerinckx-Rice <me@tobias.gr> writes:
>> Just for the record, I'm glad to translate that change or whatever
>> comes
>> next, but it makes me a bit sad when that effort is reduced to a
>> number,
>
> I'm not reducing your effort to a number, quite the opposite: I meant
> that keeping the old wording ‘just because it's already been
> translated’ would be doing so.

No problem, I understood, but my point really was that it isn't a
problem because "it's already been translated" but because "it triggers
again a procedure which was already taking place".

> Nobody actually suggested that, and I'm very happy that you're both
> willing and able to translate new strings so late.  I wasn't expecting
> that.

I try to maintain the translation up to date, as I'd like to keep "info
guix.es" as close as possible to a fully translated "info guix" (quite
hard to do though, and not really an option with our current flow), so
for me it actually means just one change in my working PO file, but that
isn't usually the case for everybody.

> Let me know what needs to happen if there's still time!

I guess that pushing another tarball to TP isn't the path we're going to
take as I feel it will cause more friction on that side, but surely we
could do it, even only sending one for the manual is a possibility
there.  On the other hand, removing that phrase is an editorial change
that perhaps could be done at project level instead of at TP: querying
the translators directly how to remove the old bits from their
translation may be an option for this.  The last option (that I don't
like neither, but it isn't on my hand to take a final decision) is to
keep the release as it is: it wouldn't affect the manual shown by the
installation, but it'll be lost as soon as a pull is performed.

WDYT?

Happy hacking!
Miguel

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 658 bytes --]

      reply	other threads:[~2020-11-09 11:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-06 13:29 Fixing Zabbix db-secret-file documentation Tobias Geerinckx-Rice
2020-11-07 12:19 ` Oleg Pykhalov
2020-11-07 12:47   ` Tobias Geerinckx-Rice
2020-11-08  0:48     ` Miguel Ángel Arruga Vivas
2020-11-08 23:27       ` Tobias Geerinckx-Rice
2020-11-09 11:54         ` Miguel Ángel Arruga Vivas [this message]

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=87v9eebv8x.fsf@gmail.com \
    --to=rosen644835@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=me@tobias.gr \
    /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).