all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 33678@debbugs.gnu.org
Subject: bug#33678: Locale problems
Date: Sun, 09 Dec 2018 00:35:54 +0100	[thread overview]
Message-ID: <87sgz74mn9.fsf@gnu.org> (raw)
In-Reply-To: <20181208223551.2ad9c226@scratchpost.org> (Danny Milosavljevic's message of "Sat, 8 Dec 2018 22:35:51 +0100")

Guten Tag!  :-)

Danny Milosavljevic <dannym@scratchpost.org> skribis:

> Can we do something against the locale problems that keep showing up
> when updating?
>
> Right now, after a half-finished update from guix master (half-finished because
> once any package build breaks, the entire update will stop), I cannot use any
> Umlauts because "xterm -u8" stops working as it should:
> $ xterm -u8
> Warning: locale not supported by C library, locale unchanged
> $
>
> Why does this keep happening?  Shouldn't the functional nature and modularity
> of Guix keep using the old locales where those make sense and the new locales
> where those make sense?

Please see:

  https://www.gnu.org/software/guix/manual/en/html_node/Locales.html#Locale-Data-Compatibility-Considerations

The solution, as described in this section, is to have both (say)
locales for glibc 2.27 and locales for glibc 2.28, which you can specify
in ‘locale-libcs’.

Another option is what ‘guix’ commands print every time you run them: to
install the corresponding ‘glibc-utf8-locales’ package.

Now I perfectly understands that this annoys everyone of us when that
happens, and many people don’t seem to find the info.  So I’m open to
suggestions on how to improve this!

Thanks,
Ludo’.

      parent reply	other threads:[~2018-12-08 23:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-08 21:35 bug#33678: Locale problems Danny Milosavljevic
2018-12-08 22:35 ` Danny Milosavljevic
2018-12-08 22:56   ` Marius Bakke
2018-12-08 22:59 ` pelzflorian (Florian Pelz)
2018-12-08 23:35 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sgz74mn9.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=33678@debbugs.gnu.org \
    --cc=dannym@scratchpost.org \
    /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.