On Sunday, August 28, 2011 09:23:46 PM Roel De Coninck wrote: > A completely different argument may be the fact that when version 2.0 will > 'officially' be released, Mnemosyne will get a peak in attention from SM, > Anki and other tool users. Wouldn't it be a petty not to have a working > importer for other formats than the Mnemosyne own format? A lot of > potential new users, like me :-), will start by trying to import their > database. They will quickly be disappointed and never come back to try > Mnemosyne.
Yes, that's indeed a valid argument. On the other hand, people have been waiting for 3 years now for Mnemosyne 2.0, and including all file formats will be several more months delay. As a workaround, people can always keep importing their data using 1.x, and then import the 1.x mem file in 2.0. In any case, the release notes will come with clear warnings about this, so people who use external importers a lot can decide to wait for a next version. > I'm a modest python user myself, maybe I can help a hand? I will not be > able to free much time , but maybe it's enough to help. That would of course be much appreciated. BTW, I just remembered that the current SM importer ( http://www.mnemosyne- proj.org/help/importing.php ) is for the text format with learning data from SM 2006, not for an xml format... If you want to get started on this, I can give you a few pointers about what to pay attention to and where to start (but let's do that on the devel mailing list). Cheers, Peter -- You received this message because you are subscribed to the Google Groups "mnemosyne-proj-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mnemosyne-proj-users?hl=en.
