LiZunYuan / networkpx

Automatically exported from code.google.com/p/networkpx
0 stars 0 forks source link

AutoCorrect Doesnt Work with iKeyEx. #31

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Enable hClipboard from international keyboard, and try typing in text..
AutoCorrect doesn't work..
2. When hClipboard is disabled, the autocorrect works fine..

What is the expected output? What do you see instead?
Obviously you'd expect auto correct to work regardless of hClipboard being
enabled or disabled.

What version of the product are you using? On what operating system
(iPhone/iPod Touch? Firmware version?)?
Version 0.0-2 on iPhone 3G Firmware 2.2

Original issue reported on code.google.com by coolkarthik88 on 26 Jan 2009 at 6:28

GoogleCodeExporter commented 8 years ago
How to you type with hClipboard? o_O

Original comment by kennytm@gmail.com on 26 Jan 2009 at 6:33

GoogleCodeExporter commented 8 years ago
(@1   s/to/do/)

Original comment by kennytm@gmail.com on 26 Jan 2009 at 6:38

GoogleCodeExporter commented 8 years ago
I hope this is fixed in the future update.. Clippy beta seems to work fine, but 
I
really like hClipBoard's implementation..

Original comment by coolkarthik88 on 26 Jan 2009 at 4:17

GoogleCodeExporter commented 8 years ago
@3

I don't understand what you mean. What do you mean by "disabled"? Plus I can't
reproduce it when hClipboard is inactive, and you can't type when hClipboard is
active anyway.

Original comment by kennytm@gmail.com on 26 Jan 2009 at 4:58

GoogleCodeExporter commented 8 years ago
Basically hClipboard when enabled, normal typing on the iPhone keyboard looses 
its
auto correct functionality.. But When i disable the international keyboard from 
the
settings, the autocorrect feature of the iPhone keyboard works fine.. 

I hope am clear on this ...

Original comment by coolkarthik88 on 27 Jan 2009 at 4:00

GoogleCodeExporter commented 8 years ago
Turns out not a problem of hClipboard but iKeyEx. Changes title.

Original comment by kennytm@gmail.com on 5 Feb 2009 at 12:03

GoogleCodeExporter commented 8 years ago
Issue 45 has been merged into this issue.

Original comment by kennytm@gmail.com on 5 Feb 2009 at 12:04

GoogleCodeExporter commented 8 years ago
Do you know any workaround or is it just a reprogramming within iKeyEx? 
Eventually I
assume it's possible to get it to work :P.

Original comment by fabca...@gmail.com on 5 Feb 2009 at 12:09

GoogleCodeExporter commented 8 years ago
Seems due to iPhoneOS creates independent dictionary for iKeyEx.

To see this, type "oll" using the AZERTY keyboard in issue 45 many times in 
Notes.
Then type "omo". 

Also see that in /private/var/mobile/Library/Keyboard/ there is a file named
iKeyEx:<KBName>-dynamic-text.dat now...

Original comment by kennytm@gmail.com on 5 Feb 2009 at 12:13

GoogleCodeExporter commented 8 years ago
But iKeyEx uses the en_US dictionary properly is that right?

Original comment by fabca...@gmail.com on 5 Feb 2009 at 12:22

GoogleCodeExporter commented 8 years ago
@10: Not really. "Ill" is now auto-correcting to "Oll" too..... @_@

Original comment by kennytm@gmail.com on 5 Feb 2009 at 12:27

GoogleCodeExporter commented 8 years ago
Is this a "problem" of iKeyEx which you have to figure out, or is it the 
"stupid"
iPhoneOS?
And by the way thanks for the InputClass, I completely rewrite the Azerty 
layout :P.

Original comment by fabca...@gmail.com on 5 Feb 2009 at 12:30

GoogleCodeExporter commented 8 years ago
(Technical)
Possible solution to fix loading static word trie (autocorrection):

NSString* UIKeyboardStaticUnigramsFilePathForInputModeAndFileExtension(NSString*
mode, NSString* ext = @"dat")

MSHook this to use the referred mode.

Original comment by kennytm@gmail.com on 5 Feb 2009 at 12:34

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
@12:

This the problem of iKeyEx because the whole iPhoneOS system doesn't understand 
what
the heck those funny "iKeyEx:XYZ" keyboards are. They just understand "en_US",
"nl_NL", etc, those which are built-in. Therefore I have to patch a lot of 
functions
to force iPhoneOS to recognize them, or pretend them to be built-in ones.

Original comment by kennytm@gmail.com on 5 Feb 2009 at 12:37

GoogleCodeExporter commented 8 years ago
@14: Comment 13 was for my own reference only. 

Original comment by kennytm@gmail.com on 5 Feb 2009 at 12:38

GoogleCodeExporter commented 8 years ago
(Technical, for my ref only)

Possible solution to fix loading dynamic word trie (user dictionary):

NSString* UIKeyboardDynamicDictionaryFile(NSString* mode)

MSHook this to use the referred mode. If both this & @13 work then case closed.

Original comment by kennytm@gmail.com on 5 Feb 2009 at 12:41

GoogleCodeExporter commented 8 years ago
I hope you get it patched. But essentially it's not about the dynamic keyboards.
iKeyEx should be patched to recognize "nl_NL" as the rightfull "nl_NL" 
dictionary and
not "iKeyEx: nl_NL". Just like the built-in keyboard they use the standard
dictionaries (ofcourse). If iKeyEx adresses the dictionaries the same way it 
should
be solved I think. Thanks for the quick responses.

Original comment by fabca...@gmail.com on 5 Feb 2009 at 12:44

GoogleCodeExporter commented 8 years ago
Fixed in r112.

Original comment by kennytm@gmail.com on 5 Feb 2009 at 2:32

GoogleCodeExporter commented 8 years ago

Original comment by kennytm@gmail.com on 5 Feb 2009 at 2:34