Trouble importing XML file from SM

[Roel De Coninck]

Hi all,

I'm new to Mnemosyme and happy I found this promising project. 

I installed the 1.2.2 version (Windows 7, 64bit) and tried to import an XML file that is the result of a SuperMemo 2008 export. 

Whatever I tried, this did not succeed.  At first, I got error messages but I was able to deviate the line number from it and found strange symbols in the xml file.  A few iterations and I got rid of the errors. 

But now, nothing seems to happen.  I thought the size of the xml was a problem and exported only a small portion of my SM database (tried with 1 note and about 100 notes): no errors, no response, nothing seems to happen.  

I also tried version 2.0 beta 3 and beta 4, but the problem in these versions is that when I click on import, I can only import .mem files, no xml files.  Maybe I'm doing something wrong? 

I really want to get started, but only if I can keep my current SM intervals.  So I did not even try a Q/A import as the Q/A exports of SM do not contain any learning information. 

Thanks for your help,

Roel

[Peter Bienstman]

> Hi all,
> I'm new to Mnemosyme and happy I found this promising project.
>
> I installed the 1.2.2 version (Windows 7, 64bit) and tried to import an XML
> file that is the result of a SuperMemo 2008 export.

Problem is that I did not write the supermemo importer myself, and the person
who wrote it no longer seems active. I do plan to resurrect this fileformat
importer myself, but it will only be after 2.0.

In any case, if you could privately mail me your xml file, that would be a
great help for when I get around to writing a new importer.

Thanks!

Peter

[Roel De Coninck]

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.  

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. 

It will take some time to get into the project, so the usefullness will depend on your planning.  What's the planning for version 2.0?  And when do you think you'll be able to have the updated importer?  

btw, no problem to send you my .xml file.  I will wait for your answer first. 

Thanks,

Roel

[Peter Bienstman]

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