all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: 59205@debbugs.gnu.org
Cc: Julien Lepiller <julien@lepiller.eu>
Subject: bug#59205: ‘guix help’ output is partly untranslated
Date: Fri, 11 Nov 2022 23:24:56 +0100	[thread overview]
Message-ID: <87r0y9ceo7.fsf@inria.fr> (raw)

Saluton!

The output of ‘guix help’ is partly untranslated:

--8<---------------cut here---------------start------------->8---
$ LC_ALL=fr_FR.utf8 guix help | head -20
Utilisation : guix OPTION | COMMANDE ARGS...
Lance la COMMANDE avec les arguments ARGS, le cas échéant.

  -h, --help             afficher de nouveau ce texte d'aide et quitter
  -V, --version          afficher les informations sur la version les droits d'auteur et quitter

COMMANDE doit être une des sous-commandes listées ci-dessous :

  commandes principales
    deploy        deploy operating systems on a set of machines
    describe      describe the channel revisions currently used
    gc            invoke the garbage collector
    home          build and deploy home environments
    install       install packages
    package       manage packages and profiles
    pull          pull the latest revision of Guix
    remove        remove installed packages
    search        search for packages
    show          show information about packages
    system        build and deploy full operating systems
--8<---------------cut here---------------end--------------->8---

The synopses that appear in ‘define-command’ forms are left
untranslated.  They are in ‘guix.pot’ but are missing from PO files.

Any idea?

Thanks,
Ludo’.




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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11 22:24 Ludovic Courtès [this message]
2022-11-12  8:11 ` bug#59205: ‘guix help’ output is partly untranslated Julien Lepiller
2022-11-22  8:54   ` Ludovic Courtès

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=87r0y9ceo7.fsf@inria.fr \
    --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 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.