Quote:
Originally Posted by S3cret
I'm just reading out the lists in sbot. Im not having a connection between the client and sbot to get the ral string.
|
I see... SBot have already spoiled unicode text in it's memory.
Tnen I have another solution/proposal:
add ability to temporary translate all dispayed chats when some key is pressed and back chat to normal view when this key resumed.
For example:
I see message like this "?@825B" and I know it was some word on Russian ("привет (dunno if all see letters)" = "privet (russian transliteration)" = "hello (english)")
I make translation table for "spoiled cyrillics" and when I press some key, your program converts "?@825B" to "privet" as described in this table.
Of course this make unreadable english words but when I resume key I can see latinics alphabet again.
More information: we can add 176 decimal to each displayed code in range 16-79 decimal for Russian cyrillic without translation table and russian text will displayed in windows-1251 encoding.