> well, I do think that it should be done by a higher level toolkit. Like in > windows.... > > Please remember that shift9 means open braces, and shift0 means close them.
Yes, and if XFree 4.3 fixed the keymap, it's very simple to fix in Qt. I'll just remove the hack I introduced to fix XFrees broken keyboard mapping. > How they are represented on screen is another thing. X is doing something > that before qt did. I actually bereave the bidi should be rendered inside X > and not gtk or qt. I don't think so. You cannot do complex text rendering inside the server. This is more or less impossible without making things unusably slow. It would still work for Hebrew, but for arabic it has to break (and would be hopeless for indic languages). The problem here is, that the client has to know about font metrics. These change according to string context, so you'd have to query the server for font metrics of every string you want to render, leading to one server roundtrip for each string. It would take 10-100 times as long to render strings than it does today. Anyways, it's not related to the keyboard problem. That one is easy to solve. Search for Q_WS_X11 in qtextedit.cpp and qlineedit.cpp in the Qt sources, and remove the #ifdef'd part where the comment says something about a broken keyboard layout on X11. > > > there were practically no negative comments (to my surprise. I didn't > > > like this proposed change, and was looking for such comments!) I'm all for this change, as it'll allow me to remove that stupid hack in Qt for X11 (which btw could easily fail in some situations). Cheers, Lars ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
