unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Luigi Salamone <lg.salamone@gmail.com>
Cc: 61965@debbugs.gnu.org, Julien Lepiller <julien@lepiller.eu>,
	Tobias Geerinckx-Rice <me@tobias.gr>
Subject: bug#61965: Incorrect Italian translation of hints
Date: Fri, 10 Mar 2023 10:03:34 +0100	[thread overview]
Message-ID: <87edpx9dw9.fsf_-_@gnu.org> (raw)
In-Reply-To: <CAMD_u569BYmp_d9n=z1H0GNt-ZN1cgpvFGFxAQ8_9zkJusnimw@mail.gmail.com> (Luigi Salamone's message of "Tue, 7 Mar 2023 20:43:59 +0000")

Hi Luigi,

Luigi Salamone <lg.salamone@gmail.com> skribis:

> Now "guix system search KEYWORD" works! But... guix install hello:
>
> hint: Backtrace: 16 (primitive-load
> "/home/anonymous/.config/guix/current/b…") In guix/ui.scm: 2300:7 15
> (run-guix . _) 2263:10 14 (run-guix-command _ . _) In ice-9/boot-9.scm:
> 1752:10 13 (with-exception-handler _ _ #:unwind? _ # _) In guix/status.scm:
> 851:3 12 (_) 831:4 11 (call-with-status-report _ _) In guix/store.scm:
> 1300:8 10 (call-with-build-handler _ _) 1300:8 9 (call-with-build-handler #
> …) In guix/build/syscalls.scm: 1442:3 8 (_) 1408:4 7
> (call-with-file-lock/no-wait "/var/guix/profiles/per-u…" …) In
> guix/scripts/package.scm: 325:7 6 (build-and-use-profile _
> "/var/guix/profiles/per-user/…" …) In guix/ui.scm: 325:5 5 (display-hint _
> #:port _ . _) 1473:24 4 (texi->plain-text _) In texinfo.scm: 1132:22 3
> (parse _) 967:36 2 (loop # (*fragment*) # …) 92:2 1 (command-spec _) In
> ice-9/boot-9.scm: 1685:16 0 (raise-exception _ #:continuable? _)
> ice-9/boot-9.scm:1685:16: In procedure raise-exception: Throw to key
> `parser-error' with args `(#f "Unknown command" esempio)'.

That’s a similar bug, this time in the ‘guix’ gettext domain.  Julien?

Should we have a “TRANSLATORS” command somewhere explaining that Texinfo
command names (like @example) must not be translated?

More importantly, should we have a tool on our side to validate all the
Texinfo strings that appear in .po files?  I’m not entirely sure how to
do that.

Ludo’.




  parent reply	other threads:[~2023-03-10  9:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-04 15:08 bug#61965: Commands like "guix system search KEYWORD" don't work with locale it_IT.utf8 Luigi Salamone
2023-03-06 22:46 ` Ludovic Courtès
2023-03-07  7:28   ` Julien Lepiller
2023-03-07 20:43   ` Luigi Salamone
2023-03-07 21:27     ` Julien Lepiller
2023-03-10  9:03     ` Ludovic Courtès [this message]
2023-03-10  9:42     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2023-03-10 11:21       ` Julien Lepiller

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=87edpx9dw9.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=61965@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    --cc=lg.salamone@gmail.com \
    --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).