Hi,

Pablo Saratxaga a �crit :
> I'm a bit surprized by that... aren't all keysyms between 0x01000000
> and 0x0100ffff valid unicode values ? and as such, aren't all of
> them encodable in utf-8 ?

Yes that's what I was guessing...
And that's what the old xterm code does...

> 
> If yes, how could it be possible that Xutf8LookupString() returns 0 ?
> (and apparently, it is the case that some valid unicode values don't
> return utf-8 strings, I've the case with 0x1000020 to 0x100007f for
> example; they should return the same thing as keysyms 0x20 to 0x7f,
> but they don't)
> 
> Isn't that a bug in itself ?

That's why I have posted my message.
But later I have checked the XFree86 CVS tree and I've found
that the code for full UTF-8 support is present.
I don't know if that code is already present in the version which
I'm using now (4.1.0.1). A least it doesn't work for me.

(I've tryed to compile the XFree86 source, but I've stopped it 
because it takes me too much time. I will wait the next release of
Debian, SuSE or Mandrake to see if the UTF-8 code works.)
 
 
> Korean also has a problem, as the Hangul_* keysyms should return the
> equivalent utf-8 strings, shouldn't it ?

I think that the CVS version will do it because there is a nice
KeySyms to Unicode translation table.
 
 
> > > This XIM server will use the Yudit tables to enter any Unicode
> > > character using an normal US keyboard. (It will be released under
> > > the GPL).
> 
> yudit also has the ability to use traditionnal XIMs (like kinput, xcin, etc)
> and XKB, trough a very simple configuration (giving two parameters,
> the name of the XIM (value for XMODIFIERS="@im=xxxx") and the value of the
> lcoale to use when connecting with that XIM.
> Then a simple menu allows selecting any of the various input methods
> defined, either yudit "native" tables, either X server input methods.
> 
> It would be wonderful if an XIM with similar features existed (that is,
> not only using the yudit tables, but also the ability to easily switch on
> the fly to any X input method), that would solve what is imho currently
> the biggest problem of XFree86 (and one of the most frustrating, as now
> there is UTF-8 support but it's not possible to fully take advantage of
> it for the input)

Very good idea. But I don't know if calling a XIM from a XIM is
possible. I will check that.

(Note that InterXim seems to be unstable yet. It makes sometimes 
the user application crash if it is killed. Unfortunately I'm not able
make this append on my computers... )

Regards,
        Jean-Marc

-- 
mailto:[EMAIL PROTECTED]
http://www.oksid.ch
_______________________________________________
I18n mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/i18n

Reply via email to