unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Andréas Livet" <andreas@livet.me>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 36180@debbugs.gnu.org
Subject: bug#36180: Problem with non ASCII chars in Libreoffice and zsh on foreign distro
Date: Thu, 13 Jun 2019 14:11:27 +0200	[thread overview]
Message-ID: <53b3272d-0f0a-b005-9a92-05e977bb91d3@livet.me> (raw)
In-Reply-To: <878su59am7.fsf@gnu.org>

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


Hello Ludo,

Thanks for your reply !

> Did you install ‘glibc-locales’ and set ‘GUIX_LOCPATH’ as explained in:
>
>    https://gnu.org/software/guix/manual/en/html_node/Application-Setup.html#Locales
>
> ?
Yes
> You must make sure ‘GUIX_LOCPATH’ is defined in the environment of
> LibreOffice and zsh.

Good catch for Libreoffice, I didn't thought about that since I use to 
open LO files with Thunar (it raise an other question : how to set 
GUIX_LOCPATH for applications that I do not from command line, but it's 
not related to guix).

But for zsh, `GUIX_LOCPATH` was already setted.

Each time I type a non ASCII letter, eg `é` it display : 
`<ffffffff><ffffffff>`

> Do you see any locale-related warnings?
I had those warnings but fix them with instructions given in 
https://issues.guix.info/issue/36074
> Thanks for reporting the issue!

And thank for taking tare of it ! :D

Andréas


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

  reply	other threads:[~2019-06-13 12:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-12 13:49 bug#36180: Problem with non ASCII chars in Libreoffice and zsh on foreign distro Andréas Livet
2019-06-13  8:02 ` Ludovic Courtès
2019-06-13 12:11   ` Andréas Livet [this message]
2019-06-13 12:35     ` Andréas Livet
2019-06-14 17:24       ` Andreas Enge
2019-06-14 21:18       ` Ludovic Courtès
2019-06-15 12:58         ` Andréas Livet
2019-06-14 11:16     ` 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

  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=53b3272d-0f0a-b005-9a92-05e977bb91d3@livet.me \
    --to=andreas@livet.me \
    --cc=36180@debbugs.gnu.org \
    --cc=ludo@gnu.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 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).