Related
WMSpellChecker
I have been programming for Windows Mobile for a few months by now, mainly using Basic4ppc which is an excellent developing-software, at a low cost, for producing great Windows Mobile-applications (but also Desktop-applications). Basic4ppc is based upon the .Net Framework.
One of the strenght of Basic4ppc is that it has great support and not only from the developer but also from other users who are supplying Basic4ppc with a lot of extra featues through external libraries. I got interested in writing a library myself and this is how the WMSpellChecker-library was born. However, from the very beginning, my idea was that the library should be compatible not only with Basic4ppc but also with Windows Mobile-applications developed in Visual Studio and SharpDevelop using VB.NET and C#.
I have seen commercial solutions for spellchecking but since I wanted to learn writing a library, I thought this would be a nice thing to give "for free" to fellow developers.
Well, let me get back to the WMSpellChecker-library:
Basically, a spell checker customarily consists of two parts:
1) A set of routines for scanning text and extracting words, and
2) An algorithm for comparing the extracted words against a known list of correctly spelled words (i.e., the dictionary).
However, what mentioned above is only a "half" spell checker since these days spell checkers also suggest replacements/corrections for misspelled words (among other things such as synonyms and grammar-hints). Said suggestions can be proposed by a spellchecking-engine based upon various techniques:
- phonetic algorithms such as "Soundex" among others.
- word lists containing common misspelled words and letters commonly inverted
- functions called "Near Miss Strategy" and introduced by one of the first spell-checkers on the market, namely Ispell for UNIX and with its roots dating back to 1971.
- algorithms like "edit distance" which measures the amount of difference between two sequences. A famous one is the "Levenshtein distance".
- and other techniques
The "techniques" mentioned above have all been implemented in the library.
I am aware of the fact that (at least) WM6 already offers spelling-suggestions and a spell checker if PocketWord (Office) has been installed but still I liked this idea so I decided to make a library. In any case, as far as I know, only the dictionary corresponding to the language of WM6 is being installed so if you want to spell check words in other languages you cannot do so.
The way it works.....
First of all, apart from referencing the library itself, you need to add two objects to your application, namely DICTIONARY and COMPUTEDETECTION.
Then you need to load the dictionary-files by using "LoadDict". Currently they consist of four separate files. However, I may change this in a future release. The dictionary-files must be located in the application-directory although you can create sub-folders. This first release only supports English and the dictionaries distributed with the library must not be tempered with. Next release will bring support for other languages and will also include a separate program for handling dictionaries.
Once the dictionaries have been loaded, you can start the spellchecking by calling the library using "ComputeDetection" which passes on your textbox-control to the library. In case there are words that are not present in the dictionary, then a set of suggestions will be returned to the calling application and at the same time the word which was not found will be shown in the textbox in capital-letters. The suggestions produced by the library can be obtained using "ReturnSuggestions" which returns a string-array.
Once you have shown the suggestions returned by the library, you can let your user in your application decide what to do i.e.
-"IgnoreWord" - ignoring the wrong word
-"AddWord" - adding an own word to replace the wrong word
-"ReplaceWord" - replacing the wrong word with a word from the suggestions
At this point, you tell the library to continue spellchecking by using "ContinueDetection". You should also verify if spellchecking has been terminated by using "IsSpellingFinished".
At any time, you can interrupt spellchecking by using "UnloadDict". This will be useful in a future release of the library so you can unload an English dictionary and to replace it with, for instance, a French dictionary without exiting your own application. However, before unloading the dictionary, you should verify if a dictionary has already been loaded or not by using "IsDictionaryLoaded".
In the help-file, you can find more important information as to the methods/properties available. Please also check out the two sample-projects present in the attachment where the source-code has been fully commented. One is using a classic spellchecking-interface and the other one is using context-menus.
Other comments....
This first release has some limitations, such as support only for English and the need for a textbox-control. However, I will add other features in the future, for instance:
-support for other languages
-dictionary-tools (for creating dictionaries) - will be an external program
-possibility to add a user-dictionary
-possibility to limit amount of suggestions produced by the library (by using a "ranking-system")
-no further need for a textbox-control in your application. Your application will be able to pass on to the library only the word(s) you wish to spellcheck and the library will only return the suggestion(s). In this way, the spellchecker-library will not "interfere" with your application and you can use whichever control you prefer although you as a developer has to take care of the words to be passed on the library for verification.
-spellchecking "on the fly"
-extended error-handling
A few notes regarding dictionaries....
The English dictionary supplied with the library is composed of nearly 70'000 words. Dictionaries to be used with the library must be sorted and each word in the dictionary must use LF = chr(10) as line-endings. In addition, the dictionary should be saved as UTF-8.
From the dictionary, a KeyMap is created using either a Soundex - or a DoubleMetaphone-algorithm. In this moment, the KeyMap is being furnished with the library and loaded as an external file but future releases might create it on the fly (or at least an option to do so). With next release, I will add a utility, to be run from the Desktop, which will let you create your own dictionary and corresponding KeyMap which are compatible with WMSpellChecker.
Unlike English and Scandinavian ones, dictionaries for German and Latin languages such as Spanish, Italian and French will probably be rather large. This is due to the fact that German, Italian and other similar languages use a lot of suffixes, for instance when creating verbs. In order to overcome this, certain famous spellcheckers such as ASpell, ISpell, HunSpell (used by OpenOffice) have implemented dictionaries which mostly contain only the base-form of words/verbs. However, they use a supplementary file called "affix" which contains a lot of grammar-rules and this file together with the simplified dictionary overcomes the problem of large dictionaries. However, I believe this system is probably rather memory- and performance-hungry and might not be the best solution for Windows Mobile and PPC. However, maybe in the future I will look into this.
Another negative side-effect of using a too large dictionary is that said dictionary may include more obscure words which will increase the risk that the spelling-engine will "miss" real-word errors. For instance, the word wether illustrates this. The word is, arguably, so obscure that any occurrence of wether in a passage is more likely to be a misspelling of weather or whether than a genuine occurrence of wether, so that a spellchecker that did not have the word in its dictionary would do better than one that did.
Conclusion....
The library can be used with projects developed with Basic4ppc (PPC and Desktop) but should also work with projects created in Visual Studio and SharpDevelop (using VB.NET and C#). The library has been compiled targeting Framework Version 2.0.
Library-version: 1.0
Helpfile-version: 1.0
As mentioned before, this is my first serious library. Please check it out and let me know how well it integrates in your applications.
Please also give me feedback, suggestions for improvements, missing features, bug-reports etc.
The idea is to add spelling-support for other languages as well and here I might need some help from end-users. I will let you know.
UPDATE - 17/08/2009: I will in the next days release an updated version with support for other languages as well (starting with French, German, Swedish and Spanish).
Enjoy!
Rgds,
Tilleke
Reserved for future use
Hopefully this evening or by the latest tomorrow, I will upload a new release of the spellchecking-library :
1) which will permit you to pass on a word to verify to the library and the library will return the suggestions without "interfering" with your application. In this way, there is no further need for a textbox-control in your application and you can apply spellchecking to other controls as well (such as the Webbrowser-control).
2) if I find the time, I will add other languages as well in above release otherwise this will follow in the next release.
By the way, has anyone tested it yet? If yes, does it work? Any problems? Please let me know.
rgds,
tilleke
tilleke,
Thanks for this. Looks great, especially the foriegn language capability. I would like to add Thai and Lao to the libraries.
Thanks.
Hmm..I'd love to be able to add support for Thai and Lao but I foresee a few problems:
1) in order to do so, I would need word lists (dictionaries) in those languages and which would be free to use/distribute. If you have any, please let me know. I tried to google for some but I couldn't find any.
2) I couldn't locate an emulator supporting Thai or Lao which I would need to work with Thai-fonts. I guess there must be some kind of support for UniCode:
ก ข ฃ ค ฅ ฆ ง จ ฉ ช ซ ฌ ญ ฎ ฏ ฐ
ฑ ฒ ณ ด ต ถ ท ธ น บ ป ผ ฝ พ ฟ ภ
ม ย ร ฤ ฤๅ ล ฦ ฦๅ ว ศ ษ ส ห ฬ อ ฮ
Click to expand...
Click to collapse
In any case, if one found a dictionary then maybe the font problem could be resolved in one way or another
3) I don't know if the "techniques" mentioned by me in my first post, can be applied to the languages of Thai and Lao...
nagbenjy said:
tilleke,
Thanks for this. Looks great, especially the foriegn language capability. I would like to add Thai and Lao to the libraries.
Thanks.
Click to expand...
Click to collapse
For Thai there are a couple of SIPs available - Thaiwince and Thai-G. I don't have the links handy, but a search on Google will find them.
I don't use either of them. What I did was copy tahoma and tahomabd from the WINDOWS\FONTS folder on the desktop. Opened them in font creator and added the Thai and Lao fonts. I then copied the new fonts to the phone WINDOWS directory overwriting the existing fonts. I use Resco Keyboard Pro to enter Thai and Lao text.
I can post the fonts and the Lao Language skin if you want them. I will aso find some word lists. BUT after thinking more about your methodology in your first post, I don't think it will work. Thai and Lao only have spaces at the end of phrases and sentences, not between words.
Thanks.
Interesting. In any case, I found a worlist for Thai If you send me by PM your e-mail address, then I can send it to you and you can let me know if it is any good.
Out of curiosity: How do you write in Thai the following sentences?
"Today the sun is shining. I think I will go to the beach with my friends. Do you want to come with me?"
nagbenjy said:
Thai and Lao only have spaces at the end of phrases and sentences, not between words.
Thanks.
Click to expand...
Click to collapse
BTW, do you know if Thai-SIPS (Thaiwince and Thai-G) or keyboards such as the one mentioned by you, Resco Keyboard Pro, insert the Unicode Character 'ZERO WIDTH SPACE' (U+200B) between words. If it does, then one could simplify the spell-checking.
See this page for further information:
http://blogamundo.net/dev/2006/12/28/the-zero-width-space/
Originally Posted by nagbenjy
Thai and Lao only have spaces at the end of phrases and sentences, not between words.
Thanks.
Click to expand...
Click to collapse
I am still looking into the the ZERO WIDTH SPACE and will reply later.
In reply to:
"Today the sun is shining. I think I will go to the beach with my friends. Do you want to come with me?"
Depends on where you live, hot climate or cold climate. For cold climate where the sun hardly shines:
"วันนี้มีแสงแดด ผมคิดว่าจะไปชายหาดกับเพื่อน คุณอยากไปด้วยไหม"
Rough transcription, no breaks separating words, no punctuation:
"wanneemiisaengdaed phomkidwajapaichaaihaadkapphuon khunyaakpaiduaymai"
breaks separating words:
"วัน นี้ มี แสง แดด ผม คิด ว่า จะ ไป ชาย หาด กับ เพื่อน. คุณ อยาก ไป ด้วย ไหม?"
wan nee mii saeng daed. phom kid wa ja pai chaaihaad kap phuon. khun yaak pai duay mai?
Hot climate:
"วันนี้แดดจ้า ผมคิดว่าจะไปชายหาดกับเพื่อน คุณอยากไปด้วยไหม"
Rough transcription, no breaks separating words, no punctuation
wanneedaedjaa phomkidwajapaichaaihaadkapphuon khunyaakpaiduaymai
breaks separating words:
วัน นี้ มี แสง แดด ผม คิด ว่า จะ ไป ชาย หาด กับ เพื่อน. คุณ อยาก ไป ด้วย ไหม?
wan nee mii daed jaa. phom kid wa ja pai chaaihaad kap phuon. khun yaak pai duay mai?
Thanks for the link, interesting
NAG
Update - 17/08/2009: - I will in the next days release an updated version with support for other languages as well (starting with French, German, Swedish and Spanish).
In this regard, I need some help with verifying that the suggested replacements generated by the spellchecking-engine are accurate and reasonable. I need to verify Spanish, French and German so if (any) above languages is (are) your mother-tongue(s) or if you know them very well, please send me a PM and I will send you an application that can be run on a normal PC-desktop (Windows).
Ahh this is your home ...
Funny that you're working on a spell checker as myself I've been looking for a replacement to phatspell for a long time and then gave up. You could find my threads http://forum.xda-developers.com/showthread.php?t=350563.
....
Hal_rr:
this project (library) is more intended for fellow developers who wish to add spellchecking to their applications. For end-users, there is not much use of this library since it's not a standalone program.
For the time being, this project is on hold (although it has evolved a lot compared to the features described in my first post/introduction). However if a developer is interested in an updated version, just let me know.
Who knows, I might one day write a small texteditor with spellchecking support, just for the fun of it.
INTRO
I've started this thread to port the EzInput Keyboard to QVGA resolution. The keyboard is now fully functional yet still has a couple of small glitches to be fixed in portrait mode.
I am doing all the testing on my elfin, so I cannot assure that it will work on other devices so you'll have to test it yourselves!
You can download it here:
http://www.sendspace.com/file/uxi3be
THANKS
I must thank
DupinBJK:
http://forum.xda-developers.com/showthread.php?t=486227
nikoan89:
http://forum.xda-developers.com/showthread.php?t=489032
and
Conflipper
for their hard work on the VGA port, since I have mixed parts of their ports to get this QVGA version working.
KNOWN BUGS
XT9 is not currently working: the keyboard seems to get the coordinates (size and position) of the VGA keys. E.g.: if you press "q", "a" or "w" the keyboard will write "q" on the screen, since the three letters are in the area of the "q" key in a VGA screen (double size).
Any help on this matter would be really appreciated!!!
XT9 UPDATE 05/01/2009:
I´ve managed to get XT9 working by replacing the xT9ime.dll of the EzInput 2 with the EzInput 1.5 dll supplied with the ROM I am using. The problem now is that I cannot change XT9 mode back to normal mode .
Anyway I encourage you to test this and see if we can get a solution to the XT9 issues.
To test it, just go to the windows directory, rename eT9ime.dll to something else (e.g. eT9ime.dll.OLD) and reset your device (this should restore the dll supplied with your ROM).
I´m waiting for your comments!!!!
VIBRATION/XT9 UPDATE 05/13/2009:
I managed to get vibration to work a couple of weeks ago, but I wanted to fix the T9 mode before releasing a new version.
I´ve been working on T9 and have not been able to find where the code responsible for calculating the key pressed (based on the coordinates) is.
OPTION A: If anyone is able to find such place in the code or just point me in the right direction, I´ll find the time to patch et9Ime.dll so that QVGA users can enjoy T9 in this keyboard.
OPTION B: Another possible option would be to patch the et9Ime.dll from ezinput 1.5, but the mappings of some important keys seem to be different (XT9/ABC switch for example), and also different registry keys need to be updated so that everything works as it should.
Sorry for the lack of feedback, but I need more time for fixing these issues since this is the first time I am dealing with SIP/IME/IMM and stuff and I´ve found it a little bit more complex than I thought it would be.
HOWTO
Additionally, I'm planning on writing a very simple "howto" to explain people what they can do to adjust/fix/change the layout of the keyboard.
PS: I cannot post any screenshot now, so if anyone of you can upload one I'd be grateful.
problem on XT9 mode, maybe is the key mapping, i dunno that
for example type q,w,a,s the result is --> qqqq
type e,r,d ---> www
thanks for your hard working
T9 issue
You're right (i did not test the XT9 )
I'll have a look at it.
Thanks
Nice
Just 2 questions :
- vibrate when keys are pressed : Don t work normal maybe ...
- Is there a way to change language to french? i see 40C file ...
ty
looks great, good to finally have EZInput for QVGA.
major bug I noticed it messes up the keyboard mapping..for example Caps does not function, nor does the light, just flickers on then off when caps is hit, I believe to turn caps on and off (at least for me) I would have to use function, which also works for function (if that makes sense) lol
also the function keys got incorrectly mapped, I will try the tilt keyboard fix, hopefully that will work, and you can post that Cab.
Minor Issue: no SIP image to open the keyboard on the phone. its a black square, hit the square to active SIP. Would be nice to get a cool new icon though ;P
other then that, I will continue to test this, because the spacing between the keys and the skin is very nice
Thanks for your hard work and the post
I installed this new version and the only major thing I see compared to all the rest of the one you have posted is that the SIP Icon for the Keyboard that shows between the softkeys is missing, if you press the empty space the Keyboard still pops up and is functional but the icon is gone.
thanks man. Work great
So I don't have the phone keypad...is this just a problem with me or does anyone else have this problem?
XT9 is off, but that's fine cause I don't find a need for xt9 on a full keyboard anyways. Though like I said in the other thread I wish there was compact qwerty, or at least I could have the compact qwerty from my other keyboard as well.
Thanks a lot! Im at school now, but as soon as I get home, I'll install this on my phone.
- Thanks, your job is really appreciated.
Great !!!
I've been waiting for this for sometime now and just say thanks for the Qvga version Just wondering if anyone is working on the xt9 bug, i have gotten accustom to using that but if not no worries still a great keyboard !!!
Well, this full qwerty is a huge improvement over the EZ-Input one. I installed the keyboard and used the full qwerty without any problems. HOWEVER, does the Compact QWERTY mode not work with this? Thanks.
Thank you man, you are awesome !
I don't have any problems with it, except the reported bug of the SIP Icon.
But the keyboard on my Elf is a bit slow without O/C. (WM 6.5)
I love this keyboard !
XT9 bug
I've been looking at the XML files, the kdb files and the ldb files and I still cannot figure out the place where the XT9 keys size/position (x,y,h,w) is defined.
Does anyone know whether it's hardcoded in a PE module or it can be configured anywhere?
BTW, I'm afraid Compact QWERTY is not possible for the time being...
Sorry if I'm repeating. If I switch to numeric and press a key and then go back to ABC then all the keys are screwed up and when I press them I get the wrong keys. Do others have the same problem?
littld, i'm not experiencing that behaviour, sorry
asak0 said:
I've been looking at the XML files, the kdb files and the ldb files and I still cannot figure out the place where the XT9 keys size/position (x,y,h,w) is defined.
Does anyone know whether it's hardcoded in a PE module or it can be configured anywhere?
BTW, I'm afraid Compact QWERTY is not possible for the time being...
Click to expand...
Click to collapse
I have been trying to find this out too, I have looked everywhere and can't find the positions for XT9.
Side note, on all 3 previous versions you could use XT9 in ABC and it worked perfectly, but in the new version it just types normally in ABC and XT9 is still broke.
ems275 said:
I have been trying to find this out too, I have looked everywhere and can't find the positions for XT9.
Side note, on all 3 previous versions you could use XT9 in ABC and it worked perfectly, but in the new version it just types normally in ABC and XT9 is still broke.
Click to expand...
Click to collapse
You mean in the previous versions I posted in the QVGA Rhodium Development thread?
asak0 said:
You mean in the previous versions I posted in the QVGA Rhodium Development thread?
Click to expand...
Click to collapse
Yes, all 3 you posted in that thread. If set to XT9 all key mapping was off as I had posted in that thread and others. But ABC worked as XT9 without a problem. It was weird. But I am running the last posted version which I downloaded from sendspace and it works as described above. When I installed the one when you opened this thread also from sendspace XT9 key mapping is still the same, totally off and ABC just functions as it should, regular typing with no text prediction.
Hope that makes sense?
ems275 said:
Yes, all 3 you posted in that thread. If set to XT9 all key mapping was off as I had posted in that thread and others. But ABC worked as XT9 without a problem. It was weird. But I am running the last posted version which I downloaded from sendspace and it works as described above. When I installed the one when you opened this thread also from sendspace XT9 key mapping is still the same, totally off and ABC just functions as it should, regular typing with no text prediction.
Hope that makes sense?
Click to expand...
Click to collapse
Not really...
Anyway I'll play around a bit with the different modules to see what I can get.
This thread will hopefully become a communal Work In Progress. I received my TP2 yesterday and have gotten to work right away on installing Japanese IME on my phone. Anyone who can offer useful tips or any help at all, I greatly appreciate it.
12:11 PM 8/21/2009
So far my first attempts have not proved fruitful. As a first step, I installed Olinex's HSPL. After that, I began installing the cabs from Zgembo's Touch Pro/Diamond Thread. I first installed the Let's Japan WM6.1 R07. After a soft reset, it seemed to be installed ok. I could see a few Chinese characters in the predictive text box above the SIP keyboard (although, there were some boxes too). Second step, I attempted to install the Japanese Advanced IME from the same thread. I should note, it clearly states that it's designed for VGA devices, and TP2 is WVGA. I went ahead with the install anyway. And that's when the trouble began. After soft reset, the HTC splash screen comes up, but after that- black. Nothing. No amount of button pressing or anything short of a hard reset resolved it. And that's as as far as I've gotten.
I'm going to do some more reading and then try again. If anyone knows a better way to go, let me know. Hopefully with more input this can become useful to other people living in Japan that require Japanese capabilities on their Touch Pro 2.
*****UPDATE*****
first off, my apologies, i realize that my solution to the problem wasn't clearly stated in my other posts below.
to get Japanese input/output working on your Rhodium/Touch Pro 2, do the following:
install Asukal LetsJapan6 and restart
install Asukal's IME_31J_FULL, but do not restart
install Asukal's Enable_IME and restart
that simple. romaji, kana, kanji, kensaku, tegaki (the handwriting recognition inputs) will all work. XT9/Predictive will be broken. And you will need to switch between かな カナ or 英数 on the soft keyboard to get the hardware keyboard to type in the language you want.
Try CE-Star Suite Chinese/Japanese enabler
http://www.mobem.com/products/cestarwm5.php
Mesquire said:
Try CE-Star Suite Chinese/Japanese enabler
http://www.mobem.com/products/cestarwm5.php
Click to expand...
Click to collapse
have you tried that on your TP2? what results did you get?
for anyone else trying Zgembo's cabs from the Touch Pro/Diamond thread, can you let me know your results? After installing LetsJapan, for my SIP icon, I'm getting an A4. In the dropdown menu where you select which keyboard to use, it has A4 智能输入 (i can't read those characters at all). anyone know the deal with this A4 menu?
No problem running CE-Star on my TP2 and the interface is in English, but I don't use or need Japanese input so I cannot comment on that.
yeh, I need Japanese input. and the A4 Chinese pre-installed in my ROM seems to conflict with it somewhat.
almost there... i hope
Ok, so here's the situation so far. After nearly 10 resets, I seem to be *almost* there.
I installed in the following order:
1. LetsJapanWM61r07.cab, then reset
2. KeyTouchJapIMEr07.cab
3. Enable_IME_2.zip, then reset
4. Softbank MMS
So far, I am able to send and receive with no problem. however, I'm still not able to type using any katakana, hiragana, nor kanji. even when i use the kensaku, it will recognize the characters, but when i choose the character, nothing shows up. Japanese input seems to be completely broken.
Is anyone on here able to type in Japanese on their device? if so, what program are you using? the relevant programs I have installed are:
Zgembo JapaneseIME
Asukal Enable_IME
Zgembo Lets Japan WM6.1
Zgembo Lets Japan WM6.1 Mincho
Zgembo Softbank MMS
The soft input keyboards available to me are:
A4 智能输入
Block Recognizer
Kana*
Kensaku*
Keyboard
KeyTouch*
Letter Recognizer
Romaji*
Tegaki*
Touch Input
Transcriber
* for the Japanese characters that don't show up when I type
CE-Star has some Japanese support (I need it to show Japanese song names, but not all words are displayed correctly) and Romaji input but since I don't know any Japanese I can't test the accuracy of inputs for you, but their Romaji input appears to work.
@mesquire: yeah, CE Star doesn't work for me. i think i'll need a bit of a more 'homegrown' solution.
Getting Japanese Input running
well, i finally managed to enable Japanese input. previously, i had been attempting to install Zgembo's KeyTouchJapIMEr07.cab. VISUALLY all the keyboards were there, but only a limited few functioned. i did a lot of trial-and-error installations to figure out what effect each cab file had.
after installing the softbank connection I began installing the IME piece by piece. I should mention that the ZTA4 (Chinese) IME is preinstalled in this stock ROM. the keyboards included in this IME are Touch Input, A4 智能输入, Block Recognizer, Keyboard, Letter Recognizer, Transcriber. i'll paste some of my edited installation/setup notes below. if you don't want to wade through that muck, just skip down to the Highlights section below it:
17. Install Keytouch (Zgembo JapaneseIME; 17.5mb) -> DON'T RESTART
18. Install Enable_IME_HTC_HD
19. Check Input (5 new: Kana, Kensaku, KeyTouch, Romaji, Tegaki)
20. Restart
21. Check input, Regional Settings (still no Japan)
22. test input
QWERTY Touch keyboard is fine (XT9 doesn't work)
Keypad only types numbers
small keyboard is fine
romaji broken (no kana)
kana broken (blocks)
KeyTouch broken (blocks)
Tegaki is fine
kensaku is fine
A4 is fine
block recognizer is fine (but sucks)
Letter Recognizer is fine
Transcriber is fine23. Install CEStar Japan (2mb); no change in SIP functionality; restart; no change in SIP functionality
24. Install Softbank MMS (5.2mb)
25. Install Asukal Lets Japan6 (4.25mb); restart; Regional Setting changed to Japan; Mapple functional; Kana is default keyboard; A4 智能输入 now reads A4 智能▯入; no change in SIP functionality
26. Install 2_IME_31J_FULL.cab (Ask IME 31J) (7.8mb); new input: Roma Ji, Kana, TagakiKensaku, restart, no change in SIP functionality
27. Install LetsJapan WM61r07 (Zgembo Lets Japan WM6.1; 4.25mb); restart
28. Install Enable_IME_HTC_HD again
29. Install 2_IME_31J_FULL.cab again; restart; No change
30. Install Enable IME2; restartl No change
31. Remove Asukal LetsJapan6
32. Remove Zgembo's LetsJapan6 (but didn't remove properly; still in Programs list); A4 is now A4▯▯▯▯; restart; problem occurred with cprog.exe
33. Install LetsJapan WM61r07 again (Zgembo Lets Japan WM6.1; 4.25mb); restart; problem occurred with cprog.exe; no regional setting change
34. Remove Asukal Enable IME; no change
HARD Reset
Highlights
if you have no desire to read through all that and decipher it, it basically says this:
ZTA4 natively allows you to view Japanese (Japanese characters are Chinese characters afterall, but it allows you to see Kanji and Kana)
ZTA4 does not allow you to write in Japanese nor display Japanese in software designed for Japanese OS.
LetsJapan6 (both Asukal's original and Zgembo's derivative) adds Japanese to the 'Regional Settings'. it also installs the font used for Japanese input/output. Of the two, only Asukal's LetsJapan allows software designed for Japanese OS to display Japanese properly (ie. Pocket Mapple). However, neither LetsJapan installs any keyboards (only fonts), so you still cannot write in Japanese yet.
LetsJapan6 (both Asukal's original and Zgembo's derivative) both appear to conflict with ZTA4. I don't know of any change in functionality, but A4 智能输入 in the list of keyboards will now read A4 智能▯入 (if anyone knows of a way for me to completely remove ZTA4, please share).
Zgembo's KeyTouch/JapaneseIME adds 5 new keyboards to your available inputs: Kana, Kensaku, KeyTouch, Romaji, Tegaki; of these 5 keyboards, only 2 work- Kensaku and Tegaki
Zgembo's KeyTouch/JapaneseIME doesn't allow Japanese input; it also breaks XT9 functionality in the English keyboards; Visually it's lovely and everything is there, but it does not function on this particular stock ROM. I should also warn: if you do install this IME, DO NOT RESTART immediately after installing. Immediately after installing, install one of Asukal's Enable_IME files (there's one from long ago and one he recently made for the Touch HD... although, i think they are exactly the same). If you do not install the Enable_IME before you restart your device, after your device boots up and the splash screen fades, you'll be stuck on a black screen, at which point, your only option is to Hard Reset.
Asukal's IME_31J_FULL is the alternative to Zgembo's KeyTouch/JapaneseIME. although Zgembo's is prettier, it unfortunately doesn't work on TP2 (if someone else has had a different experience, please share). Asukal's IME is rudimentary, no fancy stuff like a Japanese Touch Keypad or predictive text, but it allows you to write in Japanese.
Asukal's IME_31J_FULL adds 4 new keyboards: Roma Ji, Kana, Tegaki, and TagakiKensaku. All seem to function perfectly fine as touch keyboards. As touch keyboards though, they're not very finger friendly, so you'll be stuck using your stylus to tap. In hardware keyboard mode, at the moment there is no known Fn key combination that allows you to switch between English and Japanese. This must be chosen by first choosing either かな カナ or 英数 on the soft keyboard, then typing with the hardware keyboard. And again, if you do install this IME, DO NOT RESTART immediately after installing Same thing will happen as stated above. Immediately after installing, install one of Asukal's Enable_IME files. If you don't, you'll have lots of fun hard-resetting.
After setting up the IME, it should be relatively safe to install the Arcsoft Softbank program. I've been using that and have no problems sending or receiving SMS and MMS... although, I don't know how to use emoji since i think it was something that is inherent in the Japanese KeyTouch keyboard.
So that's my rundown. Hope it will be useful to others. What I want to do now is find a way to Isolate the Japanese KeyTouch keyboard, get rid of ZTA4, and get XT9 prediction working again on both English and Japanese keypad. I'd really love it if Asukal, Alcibiade, Zgembo, larsucks and the rest of the X01HT gang could get in on this and offer some suggestions. Anyone else who has discovered anything interesting, please don't hesitate to post!!
Ookii.org
You should look at Ookii.org:
http://www.ookii.org/software/japaneseinput/
mschaffer said:
You should look at Ookii.org:
http://www.ookii.org/software/japaneseinput/
Click to expand...
Click to collapse
thanks, i'm familiar with ookii.org. good stuff. i've been using his pocket dictionary for a few years now. but with regards to his japanese input, i don't imagine there will be added functionality over Asukal's IME, but I do imagine there will probably be less. And still, it's old, so the letters will still be tiny, there will be no keypad, and there will be no predictive text.
Did you try BeeGee_Tokyo's CAB for Topaz?
http://forum.xda-developers.com/showthread.php?p=4102158
I tried it on my Rhodium and it works quite well, though it seems to slow the system down. Only thing I found is that I can't use the physical keyboard to input Japanese.
Topaz and Rhodium are quite similar, definitely in terms of screen res and probably software I think.
e60202 said:
Did you try BeeGee_Tokyo's CAB for Topaz?
http://forum.xda-developers.com/showthread.php?p=4102158
I tried it on my Rhodium and it works quite well, though it seems to slow the system down. Only thing I found is that I can't use the physical keyboard to input Japanese.
Topaz and Rhodium are quite similar, definitely in terms of screen res and probably software I think.
Click to expand...
Click to collapse
thanks for the suggestion. i already got Japanese input working now, but i may try that one in a later configuration.
what i'd like to know now is if anyone else has been able to install HTC KeyTouch (the Japanese version from the X05HT) onto their Rhodium. That is the SIP keyboard I would really like to get functioning, as one-handed typing on the Rhodium would be lovely. Also, I think that the emoji are preset in that SIP, so presently, i can't get them working in my Softbank Mail program. anyone have any success with that?
btw e60202, if you follow the method i stated on the previous page, you can have Japanese input both software and hardware keyboard.
Cool...I'll give that a try and let you know if I have any trouble. Thanks.
@shunsai
I want to buy the HTC Touch Pro 2 here in Germany soon. But reading and writing Japanese is very important to me. So, I am glad that you found a solution for my problem.
But I still have some questions.
Could you tell me where I can download Asukal LetsJapan6, Asukal's IME_31J_FULL and Asukal's Enable_IME?
If it won't work the way I hope it will, how can I remove it from my device afterwards?
dkun said:
@shunsai
I want to buy the HTC Touch Pro 2 here in Germany soon. But reading and writing Japanese is very important to me. So, I am glad that you found a solution for my problem.
But I still have some questions.
Could you tell me where I can download Asukal LetsJapan6, Asukal's IME_31J_FULL and Asukal's Enable_IME?
If it won't work the way I hope it will, how can I remove it from my device afterwards?
Click to expand...
Click to collapse
asukal keeps a blog where he also includes his files. this entry he wrote is about the Touch HD, but the files work for the Touch Pro 2 as well. the 1_Enable_IME_HTC_HD.cab included in the zip seems to be the exact same as Enable_IME_2.zip
LetsJapan6 is available here
most of his other files are available here.
if things don't work out, hard reset will become your friend, so make sure to backup all your files and settings before you install just in case.
Thank you very much for the info, Shunsai!
Have you already found a way to change the input method with the hardware keyboard?
Somewhere I read something about pressing the Crtl and Shift at the same time. Does that work on your device?
Having trouble with text
First of all. I want to thanks to you Shunsai and Asukal!
I'm having trouble to input Japanese with Touch pro 2.
Now everything work good except text message.
When I text with Japanese it shows "????????????????".
It shows fine with email and web browser.
Do you have same problem? Or it is just for me?
dkun said:
Thank you very much for the info, Shunsai!
Have you already found a way to change the input method with the hardware keyboard?
Somewhere I read something about pressing the Crtl and Shift at the same time. Does that work on your device?
Click to expand...
Click to collapse
hey dkun, no, i still haven't found a way yet. hopefully someone with more knowledge can suggest something soon.
quickmo said:
First of all. I want to thanks to you Shunsai and Asukal!
I'm having trouble to input Japanese with Touch pro 2.
Now everything work good except text message.
When I text with Japanese it shows "????????????????".
It shows fine with email and web browser.
Do you have same problem? Or it is just for me?
Click to expand...
Click to collapse
no prob. i'm here to help people in the same boat as me if i can, but really i haven't done anything. i'm just benefiting from the fruits of asukal's labor like you. can you tell me more about your device (which ROM/region)? what order did you install the cabs in? was it on fresh install?
i'm still tinkering around trying to get japanese and english input where i want them, but japanese IME seems to be very tempermental in general. so far, its really only worked for me consistently when i installed in the order in the OP.
Have you guys tried this Japanese display and input app?
http://forum.xda-developers.com/showthread.php?t=445550
No need for separate installs - all in one cab, works on many different devices, also with hardware keyboard. Much smoother than LetsJapan or CE-Star IMO.
I take no credit for this, I just found it in the general forum.
Original post by [FONT="]hirad_sabaghian[/FONT] and thread: http://forum.xda-developers.com/showthread.php?t=598633
"Move over T9, here comes Swype
Swype works with an on-screen QWERTY keyboard like you have on the tablet version of Windows and on the iPhone. But instead of tapping letters out, you press your finger or stylus on the first letter, then, without lifting it, move it to the remaining letters in the word. When the word is done, then you lift."
Head over to the original thread to download the WVGA version...
Been using this for the past couple of days and I must say it's excellent! Doesn't quite fit correctly on 6.5.x as it overhangs the bottom bar, but doesn't make it unusable. Recommend looking at some of the tutorial videos on the Swype website.
Been using shapewriter for months myself and fairly happy with it, fits HD fine and I find it the quickest way of entering data. Using the stylus it is very accurate (95 - 100%), with my finger, not quite so accurate (50 - 75%) but good enough for a short SMS. Will give Swype a go and compare.
woolytoon said:
Been using shapewriter for months myself and fairly happy with it, fits HD fine and I find it the quickest way of entering data. Using the stylus it is very accurate (95 - 100%), with my finger, not quite so accurate (50 - 75%) but good enough for a short SMS. Will give Swype a go and compare.
Click to expand...
Click to collapse
no other dictionnary dispo as wwe or is there already dutch or french supported t9?
djcedric said:
no other dictionnary dispo as wwe or is there already dutch or french supported t9?
Click to expand...
Click to collapse
Or German perhaps?
Absolutely love Swype on my HD, now hoping for German layout to follow soon. But with $5 million just received from Nokia and Samsung Swype should get up to speed soon! Android version in the works.
Tut on how to add custom word dic's and user databases in your language of choice: http://forum.xda-developers.com/showpost.php?p=5127650&postcount=3
Firstly I would like to say I love Swype !
What I have realised is that when sending a SMS with the HTC Messaging interface (6.5 ROM Dutty HG Leo R0), as I type a contact name with the original keyboard I am presented with a like of possible contact matches as I type more letters. Now with Swype, as I type the contact name it now longer presents a list of possible contacts like the original keyboard. Has anyone found a workaround for this problem.
the workaround is to type some letters then backspace one character... the list will then pop up. not sure why this is but at least there's a way.
I've just tried this and must say it is a very nice input method! Thank you for starting this thread and making this excellent software known
Hi,
I know this is a topic that has already been talked about a lot, but after going through many pages in different threads and a lot of experimenting, I still haven't found a complete solution.
I am using a Tilt 2 using a Titanium Energy ROM and am looking for a solution for Hebrew input. I have tried 3 cabs so far: HD2_HebrewEnabled_v1.2", "HebrewHD2", and "Uniscribe".
I have discovered that some apps work better with Hebrew then others. Word, OneNote, Phatnotes, etc. have a cursor problem with all three cabs (the cursor stays to the right, and after typing has a "mirror" effect and if you try to place it in a sentence to select text or edit, it will not actually insert or select there but at a different point). Notepad and PhatPad do not have this cursor problem.
The first 2 cabs have a problem with mixed text (heb & eng) in Word, etc. Uniscribe has a problem always putting punctuation to the right even in Notepad (the first two cabs are fine with this in all apps).
Has anyone found a cab that solves all?
Thanks
UPDATE!
After doing more searching, I found another cab at this thread "forum.xda-developers.com/showthread.php?t=554802" called simply "Hebrew.cab" and it is actually better then the other 3 I had tried. It allows mixed text and does fine with punctuation, the only remaining problem is the cursor in Word, etc.
I also wanted to detail some other things I came up with in my research. To get Hebrew on the hard keyboard I am using AEk mapper. A while back I found a layout provided by a generous member (OSM or rbroudo?) and I made up my own phonetic layout, bec I found using stickers very impractical. I found that I could also set a different shortcut to the Home key, w/o interfering with AEK.
Acrobat Reader 2.0 works well with Hebrew and has a rich feature set, you just have to reverse your input when entering a search term.
Ulrich Grieve has a Hebrew Reader for viewing Palm text files.
I found an epub reader called "Freda" which also works with html that works with Hebrew. I found (on html at least) that the settings that worked are "Force Line Direction = RTL", "Force Word Direction = LTR" (I also set encoding to utf8 but don't know if that is necessary).
Perhaps this will be useful for you (if it's been updated for 6.1/6.5):
http://www.penreader.com/pocket-pc/hebrew/Language_Extender_Hebrew.html
AlecTaylor said:
Perhaps this will be useful for you (if it's been updated for 6.1/6.5):
http://www.penreader.com/pocket-pc/hebrew/Language_Extender_Hebrew.html
Click to expand...
Click to collapse
Thanks for the response
I checked the website and highest listed is 6.0 In any case my experience with that software in the past wasn't so great and I am looking for a free solution.
All in all, despite a few quirks, I am pretty happy with the Hebrew situation now. WP7 doesn't support Hebrew at all. Symbian doesn't have anywhere near all the options I mentioned in post #2, not does Maemo on the n900.
Does anyone know how well Android is doing?
Hebrew for Touch pro 2
Hi
I'm a newbe i would like to be able to read and write Hebrew for Touch pro 2
(not change any menu)
What files do i need to install (can you post a link)
(I tried installing Hebrew support only.cab file from the_dude
I get hebrew words but not RTL)
Which ROM are you using?
I found the attached .cab file to work very well with the "Energy" ROM (I use the Titanium with enhanced Mobile Shell), I don't know if it works as well with the stock ROM.
(see my earlier post #2 for more tips)
If it doesn't work well I could give you other links