[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: hack: arabic/vnc on linux client

It's actually still an issue. What I presented was a hack. But the xkb extension still doesn't work over vnc, whether linux or windows.

Let me rephrase: when using vnc, the characters that appear on the remote machine are always taken from the local machine's keymap. Changing the keymap on the remote machine isn't supported. So what I did was run kxkb on the local machine (RH9) and switch keyboard maps using it while accessing the remote machine (FC1). This is a workaround. The xkb extension needs to be supported on vnc.

And since it looks like you're looking for issues to work on, :) neither xmms nor Realplayer 9 (on FC1) handle Arabic paths properly. RP9 for Linux is a community project. While xmms can traverse the directories but displays them as gibberish, RP can't even open a file if Arabic is in the path.


Moustafa Mounir Elqabbany مصطفى منير القباني
(The above message uses Unicode (UTF-8) encoding.)

Munzir Taha wrote:

On Sunday 07 December 2003 11:16, Moustafa Mounir Elqabbany مصطفى منير القباني wrote:

Assalamu alaikum.

As a follow-up to my previous question, I found that if the client
running vnc is also running X and I switch the kbd layout to be Arabic
on the local machine, it will type Arabic on the remote machine.  So,
until there's a way around it, you can start kxkb on the local machine
and Alt-Tab between it and a full-screen vnc session of the remote
machine to switch input languages.  It's a clumsy hack, but it works.

(This still doesn't answer my original question because it was regarding
a vnc client on Windows.)

Since X is available with linux then there is no problem in linux, right?. The problem is in Windows then. Please Mustafa, confirm Arabic with vnc in linux works and I haven't misunderstood you so I can remove this from my own pending issues.