unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 59205@debbugs.gnu.org
Subject: bug#59205: ‘guix help’ output is partly untranslated
Date: Tue, 22 Nov 2022 09:54:10 +0100	[thread overview]
Message-ID: <87y1s3gyj1.fsf@gnu.org> (raw)
In-Reply-To: <20221112091135.06692917@sybil.lepiller.eu> (Julien Lepiller's message of "Sat, 12 Nov 2022 09:11:35 +0100")

Hi!

Julien Lepiller <julien@lepiller.eu> skribis:

> The pot generation process for translations at weblate is separate from
> the one for Guix. The pot in Guix is outdated and not updated
> automatically.

Oh.  So if we add a new ‘--keyword’ option (say) to ‘XGETTEXT_OPTIONS’,
it won’t be picked up automatically, right?

How can we improve sharing between these two processes?

> It seems that the rules for generating the pot changed in Guix, but I
> don't use them for generating the pot files in the translation repo.
> That is because I don't want to run configure, make and risk something
> breaking because of an ABI change, just for translations. I updated the
> generation process and ran an update. The pot file in the translation
> repo now has the missing strings and they should appear at weblate in a
> few hours if all goes well :)

Perfect!  Let us know when we can close this bug.

Thank you,
Ludo’.




      reply	other threads:[~2022-11-22  8:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11 22:24 bug#59205: ‘guix help’ output is partly untranslated Ludovic Courtès
2022-11-12  8:11 ` Julien Lepiller
2022-11-22  8:54   ` Ludovic Courtès [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=87y1s3gyj1.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=59205@debbugs.gnu.org \
    --cc=julien@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 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).