I published a new version of the application.

It adds three different open source Japanese fonts to address AzureBlue's problem. I found them on http://www.freejapanesefont.com/tag/open-type/.
We can discuss about providing other fonts with the app but I cannot provide more than 3 because each of them weigh 2mo and I wanted to provide one for each type : Mincho, Gothic and Maru.

I also optimized the new version for the load time so, Creamyhorror, if you could give me some feedback from your side, I would appreciate it.

Next things that I noted from this post that could be improved:
- Furigana management (display them correctly or strip them altogether)
- Analyse the idea of providing some flexibility on the Anki card creation (at least the deck name)
- Provide some more navigation gesture to switch between chapters (swipe left/right?)

The new version is going to be available in a few hours on the Play store.

I uploaded a new version for the navigation gestures.

You can now swipe left and right to change chapters or use the volume button to do so.

Everything is configurable in the settings and there is an added possibility to change the effect of the volume buttons to do a page up and down instead.

Again, new version to quickly address the last concerns :
- Furigana are now stripped from the text;
- The anki deck name is now configurable in the settings.

These are just quick fix for the two problems. I will probably add the possibility later on, to display furigana properly and for now, you have to type the deck name correctly if you want to target an existing deck otherwise it will create a new one. I want to add an autocomplete feature on the text box so that you can see what deck are available from Typhon without having to switch.

Been meaning to reply, sorry for the delay ZorgBlub.

I installed the version you released on 4 May - had to uninstall and reinstall to get it to work without crashing. The book loading time seemingly hasn't improved. I only tried it on a book without chapters, though.

Still appreciating the work you're putting into this

aw… too bad!

I just made some general optimizations for the overall app. I saw some improvements on my tablet but I guess I won't get out of this one so easily :p

Anyway, I'll have a look to see how I can optimize this in particular, no worries.

There's like one and a half things stopping me from switching from Play Books to this, vertical rtl text support and the app not going into immersive mode, or whatever they're calling it nowadays where the soft home buttons, status bar and the like move off the screen. One slight issue is that the selection doesn't vanish when the dictionary popup is closed. Other than that, awesome job!

Typhon runs super smoothly on my tablet (Android 4.4) but painfully slow on my phone (Android 5.02).
Somehow AnkiDroid on my phone does not recognize Anki deck created by Typhon as legit. Any ideas?
Anw, thanks for your hard effort!

(2016-05-10, 1:14 am)MarseSnorty Wrote: There's like one and a half things stopping me from switching from Play Books to this, vertical rtl text support and the app not going into immersive mode, or whatever they're calling it nowadays where the soft home buttons, status bar and the like move off the screen. One slight issue is that the selection doesn't vanish when the dictionary popup is closed. Other than that, awesome job!

The vertical text support is something I will look at because it seems it is something people want. I still have yet to find a way and to understand how it can work with the pop-up because I wouldn't want to close after each lookup to proceed with the reading.

The immersion mode and the selection remaining after the closure of the pop-up are easy to fix so I will include that.

(2016-05-14, 5:44 am)ilovekazehikaru Wrote: Typhon runs super smoothly on my tablet (Android 4.4) but painfully slow on my phone (Android 5.02).
Somehow AnkiDroid on my phone does not recognize Anki deck created by Typhon as legit. Any ideas?
Anw, thanks for your hard effort!

Yes performance will be my priority for now. I use a pixel c tablet so that's why I don't suffer from them but I can see on my Nexus 5 that even the lookups are slowish.

About the deck, do you see any kind of error or the deck simply isn't there? Can you check if you have a value for the deck name in the settings?

(2016-05-15, 11:11 am)ZorgBlub Wrote: The vertical text support is something I will look at because it seems it is something people want. I still have yet to find a way and to understand how it can work with the pop-up because I wouldn't want to close after each lookup to proceed with the reading.

The immersion mode and the selection remaining after the closure of the pop-up are easy to fix so I will include that.

Awesome, looking forward to whatever you come up with. Maybe have the support as a switch so it closing to continue is the user's choice, or maybe have the window take up about a third of the screen coming in from the right. It might make it easier if you can use a Google chrome web view or something because it supports at least one of the vertical css rules.

(2016-05-15, 11:13 am)ZorgBlub Wrote:

(2016-05-14, 5:44 am)ilovekazehikaru Wrote: Typhon runs super smoothly on my tablet (Android 4.4) but painfully slow on my phone (Android 5.02).
Somehow AnkiDroid on my phone does not recognize Anki deck created by Typhon as legit. Any ideas?
Anw, thanks for your hard effort!

Yes performance will be my priority for now. I use a pixel c tablet so that's why I don't suffer from them but I can see on my Nexus 5 that even the lookups are slowish.

About the deck, do you see any kind of error or the deck simply isn't there? Can you check if you have a value for the deck name in the settings?

I can see the deck but AnkiDroid always encounters error when opening it and quits.  

OK, I've found the solution to my problem. I changed the deck name into standard Latin one word,  (i.e. "Typhon") Now AnkiDroid recognizes the new deck I've created but I guess I have to lose the old deck (changing name doesn't help)

Few things I would try to recover the deck:

- check if ankidroid is up to date;
- use the "check databse" of ankidroid;
- try synchronizing the deck on anki desktop and if necessary do a check db there.

The API I use is the one provided by ankidroid so that's why I suspect that it is not up to date. Otherwose either I have misinterpreted the specs of the API or there might be a bug in it. Because the code seems fine after reviewing it for your problem.

Were you ever able to open the deck or it was unusable from the start?

(2016-05-19, 2:58 pm)ZorgBlub Wrote: Few things I would try to recover the deck:

- check if ankidroid is up to date;
- use the "check databse" of ankidroid;
- try synchronizing the deck on anki desktop and if necessary do a check db there.

The API I use is the one provided by ankidroid so that's why I suspect that it is not up to date. Otherwose either I have misinterpreted the specs of the API or there might be a bug in it. Because the code seems fine after reviewing it for your problem.

Were you ever able to open the deck or it was unusable from the start?

I'm sure about no. 1 but can't check other options because I deleted the failed deck lol
And it was unusable from the start.

OK good to know, I will try and reproduce the bug otherwise it will have to wait until someone gets it.

Apart from that I have a new release ready for the immersive mode and the removal of the selection after the pop-up is closed but I cannot upload in the country I am currently in because the play store is banned there so I guess it will have to wait for the end of the trip :p