Bug 103788 - input of arbitrary unicode characters as defined in ISO 14755
Summary: input of arbitrary unicode characters as defined in ISO 14755
Status: RESOLVED UPSTREAM
Alias: None
Product: kdelibs
Classification: Unclassified
Component: qt (show other bugs)
Version: unspecified
Platform: Mandrake RPMs Linux
: NOR wishlist with 293 votes (vote)
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
: 187263 231823 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-04-13 13:31 UTC by Helge Hielscher
Modified: 2015-11-15 12:01 UTC (History)
11 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 Helge Hielscher 2005-04-13 13:31:03 UTC
Version:            (using KDE KDE 3.3.2)
Installed from:    Mandrake RPMs

please support the input of arbitrary unicode characters as defined in ISO 14755
http://www.cl.cam.ac.uk/~mgk25/volatile/ISO-14755.pdf
Comment 1 Thiago Macieira 2005-04-13 23:58:42 UTC
I think this is more of a Qt issue.
Comment 2 Nicolas Goutte 2005-09-10 16:03:16 UTC
You probably should report the wish to qt-bugs (at) trolltech.com

Have a nice day!
Comment 3 Helge Hielscher 2007-02-20 10:54:35 UTC
reported upstream:
Task 150387 - It would be useful to have full support of unicode characters as defined in ISO 14755.
http://www.trolltech.com/developer/task-tracker/index_html?id=150387&method=entry
Comment 4 Daniel Aleksandersen 2007-07-22 08:46:05 UTC
*** This bug has been confirmed by popular vote. ***
Comment 5 Daniel Aleksandersen 2007-07-22 08:47:16 UTC
GTK+2—and even Windows XP—supports this.
Comment 6 Helge Hielscher 2008-07-15 12:33:52 UTC
upstream:
Task 71224 - Qt/X11 does not allow input of Unicode characters using Ctrl+Shift followed by the character code
http://trolltech.com/developer/task-tracker/index_html?id=71224&method=entry
Comment 7 Dotan Cohen 2009-10-13 13:26:40 UTC
*** Bug 187263 has been marked as a duplicate of this bug. ***
Comment 8 Christoph Feck 2009-12-09 22:53:52 UTC
http://bugreports.qt.nokia.com/browse/QTBUG-8
Comment 9 Dotan Cohen 2010-02-23 21:37:37 UTC
The Qt devs conclude this:
"This seems like a feature that should belong in the window-system and/or input-method, not in each toolkit."

Therefore, Qt won't "fix" it and are passing he ball back to KDE.
Comment 10 Andreas Pakulat 2010-02-23 22:31:03 UTC
No they didn't, they actually moved it further upstream, i.e. X11 or the input-method you're using (scim or uim for example).
Comment 11 Dotan Cohen 2010-02-24 00:01:56 UTC
Where do you see that, Andreas? Here is the Qt bug:
http://bugreports.qt.nokia.com/browse/QTBUG-8

I see no mention of X11 or scim/uim. The bug was resolved CLOSED as a feature request because the bug assignee does not think that it is a Qt issue.

If this really was pushed further upstream, please link to the upstream bugs. Thanks.
Comment 12 Andreas Pakulat 2010-02-24 08:51:24 UTC
(In reply to comment #11)
> Where do you see that, Andreas? Here is the Qt bug:
> http://bugreports.qt.nokia.com/browse/QTBUG-8
> 
> I see no mention of X11 or scim/uim.

"windows-system" is clearly X11 for linux, note this is not the same as 'window-manager'. In particular the window-manager has nothing to do with typing any kind of text. Additionally the assignee mentioned "input-method" which scim/uim are.

> The bug was resolved CLOSED as a feature
> request because the bug assignee does not think that it is a Qt issue.

Right, the assignee thinks it should be done in the input-method or the window-system and not the Qt toolkit. Both are further "up" on the stack, while KDE is down on the software stack (compared to Qt).

> If this really was pushed further upstream, please link to the upstream bugs.

Unfortunately I can't as the assignee didn't mention any bugreport he opened, apparently their policy on how to handle such things is differently than KDE's. Hence somebody who wants this feature will have to go to x.org and file a new request with them.
Comment 13 Dotan Cohen 2010-02-25 09:29:05 UTC
Thank you Andreas. Here is the Xorg bug:
https://bugs.freedesktop.org/show_bug.cgi?id=26747

Please comment there and correct my report if there are any errors. I am not a developer, but of course I want the report to be accurate.
Comment 14 Christoph Feck 2010-03-23 12:57:01 UTC
*** Bug 231823 has been marked as a duplicate of this bug. ***
Comment 15 Arran 2015-02-17 08:37:28 UTC
I can not accept these responses. It works with Ubuntu. So it can well be done in KDE too. This shoving around a very important convenience from one to each other is really one of the reasons that Linux has real problems to become really popular. 

That it is considered as important can be seen in Comment 4:
« *** This bug has been confirmed by popular vote. *** »

I do indeed hope, it can be attributed to somebody who is ready to try to solve it.
Comment 16 Navid Zamani 2015-02-17 12:58:07 UTC
Well, the thing is: This is not some company that we paid for, neither do they necessarily want to.
But instead, the source is open and free from the Content Mafia, and everybody can change things himself, or hire somebody or whatever.

It’s another way of thinking that people who still think in the Microsoft/Apple box (like pretty much all Ubuntu and iDevice people, and far too many from Mozilla and the Plasma team) don’t seem to (want to[?]) get.

It’s not *that* expensive to hire some developers. :)
Many companies do it. Which is how most important open-source projects survive currently AFAIK.

If we have a genuine need (spoiler: we do), and there’s enough people (seems like it), we could start a micro-Kickstarter or bounty on some other site, share the costs, and tell our favourite developers about it. :)

I, personally, have given up on KDE, and “desktop” environments, applications, widget sets, window managers, etc in general, have seen the iDevicelikes and WhatWG cancers, and moved in a quite different direction, developing a very different user environment, primarily for me (and happily me alone), as I write this. So I’m out.

But if you want, go ahead and set a bounty. :)

(I wish bug trackers generally offered a bounty feature. :)
Comment 17 Arran 2015-04-01 16:30:49 UTC
How would I do that?
How expensive would that be? Any thoughts? Are we speaking in hunderds, thousends or more?