Definitely AnkiDroid. It's not perfect (nor is its syncing), but it's pretty good and I use it pretty confidentially. Simeji is good for typing in Japanese. I have a bunch of others I've never gotten around to trying, unfortunately, and lack the time right now...but unfortunately it's not nearly as rich as iTunes in quality.

https://code.google.com/p/ankidroid/downloads/list

Sure it still has some bugs (not that I've encountered any), but the custom fonts support makes it all worth it. Solves the problems we had on the previous page

Vertical Text Viewer just got a Honeycomb update. Woot. Looks a lot better on the tablet. Yay for bigger text on the tablet.

Also, I've been messing with AnkiDroid 0.7 alpha 2, and it's a whole new iteration. The program is a lot smoother in design, with a lot of annoying bits fixed, and now I can replace the awful standard Android font with YOzFont for my cards.

It's a little tricky to install, but it's doable. Since YOzFont is stored on my Win7 box as .ttc files, you have to find the right file for the version of YOz that you're using, then rename it to the exact name of the font that you're using. (For example, YOzRE.ttc gets renamed to YOzFontE.ttc if you're using YOzFontE for your cards.)

It's an alpha, so there are bugs, but it's not as bad as Chrome for Honeycomb, which drives me up the wall. -_-#

I'm also having problems. I added some fonts to /AnkiDroid/fonts (DroidSansJapanese.ttf, msgothic.ttc and msmincho.ttc) and they are listed when I select menu>Preferences > Other > Default font, but they do not seem to be applied when I select them... (Nexus S, Android 2.3.4, AnkiDroid 0.7beta6)

Last edited by Ricardo (2011 July 27, 10:12 pm)

According to Using custom fonts with AnkiDroid:

The name of the font file must match the name of the font used in your card layouts.

My deck (RTK, downloaded from Anki) is using "Arial" for English and "MS Mincho" for Japanese. If I rename /AnkiDroid/fonts/msmincho.ttc to Arial.ttc, the English text in my cards appears with the MS Mincho font. If I rename the file to "MS Mincho.ttc", since the kanji in the cards are using this font, the English text goes back to the default Arial font and the Japanese text is still using the default Android font.

Ricardo wrote:

My deck (RTK, downloaded from Anki) is using "Arial" for English and "MS Mincho" for Japanese. If I rename /AnkiDroid/fonts/msmincho.ttc to Arial.ttc, the English text in my cards appears with the MS Mincho font.

Rooting the phone is great, but why would you do the above? Renaming one font to another? Of course it appears wrong; it uses the wrong font.

It's so simple, if you use the 'EPSON 教科書体 M Normal' font, you copy the file, rename it from 'epkyouka.ttf' to 'EPSON 教科書体 M Normal.ttf', and put it in the AnkiDroid/fonts folder. Do the same for all the fonts you use.

The use of custom fonts isn't very stable yet though, is anyone else having problems with displaying the furigana when custom fonts are involved? My deck has three fields that all use other fonts, and with furigana turned on it usually doesn't display the text. It's not a problem with displaying the furigana, it's unable to display the entire field because of it.

I know I should be bringing this up in the AnkiDroid discussion forums, but if this is a common problem you'd think there'd be an issue on it already.

Just bumped into that thread... thanks all for using AnkiDroid!
If you notice any bug, please search it in the issue tracker and add it if not present, that will make it easier to keep track of the progress:
http://code.google.com/p/ankidroid/issues/
I will probably release AnkiDroid 0.7 (with custom fonts) on Wednesday, so now is your last chance to test the beta and let us know!

By the way, we gladly welcome volunteers :-)
There is a lot you can help with, even without coding:
https://code.google.com/p/ankidroid/wik … oper_tasks

Cheers!
Nicolas Raoul

I use the Anymemo flashcard program on my N1 and it allows you to install and use TrueType fonts.  I am currently using MTLc3m.ttf to display proper Japanese fonts.

Bit late but it should also be listed here:

A while ago I created an Android app called Conjugation Japanese, you can find our "official" thread for it here.

Its a simple game that helps you learn and practice Japanese conjugations.

Double-posting, but it's new info:

OpenWNN Flick is pretty good. It's slightly less ugly than Simeji (which is also based on OpenWNN), but it also suffers from being too small in landscape mode on a tablet. Otherwise, it's a solid JP QWERTY-keyboard. (It also has 2 built in cursor movement keys-- really handy.)

https://market.android.com/details?id=com.pm9.flickwnn

The Multiling JP plugin is *really* annoying in one aspect-- they killed the "X" key, so I still have no clue how to make small characters, like っ. I would consider it beta for now, and just wait for the foreseeable future until the Japanese plugin comes out of beta. One nice thing the Multiling keyboard does do-- it has an option that changes the keyboard layout so that it's better suited to thumb-typing on tablets. For English, it should be pretty usable.

Yes, both use QWERTY keyboards-- all of them use QWERTY keyboards for tablet mode. If they're not in that mode, fix it in settings.

The only way to fool the market into possibly letting you load the ATOK app would be to use a JP VPN service... maybe. Even then, it knows where you are via GPS, so there's a high probability that it wouldn't work.

The best way to get a JP keyboard is to buy a tablet in Japan, and if there isn't a good keyboard pre-loaded, install one yourself from the Market there. (Or ask the sales guy where to find one.)

Here's another keyboard, kind of a mixed bag. Missing the kana key that Simeji has, but nice and big; slightly smaller than Multiling, which is smaller than the standard Android Kbd.:

https://market.android.com/details?id=n … eyboardpro

Needs this bit to work:
https://market.android.com/details?id=n … oardpro.jp

Use the trial version first to make sure you want to spend the $2-3 on it:
https://market.android.com/details?id=n … boardtrial

It doesn't have the sharpest dictionary. It can't do 行って unless you type something extra after it, same with 買って and a few other basic words. Not sure what the deal is with that. But it does have an X key, so you can type small characters like in パーティ. (Which is pa-texi.) (Unlike Multiling.)

FlickWnn doesn't have a kana key, but it will automatically suggest what you're typing in katakana. (But it's actually smaller than the Simeji Keyboard.)

IMO, Simeji is the best of them all. You just have to get used to it's ugly looks and odd size. It just works.

Elenkis wrote:

Unfortunately it sounds like Market Enabler doesn't work on Honeycomb, at least not for wifi only tablets anyway.

I think I'll hold off on buying an Android tablet for now.

It seems you're not alone on this (here), might be a good reaction for two reasons.

One, I personally think Google shot themselves in the foot by creating another "branch" of their system just for Tablets. They're trying to repair this mistake now but the message is clear for me: "we were caught with our pants down by Apple, wanted to respond quickly and thus our bastard OS was born". It's the first iteration of a platform that will be killed in
one/two releases, where both mobile+tablet OS will merge and new combined API will be available. I think this new version will still be too early for prime time, but at least this time they might have more developers on their side.
Two, crazy high prices are just here because MBA execs cannot grasp why Steve can sell his shit for a premium price and they can't. After all Steve only has tons of quality apps, well polished UI, proper form factor (no 7inch bastard of a phone without a phone), sleek design and millions of devoted users. This will fortunately change as their stockpile numbers will start approaching US debt, prices will budge. Fortunately we don't need MBAs to get a clue or get smarter for it to happen.