Bug 362967

Summary:	Cannot input Japanese as a name of brush preset tag (3.0 beta git 25ecbaf)
Product:	[Applications] krita	Reporter:	tokiedian <lamentisimo>
Component:	Resource Management	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED WAITINGFORINFO
Severity:	normal	CC:	brunodepaulak, halla
Priority:	NOR
Version:	2.9
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:

Description tokiedian 2016-05-12 05:03:21 UTC

I found that I cannot input 2-byte characters with a keyboard to the box of "New tag" and "Rename tag" in the list of brush preset. https://bugs.kde.org/attachment.cgi?id=98322 It is possible to paste a word which contains 2-byte characters into these boxes.

Reproducible: Always

Comment 1 tokiedian 2016-05-12 05:33:43 UTC

I also found that I cannot rename tags that contains 2-byte characters, which results in two tag of one which is left not renamed and the other which has a name of word that I use to rename the tag.

Comment 2 Halla Rempt 2016-05-12 10:10:55 UTC

Not a regression then.

Comment 3 Halla Rempt 2016-05-14 10:37:43 UTC

I'm marking bugs that also occur in 2.9 as 2.9, focusing on real regressions first.

Comment 4 Bruno P. Kinoshita 2017-06-01 10:11:09 UTC

I can reproduce the bug. I had a Python project to reproduce it with PyQt5, but spent some time building a C++ project to both learn and have a better example to report a bug to Qt.

Here's the bug reported: https://bugreports.qt.io/browse/QTBUG-61152

And here's a simplified project, that creates similar objects, to have a popup menu where the input is always set to English, not matter the input keyboard settings.

https://github.com/kinow/qt-japanese-submenu

Hope that helps!
Bruno

Comment 5 Halla Rempt 2017-06-06 08:54:56 UTC

I wonder whether there's anything left for us to do with this -- I don't think we can fix this in Krita?

Comment 6 Bruno P. Kinoshita 2017-06-06 09:38:15 UTC

I do not think so Boudewijn. I tried changing the objects, changing the parents, but nothing that really fixed the bug. If I moved the QLineEdit out of the action, and left it always being displayed, it would work. But I think Qt does something else when it creates the widget for the QPushButton, and it loses track of the locale. Sounds more like a bug somewhere deep down in Qt.

I'm watching the QTBUG-61152, but so far it receives only minor edits, which were changes of assignees or further categorization. I'll update this issue in case the issue is confirmed in Qt or if they suggest an alternative to be implemented in Krita.

Bruno

Comment 7 Halla Rempt 2017-06-06 09:48:27 UTC

OKay, in the meantime we can mark this bug as WAITINGFORINFO then -- to avoid cluttering up bugzilla with things we cannot take action on.