Kanji Recognizer & Hanzi Recognizer 1.6 Released

The new versions up of Kanji Recognizer (1.6.3) and Hanzi Recognizer (1.6) are now available in the Android Market. The major feature of this release is search on stroke. While you had to draw the whole character, and then press the 'Recognizer' button in previous releases, now the list of candidates is updated automatically as you add or remove strokes. This gives you immediate feedback and is particularly valuable  when you are not sure of the number and order of strokes in a character. On the flipside, it requires some processing power, so on older devices it may not work smoothly. If recognition is slow on your device, you can switch to the previous list view mode in Settings.

That, of course, is not all. Here's a list of all the new features and changes:
  • Drawing pen size and color are no adjustable. You can select any color with the built-in color selector (added in 1.6.3 for Kanji Recognizer).
  • Shake to delete stroke/clear all. A simple shake will delete the last stroke or clear the drawing canvas (you can change the mode or disable in Settings).
  • Failed downloads are now properly resumed.
  • The Settings screen has been re-organized for easier access to frequently used options.
  • Killed some bugs that happen in the wild.
Here's a screenshot of the new drawing screen, featuring recognition candidates on top, updated as you draw. You can long-press to get a context menu, just as with a regular list view. As you can, see the drawing color has also been customized.


Comments

Jack said…
hey - the app is great! Would you consider adding the feature of refining the search by stroke number? I think your recognizer doesn't use this...
24 June, 2011 01:25
Unknown said…
Glad you like it. It does take the number of strokes into consideration, although the mapping is not one-to-one: drawing 10 strokes doesn't necessarily give you only 10 stroke kanji as candidates.
24 June, 2011 11:47
Post a Comment

Popular posts from this blog

Decrypting Android M adopted storage

Image
One of the new features Android M introduces is adoptable storage . This feature allows external storage devices such as SD cards or USB drives to be 'adopted' and used in the same manner as internal storage. What this means in practice is that both apps and their private data can be moved to the adopted storage device. In other words, this is another take on everyone's (except for widget authors...) favorite 2010 feature --  AppsOnSD . There are, of course, a few differences, the major one being that while AppsOnSD (just like app Android 4.1 app encryption ) creates per-app encrypted containers, adoptable storage encrypts the whole device. This short post will look at how adoptable storage encryption is implemented, and show how to decrypt and use adopted drives on any Linux machine. Adopting an USB drive In order to enable adoptable storage for devices connected via USB you need to execute the following command in the Android shell (presumably, this is not needed if your...
Read more

Unpacking Android backups

Image
One of the less known new features introduced in ICS is the ability to backup a device to a file on your computer via USB. All you have to do is enable USB debugging, connect your phone to a computer and type the adb backup command in a shell. That will show a confirmation dialog on the phone prompting you to authorize the backup and optionally specify a backup encryption password. It looks something like this: This doesn't require rooting your phone and lets you backup application data, both user installed and system applications (APK's), as well as shared storage (SD card) contents. There are some limitations though: it won't backup apps that have explicitly forbidden backups in their manifest, it won't backup protected (with DRM) apps and it won't backup some system settings such as APN's and WiFi access points. The transfer speed is limited by ADB channel speed (less than 1MB/s), so full backups can take quite some time. There is also a rather annoying...
Read more

Using app encryption in Jelly Bean

Image
The latest Android version, 4.1 (Jelly Bean) was announced last week at Google I/O  with a bunch of new features and improvements . One of the more interesting features is app encryption, but there haven't been any details besides the short announcement: 'From Jelly Bean and forward, paid apps in Google Play are encrypted with a device-specific key before they are delivered and stored on the device.'. The lack of details is of course giving rise to guesses and speculations, some people even fear that they will have to repurchase their paid apps when they get a new device. In this article we will look at how app encryption is implemented in the OS,  show how you can install encrypted apps without going through Google Play, and take a peak at how Google Play delivers encrypted apps. OS support for encrypted apps The previous version of this article was based on Eclipse framework source packages and binary system images, and was missing a few pieces. As Jelly Bean sour...
Read more