emacs and other programs do not display special characters

  • Open
  • quality assurance status badge
Details
4 participants
  • Bengt Richter
  • quiliro
  • Ricardo Wurmus
  • Miguel Arruga Vivas
Owner
unassigned
Submitted by
quiliro
Severity
normal
Q
Q
quiliro wrote on 10 Sep 2019 01:27
(address . bug-guix@gnu.org)
fcd8b47e1a9093ed62acca7845113b01.squirrel@sm.riseup.net
Hello Guix:

I am reporting this because there are no other similar cases on the
mailing list and because I think this might be a bug and not my error.

Emacs Magit and Emacs shell don't dispaly special characters (such as ñ,
í, ó) on their output. It is strange because a command that includes a
special character is displayed. But a special character from the output
will not be displayed correcly. Those special characters are displayed
correctly on afairs such as opening a file with those characters.

With 'emacs -Q' I did not have that problem. When copying .emacs.d to
another directory, setting that directory as HOME and running emacs with
'mkdir ~/temp', 'cp ~/.emacs.d ~/temp/' and 'HOME="~/temp" emacs', it
would not use my configurations. But it would not have the problem with
Emacs shell. Emacs Magit would not be available either. The same situation
is with 'emacs -Q' as with 'HOME="~/temp" emacs'.


Sample from BASh displaye correctly:

quiliro@GSD3 ~/magit/prueba0$ git log
commit 0904ec46cb737d2116d59b0b7c4f0c21a74feb70 (HEAD -> master)
Author: quiliro <quiliro+commits@fsfla.org>
Date: Sun Sep 8 15:43:09 2019 -0500

Modificación remota

commit 5024f6d525b1b61cd2691aaaa60dde07ae6f489f (origin/master)
Author: ramiro.ordonez <quiliro+fablab@fsfla.org>
Date: Sun Sep 8 13:20:11 2019 -0500

Añadí a mi amor
quiliro@GSD3 ~/magit/prueba0$


Same command sample from Emacs shell displayed incorrectly:

quiliro@GSD3 ~/magit/prueba0$ git log
WARNING: terminal is not fully functional
- (press RETURN)
commit 0904ec46cb737d2116d59b0b7c4f0c21a74feb70 (HEAD -> master)
Author: quiliro <quiliro+commits@fsfla.org>
Date: Sun Sep 8 15:43:09 2019 -0500

Modificación remota

commit 5024f6d525b1b61cd2691aaaa60dde07ae6f489f (origin/master)
Author: ramiro.ordonez <quiliro+fablab@fsfla.org>
Date: Sun Sep 8 13:20:11 2019 -0500

Añadí a mi amor
quiliro@GSD3 ~/magit/prueba0$


I am not sure if this is related that in Icecat I sometimes see square
boxes with numbers inside them in place of characters. But other special
characters are displayed. That is probably a missing font. It could be a
separate problem.


Happy hacking!
Q
Q
quiliro wrote on 10 Sep 2019 02:13
(address . 37363@debbugs.gnu.org)
5b7a274019a6659a19b1193a154fd6c4.squirrel@sm.riseup.net
As per nckx's question on IRC, this is the output to locale on both Emacs
shell and BASh:

quiliro@GSD3 ~/magit/prueba0$ locale
LANG=es_EC.UTF-8
LC_CTYPE="es_EC.UTF-8"
LC_NUMERIC="es_EC.UTF-8"
LC_TIME="es_EC.UTF-8"
LC_COLLATE="es_EC.UTF-8"
LC_MONETARY="es_EC.UTF-8"
LC_MESSAGES="es_EC.UTF-8"
LC_PAPER="es_EC.UTF-8"
LC_NAME="es_EC.UTF-8"
LC_ADDRESS="es_EC.UTF-8"
LC_TELEPHONE="es_EC.UTF-8"
LC_MEASUREMENT="es_EC.UTF-8"
LC_IDENTIFICATION="es_EC.UTF-8"
LC_ALL=
Q
Q
quiliro wrote on 10 Sep 2019 11:53
(name . 37363)(address . 37363@debbugs.gnu.org)
54101b276c9500b5d28fa5ca4cf1fb56.squirrel@sm.riseup.net
On M-x shell with (locale "es_ES.utf8"):
quiliro@GSD3 ~$ ñ
bash: $'quiliro@GSD3 ~$ ñ
bash: $'\361': command not found\361': command not found
quiliro@GSD3 ~$

