unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: me@tobias.gr, 51259@debbugs.gnu.org, leo@famulari.name
Subject: bug#51259: Cannot build Guix from source (error messages about the translations)
Date: Mon, 18 Oct 2021 08:57:34 -0400	[thread overview]
Message-ID: <9A2AACA6-D952-46B2-A618-3547CCBCD7AA@lepiller.eu> (raw)
In-Reply-To: <8735oybl41.fsf@nckx>

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

I managed to reproduce the issue on fedora, in a broken pure environmert. In a pure environment, fedora gives error messages about software that doesn't exist, and asks if I want to install them. If I ^C at that point, I enter the environment, but some things are missing.

There are litteral ?? in manuals that don't use ascii, and this is especially visible in the korean manual. Po4a works fine in my experimentation, but it looks like the po parser or regular expression matching is broken at the POXREF phase, and everything is copied as literal ??.

Maybe setting LANG to a UTF-8 locale in the poxref rule would help? It didn't hix the issue in my case, but I think that's because I'm missing even more variables.

Le 18 octobre 2021 07:54:08 GMT-04:00, Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org> a écrit :
>Leo Famulari 写道:
>> ./doc/guix.ko.texi:431: here is the previous definition as @node
>> ./doc/guix.ko.texi:2065: @node `??????' previously defined
>
>This seems to hint at a locale error, and indeed it was: when I 
>check out a fresh guix.git and build it in a recent ‘guix 
>environment guix’ on Guix System, I get the same error as you.
>
>When I repeat the exact same steps but first set
>
>   $ export LC_ALL=en_IE.utf8
>
>in the environment, the build goes swimmingly.
>
>I only ran each test once so it could be a coincidence, but I 
>doubt it.
>
>As for the actual error…
>
>> ./doc/guix.ko.texi:431: here is the previous definition as @node
>> ./doc/guix.ko.texi:2065: @node `??????' previously defined
>
>At the risk of being naive: could it simply be that the missing 
>locale turns the Korean UTF-8 into a literal ‘??????’, which of 
>course matches another mangled @node string of the same length?
>
>Kind regards,
>
>T G-R

[-- Attachment #2: Type: text/html, Size: 2381 bytes --]

  reply	other threads:[~2021-10-18 13:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18  4:01 bug#51259: Cannot build Guix from source (error messages about the translations) Leo Famulari
2021-10-18 11:23 ` Julien Lepiller
2021-10-18 14:37   ` Leo Famulari
2021-10-18 11:54 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-10-18 12:57   ` Julien Lepiller [this message]
2021-10-19  8:18 ` Simon Streit
2021-10-19  9:59   ` Simon Streit
2021-10-19 10:29     ` Raphaël Mélotte
2021-10-20  2:06       ` Julien Lepiller
2021-10-20 10:40         ` Raphaël Mélotte
2021-10-20 11:12           ` Julien Lepiller
2021-10-20 12:11           ` Julien Lepiller
2021-10-20 14:20             ` Raphaël Mélotte
2021-10-22  0:37             ` Julien Lepiller
2021-10-19 22:45               ` bug#51294: Error/bug: bootstrapping a new guix source tree jgart via Bug reports for GNU Guix
2021-10-20  2:04                 ` Julien Lepiller
2021-10-20  2:07                   ` Julien Lepiller
2021-10-20  2:34                     ` jgart via Bug reports for GNU Guix
     [not found]                 ` <handler.51294.D51259.163486307231239.notifdone@debbugs.gnu.org>
2021-10-22  0:57                   ` bug#51294: closed (Re: bug#51259: Cannot build Guix from source (error messages about the translations)) jgart via Bug reports for GNU Guix
2021-10-22  9:23                     ` zimoun
2021-10-19 21:35 ` bug#51259: Cannot build Guix from source (error messages about the translations) Ricardo Wurmus
2021-10-20 15:44 ` Denis 'GNUtoo' Carikli
2021-10-20 15:52   ` Julien Lepiller
2021-10-20 23:36     ` Denis 'GNUtoo' Carikli
2021-10-20 15:57   ` Tobias Geerinckx-Rice via Bug reports for GNU Guix

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=9A2AACA6-D952-46B2-A618-3547CCBCD7AA@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=51259@debbugs.gnu.org \
    --cc=leo@famulari.name \
    --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).