If the page doesn't take too long to load, it can be a good alternative of rikaichan

Wow, this is amazing! I really like this program. As I don't use firefox, this could be extremely useful!

First I would just like to thank everyone for their ratings and comments, they've been very helpful!

deign wrote:

If the page doesn't take too long to load, it can be a good alternative of rikaichan

Unfortunately the file sizes of the pages are fairly large at the moment, especially for longer texts. I will do some optimization that should make them much more smaller.

Tolerence91 wrote:

I was also thinking it might be a good idea to have a way to look up the kanji, especially is essential to understanding a word or if the kanji is an old obscure one

Thanks for the suggestion. I've been focusing on adding grammar support to the program so I haven't given much thought to supporting kanji look-up. But I do see why it would be useful, I'll just have to think of how I can fit it into the interface.

sweet stuff

jettyke wrote:

How is it better/different than yomichan or rikaichan?

The main difference from rikaichan is that this program provides more explanations of grammar (specifically auxiliary verbs and functional expressions). It also automatically identifies the words in the text for you, rather than just finding the longest matching word nearest your cursor.

belton wrote:

At the moment you seem to have static (hand-coded?) pages. I'd be interested in how it would cope with pasted or imported text. How accurately it will be parsed, the parts of speech detected and the links to definitions, Tae Kims Grammar  and Wikipedia etc. auto-generated.

Actually these pages are being generated automatically. The only parts currently added manually are the explanations and Wikipedia links for the proper nouns (although I hope to eventually do this automatically as well). I'm just showing these three sample pages at the moment because I wanted to collect feedback on the way  that the program is displaying the grammar explanations.

Of course the program does not support everything yet, especially since automatic identification of some functional expressions can be very difficult.

belton wrote:

In your definitions you refer to plain polite form. (which I think of as non-past polite form). Usually I see ~masu form called "polite" and dictionary form called "plain".  So At first I wasn't quite sure what you meant by "plain polite"

Thanks for pointing this out. You are right, non-past would be better.

belton wrote:

Graphically it looks fine. Although I find the thin underlines a little bit distracting. Maybe it might be better as a hover turning on the thin line. At the moment the hover turns it off.

I originally thought to display the underlines so that people could easily see which parts of the text had explanations, but maybe it would be good to have a couple different styles to choose from.

Last edited by gh123 (2011 May 15, 2:47 am)