Also with (locale "es_ES.utf8"), the system is all in English and Gnome
Terminal will not start:
quiliro@GSD3 ~$ gnome-terminal
# Locale not supported by C library.
# Using the fallback 'C' locale.
# Error constructing proxy for
org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling
StartServiceByName for org.gnome.Terminal:
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
org.gnome.Terminal exited with status 9
quiliro@GSD3 ~$

I have also tested unknown command error output. On Emacs' M-x shell with
(locale "es_EC.UTF-8"):
quiliro@GSD3 ~$ ñ
bash: $'\361': no se encontró la orden
quiliro@GSD3 ~$

On BASh with (locale "es_EC.UTF-8"):
quiliro@GSD3 ~$ ñ
bash: ñ: no se encontró la orden
quiliro@GSD3 ~$

I have tested this with:
guix (GNU Guix) 1d03a9198db6f3656a34d62eb89e5f7d5a99e76a
and with:
guix (GNU Guix) 83aa6562173e06e8fafd4857a2e708feabfe56f8
R
R
Ricardo Wurmus wrote on 10 Sep 2019 18:40
(address . quiliro@riseup.net)(name . 37363)(address . 37363@debbugs.gnu.org)
874l1kqf4k.fsf@elephly.net
quiliro@riseup.net writes:

Toggle quote (6 lines)
> Also with (locale "es_ES.utf8"), the system is all in English and Gnome
> Terminal will not start:
> quiliro@GSD3 ~$ gnome-terminal
> # Locale not supported by C library.
> # Using the fallback 'C' locale.

Do you have “glibc-locales” installed?
Is GUIX_LOCPATH set?

--
Ricardo
B
B
Bengt Richter wrote on 11 Sep 2019 04:15
(address . quiliro@riseup.net)(address . 37363@debbugs.gnu.org)
20190911021503.GA1118@PhantoNv4ArchGx.localdomain
Attachment: file
Q
Q
quiliro wrote on 11 Sep 2019 17:32
(name . 37363)(address . 37363@debbugs.gnu.org)
3607ee9b9427d5d654e27f7dbb56c7b1.squirrel@sm.riseup.net
El Mar, 10 de Septiembre de 2019, 11:40 am, Ricardo Wurmus escribió:
Toggle quote (12 lines)
>
> quiliro@riseup.net writes:
>
>> Also with (locale "es_ES.utf8"), the system is all in English and Gnome
>> Terminal will not start:
>> quiliro@GSD3 ~$ gnome-terminal
>> # Locale not supported by C library.
>> # Using the fallback 'C' locale.
>
> Do you have “glibc-locales” installed?
> Is GUIX_LOCPATH set?

Not on my user. Probably on my system. I did not know I had to add those
on Guix System. Should I?
M
M
Miguel Arruga Vivas wrote on 21 Oct 2019 19:52
20191021195257.1f8b2d83@gmail.com
I'm running on guix and spanish symbols work properly, on emacs and the
terminal.

---
miguel@unfall ~/src/gnu/guix$ locale
LANG=es_ES.utf8
LC_CTYPE="es_ES.utf8"
LC_NUMERIC="es_ES.utf8"
LC_TIME="es_ES.utf8"
LC_COLLATE="es_ES.utf8"
LC_MONETARY="es_ES.utf8"
LC_MESSAGES="es_ES.utf8"
LC_PAPER="es_ES.utf8"
LC_NAME="es_ES.utf8"
LC_ADDRESS="es_ES.utf8"
LC_TELEPHONE="es_ES.utf8"
LC_MEASUREMENT="es_ES.utf8"
LC_IDENTIFICATION="es_ES.utf8"
LC_ALL=
---

I've seen some es_EC localizations instead of es_ES, could
you check that's not your issue?

Best regards,
Miguel
?