Bug 342098 - Non-ASCII characters are not recognized correctly
Summary: Non-ASCII characters are not recognized correctly
Status: RESOLVED WORKSFORME
Alias: None
Product: konsole
Classification: Applications
Component: keyboard (show other bugs)
Version: 2.13.2
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2014-12-21 22:18 UTC by Aleksejs
Modified: 2018-11-11 16:24 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aleksejs 2014-12-21 22:18:48 UTC
I use two keyboard layouts - Latvian QWERTY and Russian Default. After recent update, konsole stopped recognizing symbols from these layout that are not from standard ACSII table. For example, symbol ā or ф.
When I try to enter them in konsole itself, nothing happens. But in programs like weechat I see two question signs "??". It means that symbol is sent but not recognized correctly.
All other software, including native terminal (Ctrl+Alt+F*) does recognize those symbols.
Tried to change encoding to UTF-8 in konsole settings - no effect.
Comment 1 Christoph Feck 2014-12-22 01:26:28 UTC
> After recent update

What did you update, from which version, to which version? This probably is not a Konsole issue.

> All other software

Including all other KDE and pure Qt software?
Comment 2 Aleksejs 2014-12-27 08:36:29 UTC
> Including all other KDE and pure Qt software?
All software I use works without problems, except konsole.

A little bit more info:
When I run locale I get:
$ locale 
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_LV.UTF-8
LANGUAGE=en
LC_CTYPE="en_LV.UTF-8"
LC_NUMERIC=en_LV.UTF-8
LC_TIME=en_LV.UTF-8
LC_COLLATE="en_LV.UTF-8"
LC_MONETARY=en_LV.UTF-8
LC_MESSAGES="en_LV.UTF-8"
LC_PAPER=en_LV.UTF-8
LC_NAME=en_LV.UTF-8
LC_ADDRESS=en_LV.UTF-8
LC_TELEPHONE=en_LV.UTF-8
LC_MEASUREMENT=en_LV.UTF-8
LC_IDENTIFICATION=en_LV.UTF-8
LC_ALL=

And now the same problem is with native terminal.

I tried solutions from this thread http://askubuntu.com/questions/162391/how-do-i-fix-my-locale-issue but nothing helped.
Comment 3 Franky 2015-01-27 08:53:37 UTC
After upgrade to konsole version:

Version 3.0.1
Unter KDE Frameworks 5.6.0

i have the same issue with german umlauts (ÄäÜüÖö) or other special characters (ß). If i type them, only a questionmark appears. Output form programs (like make) throw a color inverted questionmark.

My locale:
$ locale
LANG=de_DE.UTF-8
LC_CTYPE="de_DE.UTF-8"
LC_NUMERIC="de_DE.UTF-8"
LC_TIME="de_DE.UTF-8"
LC_COLLATE=C
LC_MONETARY="de_DE.UTF-8"
LC_MESSAGES="de_DE.UTF-8"
LC_PAPER="de_DE.UTF-8"
LC_NAME="de_DE.UTF-8"
LC_ADDRESS="de_DE.UTF-8"
LC_TELEPHONE="de_DE.UTF-8"
LC_MEASUREMENT="de_DE.UTF-8"
LC_IDENTIFICATION="de_DE.UTF-8"
LC_ALL=
Comment 4 Franky 2015-01-27 12:37:34 UTC
As i even noticed, some of the applications that ported to kf 5 do not support the locale-settings. Here it is

konsole (Version 3.0.1, Unter KDE Frameworks 5.6.0)
qtcreator  (Version3.3.0, Based on Qt 5.4.0)

But kate (Version 5.0.0, Unter KDE Frameworks 5.6.0) works correct...
Comment 5 Franky 2015-01-27 12:46:05 UTC
correction: in qtcreator only the filemanager works incorrect (Folder with "äöüß" aren't shown correct) In the editor the letters appears correct.
Comment 6 Franky 2015-01-28 09:28:07 UTC
I fix this issue for me: Just make a rightclick in konsole window (not the border) and changed the setting "Set Encoding" from "Default" to "Unicode -> UTF-8".

Don't know if it is related: If i start konsole from konsole and change the setting as described, the Terminal output is:

codecForName: ucnv_open failed ISO-8859-16 U_FILE_ACCESS_ERROR

The output is triggered as soon as the mousepointer ran over "Set encoding".
Comment 7 Andrew Crouthamel 2018-10-21 02:39:05 UTC
It sounds like this is resolved? Could Aleksejs or Franky confirm?
Comment 8 Franky 2018-11-11 09:40:39 UTC
I think this is fixed :-)