Bystroushaak

> Are any attempts were made to make some (maybe very slow) implementation over JVM? There were some in the history, but I think that none was really successfully finished....

> What is your native language? Czech language. > Which characters do you need apart from ASCII? "á", "é", "ě", "í", "ó", "ú", "ů", "ý", "č", "ď", "ň", "ř", "š",...

I've offered to pay ~$500 to one C++ programmer I know to implement Xlib unicode input. He looked at Self and played with it for a while, but then decided,...

I will have to look how is input handled. I suspect, that there may be just some condition that prevents input of any character that self doesn't understand. In the...

> To do this right shouldn't we transition to a utf8 string type - detach traits string from traits byteVector and make it standalone to handle multibyte characters etc? That...

I've managed to trace the input into the `traits abstractUI2Event editorKeyCapComboHandler`, where is code for handling the input like `handlePressWithNoModifiers: combo IfCannot: b`, which is limited only to *printable* characters...

I've played with Self again today and managed to trace the input handling into the: - `traits abstractUI2Event editorKeyCapComboHandler` where is `handlePressWithNoModifiers: combo IfCannot: b` This may be updated to...

I was thinking about implementing translation table for keysyms in Self, but decided I will try to do it in C++ Xlib code, because I don't want to replicate functionality,...

I've tried that, but nope, not related. I am kinda confused by that random output, which looks like it maybe reads pieces of memory which it shouldn't.

I've made some progress and it is almost working now, except when the combining / dead key is pressed with shift.