resolve wrote:

Personally I find all the multimedia support a bit of a gimmick

I'd agree, if it wasn't for animated stroke-order diagrams, which I think is sufficient reason to make it a requirement.

resolve wrote:

It gets complicated when you try and support 4 different platforms (Anki runs on Qt, the web, cell phones and also Emacs), though.

Where can I get the emacs version?!

yorkii wrote:

all i know is ４文字熟語 and the difference between 縁 and 緑. Im not too hot on computers tbh... hehe so what does that mean?

i have been doing a simple

<IMG SRC="C:\Documents and Settings\Administrator\Desktop\Image Dictionary\***.jpg"> type thing.

I'm pretty good with computers and I still can't get it to work.  The Anki shortcut on my desktop has "C:\Program Files\Anki" under "Start In," so I would assume that would be the "current directory," but I have tried putting images in:

C:\
C:\Program Files\Anki
C:\Documents and Settings\<username>
C:\Documents and Settings\<username>\.anki

all to no avail.
It would be nice if the image tags allowed HTTP addresses.  That would make the decks much more portable and allow the cards to be correctly displayed on the web version.

I may be being stupid here, but how do you import entries from Mnemosyne? I was going to try that out, there's an Import menu item, but it seems to be grayed out....

resolve wrote:

Cmaj7: thanks for the report. Please email me the file you're having trouble with so I can check it out for you. My email address is at the bottom of the Anki pages.
.

Thanks, I manged to reformat the file in a way that fits Anki, using openoffice and the plugin that splits words separated by a space into two distinct colums. I couldn't find out wich word was giving troubles... so I just deleted a whole extra column and it worked fine!

Looks like my router's died. I'll be home in two hours (still at work), and I'll reboot it then.  Avoid cheap routers in Japan!

I don't understand what you mean. Are you taking "properly" from the fact that wikipedia says ruby characters are either above or to the left? I have seen books with furigana below the text, too. The reason Anki displays furigana below the kanji rather than above it, is because I want to encourage the user to read the kanji first before reading the furigana. I found when it was the other way around, I had a tendency to just read the furigana before answering the question.

The web version will let you customize the layout further in the future.

The standalone version is somewhat limited in its ability to do complicated presentation like aligning ruby characters to each kanji, due to limitations with the HTML rendering engine in the toolkit.

No offense taken :-) I just wasn't sure what you meant.

Anki 0.3 is moving to a semantic representation of data, where cards are just a description of how to represent that data. This will make it very easy to customize the display format into whatever way you wish. Should be ready within a few weeks.

Crude.  I'd say it's kicking 尻.

Thanks for all your hard work, resolve.  Anki is already miles ahead of everything else out there.

JimmySeal wrote:

Crude.  I'd say it's kicking 尻.

intentionally so. the phase is kicking ass, not "rear" or "bottom".

yorkii wrote:

JimmySeal wrote:

Crude.  I'd say it's kicking 尻.

intentionally so. the phase is kicking ass, not "rear" or "bottom".

<consults a dictionary>  Ok, I see now.  Some rubi text would have been a good call there.  尻 can also be read as けつ, but unlike 穴, it can't be mistaken for あな.

Hi Yufina,

There's a bug in the importing in the latest version. I'm rewriting all the importing for the new version, so it should hopefully be fixed soon.

To all: thanks for the motivation :-)

I've pretty much put aside Mnemosyne in favour of your app. Just thought I'd let you know that I'm in love with your program, resolve! Keep up the great work!

P/S: Is it possible to have some sort of quickie HTML button around? E.g. a 'Bold' or 'Italic' or 'Colour' button? That would expedite text formatting by a whole lot. (Though HTML tags may be familiar to us, it's quite cumbersome to edit them, especially with regards to the current Edit Deck interface.)