An problem of IME action in the Chat module.

[Haruhiko MITSUYA]

Hi Developers,

I found an problem in the Chat module.

There is a misbehaving in IME(Input Method Editor) action.

As you know, IME is a helper application of a user's text input.

It handles native key events before or after focused application (depending on the platform)

and creates a composition string, suggests a list of what the user attempts to input,

commits composition string as a selected item off the list and commits composition string

without any conversion. 

(IME is used by Chinese, Japanese, Korean and Taiwan users for inputting Chinese characters

because the number of them is beyond thousands and cannot be input from the keyboard directly.)

 

Typical Japanese IME can input two or more words into a composition string.

When a user converts from Hiragana characters to Chinsese characters the composition string,

Japanese IME separates the composition string into multiple clauses.

When a user presses Convert key (It's a space bar in general.), Japanese IME separates

the composition string as "わたしの" (my), "なまえは" (name is) and "ハリーです" (Harry).

Then, converts each clause with Chinese characters: "私の", "名前は" and "ハリーです".

If one or more clauses were not converted as expected, the user can choose one of the clauses

with Arrow keys and look for the expected result form the list in the drop down menu.

At last, input the "Enter" key to settle a conversion on each words.

# When I was typing Japanese words and converting the first word, Chat user interface sent

the incomplete text in an unintended timing.

It comes into being in Chrome, not in FireFox.

[Chrome, Input IME converting Enter-key]

- keyDOWN : 229

- keyUP : 13(enter)

[Chrome, Input only Enter-key]

- keyDOWN : 13(enter)

- keyPRESS : 13(enter)

- keyUP : 13(enter)

[FireFox, Input IME converting Enter-key]

- keyUP : 13(enter)

[FireFox, Input only Enter-key]

- keyDOWN : 13(enter)

- keyPRESS : 13(enter)

- keyUP : 13(enter)

I think, a chat module of the Big Blue Button is checking a keyDOWN event to send chatting text.

It's a wrong approach for multilingual input editors.

Please make modification before officially launching of ver.0.9.0.

Thanks in advance,

Harry

[Fred Dixon]

Hi Haruhiko,

Thanks for reporting this issue when using BigBlueButton with a Input Method Editor.  We've opened an issue to track it 

  https://code.google.com/p/bigbluebutton/issues/detail?id=1892

We'll be working on fixing this before we move to a release candidate for 0.9.0.  Thanks again for such a (great) detailed explanation.

Regards,... Fred

--
You received this message because you are subscribed to the Google Groups "bigbluebutton-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-u...@googlegroups.com.
To post to this group, send email to bigbluebu...@googlegroups.com.
Visit this group at http://groups.google.com/group/bigbluebutton-users.
For more options, visit https://groups.google.com/d/optout.

--

BigBlueButton Developer

http://bigbluebutton.org/
http://code.google.com/p/bigbluebutton

BigBlueButton on twitter: @bigbluebutton