Posted 07 Feb 2013
Link to this post
Thank you for your reply and let me explain roughly.
For example, let's assume type 'telerik'(텔레릭) in Korean, then actually 3 letters pronounced such as
'tel - re - lik'. When you type 'tel' in english,actually 3 uni code arranged and displays sequentially
in screen but pronounce 1 letter as 'tel',but in korean, first consonant + middle vowel + last consonant(optional)
makes a letter,so 3 typing displays 1 letter pronounced as 'tel'.
Because each of 't','te','tel' has it's own unicode,every key press should listen next chracter
and check if matching unicode exists.
Briefly showing what happens in korean when types 3 letter 'tel - re - lik' in korean '텔레릭',
1.type 't','ㅌ' in korean, screen shows 'ㅌ' in screen.
2.type 'e' in korean 'ㅔ',테'(te) exists in unicode,so screen displays '테'.
3.type 'l' in korean 'ㄹ', '텔'(tel) exists in unicode, so screen displays '텔' with exact 1 letter.
4.type 'r' in korean, screen shows '텔ㄹ'(tel-r) and this letter is not exists in unicode,
so 'r' is incomplete and he becomes the first consonant of next letter 're' and waits next character comes in.
4.type 'e' in korean 'ㅔ', prior incomplete 'r' can make a letter 're'(레),and now screen show 'tel-re'(텔레).
5.type 'r' in korean 'ㄹ'. (l and r is same character in korean).
now screen shows 'tel-rel'(텔렐) not 'tel-re-r'(텔레ㄹ) because 'rel' exists in unicode.
6.type 'i' in korean 'I' vowel. Because no vowel can become first consonant,last 'r'(ㄹ) is changed as
first consonant and joined with 'i',so screen shows 'tel-re-ri'(텔레리).
7.type 'k' in korean 'ㄱ', then last letter 'rik'(릭) completed and screen shows 'tel-re-rik'(텔레릭).
When I type your company name in normal speed in icenium editor,'tel-re-rik' (텔레릭),
it shows '텔ㅔㅣ' (tel-e-i) or '텔ㅣ'(tel-i)' or something else ,differing with typing speed.
I think you can find automata which has korean letter algorithm with googling and can have a better knowledge.
In chinese and japanese, I'm not sure but nearly similar rule exists along with same problem with korean as well.
In your RadRichTextBox at earlier version of SL, similar problem arouses but cleared since mid of last year.
Pls refer follwoing link and read your member's note.
Hope this might be a little help.