openSUSE 13.1: Lots of character encoding issues

English Install/Boot/Login
#21

That was already clear - as soon as OP said that setting locale to 8859-1 works.

What is needed here is exact and precise description of environment. E.g. PuTTY always defaulted to 8-bit code set translation until the latest version 0.63 (and we do not know what version OP has).

Locale set in shell has nothing to do with locale used by terminal program (including Linux tty console) to translate incoming keys into character codes. What happens here is that the latter is effectively set to 8859-1.

To demonstrate:

host:~ # locale
LANG=POSIX
LC_CTYPE=en_US.UTF-8
LC_NUMERIC="POSIX"
LC_TIME="POSIX"
LC_COLLATE="POSIX"
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER="POSIX"
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"
LC_ALL=
host:~/t # touch öäüßÖÄ
host:~/t # ls -l
total 0
-rw-r--r-- 1 root root 0 Apr  1 17:16 ??????
host:~/t #

This PuTTY session with translation set to 8859-1. And if I now change translation to UTF-8 (without even reopen session)

host:~/t # touch öäüßÖÄ
host:~/t # ls -l
total 0
-rw-r--r-- 1 root root 0 Apr  1 17:18 öäüßÖÄ
#22

But only in the Terminal. What bothers me more is the fact that it doesn’t work in all KDE applications.

What I’m wondering is that I can reproduce it immediately on two totally different virtual environments, while none of you (with your physical installations) can’t. Maybe it’s a “virtual” issue?

#23

Huh? I just demonstrated how easy to reproduce it is.

I repeat - you need provide exact step by step description of what you do - how you log in to the system, what program you start. Every key press, every mouse click. So far after three pages it is not even clear what program(s) you use to access your system and whether you do it locally in text console, locally in GUI or remotely from another system.

You keep saying “Console” without explaining what it means (KDE terminal is named Konsole and if you mean Linux text console, why it is capitalized?)

#24

I do not know enough of VM (and this is not in the VM forum). But if you type on the keyboard of the mother system (well, we realy need to know what avidjaar asks for), does the mother system then propagate the key codes, or character codes? And when the last is the case, what character codes?

#25

I already told you what I meant by “Console”. But let’s forget about the Konsole, Terminal, Shell, or whatever you call it. Let us concentrate on the graphical issues.

The steps are really not complicated how I can easily reproduce the problem. Once again:

  • Install openSUSE 13.1 from ISO on Microsoft Hyper-V or VMware Workstation, standard (manual) install with KDE, language U.S. English
  • When it’s done installing, log in as the user you created via your local VM console and open the file manager Dolphin
  • Create a folder with special characters, e.g. öäüß. Create a text file in it, right klick on it and select “move to trash”. It will say “the file or folder xyz does not exist”

I don’t know what else to say here. It’s really that quick and simple to reproduce.

#26

On 2014-04-02 10:56, SheriffHobbes wrote:

> The steps are really not complicated how I can easily reproduce the
> problem. Once again:
>
> - Install openSUSE 13.1 from ISO on Microsoft Hyper-V or VMware
> Workstation, standard (manual) install with KDE, language U.S. English

I use VMware player (which is more of less a reduced version of
workstation), on a Linux host. Works fine.

I have several virtual installs, and I have never seen that issue. But I
do not have a Windows host on which to try and find out if that makes a
difference.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)