Version: (using KDE KDE 3.4.0) Installed from: Mac OS X (Fink) Packages Compiler: gcc 4, Mac OSX 10.4.1 I have installed Kbabel for the first time on Mac OSX 10.4.1, using fink. I was really pleased to be able to install it, since I translate for various OSS projects, including KDE. :) Kbabel crashed twice, while I was setting up the main prefs. Each time I pressed "Apply", it disappeared. I had to restart it. The fatal bug for me is that it won't input my Vietnamese Unicode accented letters. This is done using "dead" keys for the accents: Kbabel just inputs a space for each dead key, instead of inputting the accent. I can't translate without being able to input translations! Two earlier bugs, the Arabic and Danish one, sound similar. In each case you queried fonts. I tried several different Unicode fonts, and the problem in Kbabel is the same with all of them (all my OSX apps. work fine). I have my X11 prefs set up to grab input from my Unicode keyboards. I'm using the unstable version of Kbabel, from source, since there was no binary available, and the new fink database for OSX 10.4.1 is pretty sparse as yet. Other severe problems: I can't cut, copy or paste *into or out* of Kbabel. The X11 menu reacts when I use the keyboard shorcuts, but I can only copy or paste *within* Kbabel by using the menu commands: the keyboard shortcuts do nothing. There is no Translation Database in the Settings -> Dictionary menu. The Kbabel manual says it's there. Kbabel crashes at odd times when I press different buttons. The Bug Reporter does nothing! I can't even get started, since I can't input anything, so I can't really give you much information ... except that Kbabel is unusable for me, since I can't input translations. :( I am really disappointed. :( I'll have to try Gtranslator after all. from Clytie, unhappy.
Can you type accented characters using deadkeys in any other KDE application? How about Qt-only applications? Do the other problems you mentioned also happen in other KDE applications?
I would be interested too to know if it would be a KBabel-only bug. I have tested (however on Linux with X11) and found that dead keys are working. So the problems are probably more due to the port to MacOS. Just another question: you get spaces immediately when you type in the accent, not that the spaces appears after the characters after you have enter the character. (From what I know Vietnamese needs to use Unicode accents, as not all letters exist as such in Unicode. So if you get spaces after the character, it would be this problem instead and not unrecognized dead keys.) Have a nice day!
It does look like a X11 OSX bug, and it's not just Kbabel, since it affects KWrite too. I haven't got any reaction from the Mac OSX Hints X11 forum yet. I've found Unicode display problems are not common experience: I've generally had to solve them myself in the past. :( Since I don't have the know-how to solve this one, I'll have to give up on using Kbabel, which is really annoying, since I translate for OSS, including KDE. :( The spaces appear immediately I type the dead key, not after typing the dead key and the vowel together. Yes, Vietnamese certainly needs Unicode, and is in fact a test case for Unicode support, having combined diacritics. I really hope I get some help with this one, but I'm not holding my breath. :( from Clytie
Let's try kdelibs for tracking this. But it was always hard to get input right for Vietnamese.
Can you see if this affects Qt-only applications as well? How about non-Qt applications?
Vietnamese is a test case for Unicode support, but if it were only a Vietnamese-specific matter, I would be getting _some_ input, maybe not all accents working, but here I have _no_ accented input at all. I think that has to be a X11 issue, but so far I can't get any help with getting X11 on Mac OSX set up to handle dead-key input. I've done everything the manual says, and it should work, but it doesn't. :( I don't think it's a Qt issue, unless Qt is different in X11: in the Mac OSX GUI, I use Qt Linguist and Psi (Qt app.) all the time, and Vietnamese input and display are perfect in those two apps. What could I run in X11 that would not be a Qt app, if you still want that checked? I just don't have the experience in X11 on Mac OSX. I've asked questions on the Mac OSX Hints forums, but nobody's answering. I may have to look for help elsewhere. More searching. :( I just want to get on with my translations. from Clytie, grouchy
I don't know what you have available, but pure X programs like xterm or emacs should present a nice testcase. Also, those pure Qt programs you're talking about, are they using the X11 server? Please make sure they do.
xterm has the same input problem, that's why I think it must be X11. I even went and joined the xfree86 mailing list to ask some questions, but it hasn't sent the auto-confirm yet. I really needsome help with this. I don't know if my Mac GUI Qt programs will run under X: probably not. I could try running their Unix versions, perhaps... I'll ask about it. from Clytie, lost
Mac OSX packages are in no way main stream I'm afraid
I don't know where to take this. I tried the Mac OSX Hints X11 forum, even joined the Xfree86 list, posted in detail on both of them and have received only a deafening silence... :( I'll keep searching, and hope I can resolve this and bring the info back to you, in case anyone else has the same problem. <sigh> from Clytie
Is this still relevant to recent KDE version? If not please close the bug. Thanks, Lex.
(In reply to comment #11) > Is this still relevant to recent KDE version? > If not please close the bug. Doesn't seem to be. Original reporter please reopen if you can still confirm.