On 09/04/2011 03:57 PM, jincreator wrote:
> At testing latest version of Unity, I was happy.
> But soon, I agreed with @Koichi.
> I'm Korean user, but I know a little bit about typing Japanese and Chinese.
> Unity can't show and process typing letter(1 CJK letters are typed by several key pressing).
> It looks like Unity has problem to CJK all!
I tested it with the latest version on Oneiric and it works like
expected. The pre-edit stuff appears in the search field, so you can see
what you type.
I tested with ibus-hangul (Korean), ibus-anthy (Japanese) and
ibus-pinyin (Chinese).
The difference you described is the following: in hangul, you compose
the syllables out of letters, like you described. There is no ambiguity,
each syllable is unique. Therefor ibus submits the syllable when it's
complete. Means, either you press Space or Enter to signal that the
syllable is complete, or you start typing a new syllable, where ibus
knows that the last component you typed can't be part of the syllable
you typed before and therefore must be part of a new syllable.
In Japanese and Chinese however, things work differently. Since we type
the pronunciation and each pronunciation can map to multiple characters
(words), we need to choose which characters we want. The input engines
nowadays are smart enough to select the correct characters for whole
sentences, by context search. Therefore we type the complete sentence in
the pre-edit phase and review if the engine has chosen the correct
characters. We can go back with the arrow keys and correct any wrongly
chosen characters.
Only when we are satisfied we submit the whole string with either Enter
or Space, depending on the input method.
Hence, the scenario you described is expected. Nothing wrong with it. :)
Cheers
Arne
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 09/04/2011 03:57 PM, jincreator wrote:
> At testing latest version of Unity, I was happy.
> But soon, I agreed with @Koichi.
> I'm Korean user, but I know a little bit about typing Japanese and Chinese.
> Unity can't show and process typing letter(1 CJK letters are typed by several key pressing).
> It looks like Unity has problem to CJK all!
I tested it with the latest version on Oneiric and it works like
expected. The pre-edit stuff appears in the search field, so you can see
what you type.
I tested with ibus-hangul (Korean), ibus-anthy (Japanese) and
ibus-pinyin (Chinese).
The difference you described is the following: in hangul, you compose
the syllables out of letters, like you described. There is no ambiguity,
each syllable is unique. Therefor ibus submits the syllable when it's
complete. Means, either you press Space or Enter to signal that the
syllable is complete, or you start typing a new syllable, where ibus
knows that the last component you typed can't be part of the syllable
you typed before and therefore must be part of a new syllable.
In Japanese and Chinese however, things work differently. Since we type
the pronunciation and each pronunciation can map to multiple characters
(words), we need to choose which characters we want. The input engines
nowadays are smart enough to select the correct characters for whole
sentences, by context search. Therefore we type the complete sentence in
the pre-edit phase and review if the engine has chosen the correct
characters. We can go back with the arrow keys and correct any wrongly
chosen characters.
Only when we are satisfied we submit the whole string with either Enter
or Space, depending on the input method.
Hence, the scenario you described is expected. Nothing wrong with it. :)
Cheers enigmail. mozdev. org/
Arne
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iQIcBAEBCAAGBQJ OZFMdAAoJENiwmJ tstTzsDdEP/ isDlCa/ ys8L85SyZDu87Hy P qY+zqhfafbHUe7m 56QFMPdslBkw4m9 AZOOfYqG/ XHWiTdwuD4 aq6E7tEWu+ nBYLLh8xMAe4/ Qs8xUIGRhpx6iRg yyN6YmxAseZ /VevdRnIRT7tO0k hZnmQ2QPTQ0OocP FKK8iNKz2IxOVvj Xo6F Vd9p5oHko3fyZKk /Ra0pVesBdXaXhr jWFuEh/ 2ws2iYJep8SA EE1cC6w5WaX0O34 GE+vEC3f7GWvKhO DE9+FSYwFI/ ycDedPXU sTqeHGkvr+ PZGQZWQyctYn55A /LdIiCkPL9glZoQ 97mWH/r0n ibpFFgGHdWRggkw e0jsA68BSKGiAKx fgvAKN+ 1zVeWp6wc91f IflXAFGiUCqj3IJ LKuRQzhSEGOXpF+ AHVWJ13IkgACDyM +8e5 TyhQbW+ 3Jk0hO+ iw6pDRonKTzMemQ bQcHpQZMzD/ C1x524GLa x00kfcjMjF7PiiV qVbeNM6ubxIYx4I GVp9zPk9DiYWzg4 WsHZ J9mrU
VgGDsICFCKG0ZNE
AGUeh5kuXDYfYOC
wNlG7fPPn1PrzLX
iaEAHdzL2QWTuyf
sIBjOSYRWtPyLO5
0x8/h7Z14vUuPZe
UweXW8MuodKjh5T
w9zPaTIFwlmyX01
Xx1yMNRsRYpo1ZG
ZExelmlT16IGe3w
CJnU8LxtieaxeK+
=pndd
-----END PGP SIGNATURE-----