This seems to be exactly what happened. The Supermemo exported text
file has kept the Unicode tags embedded within in the text, and these
also show up on display when imported into Mnemosyne.
Patrick, do you know if there is a way to force Supermemo to export
only the Japanese text which is
How about a way to manipulate the exported text (using replace) so
that only the tags which designate the Japanese remain? It sounds
impossible to me, but I thought I'd ask. Here's one Q and A field from
a text file (I already replaced lt; with and gt; with )
Q: FONT face=Arial
Unfortunately, because of the way SuperMemo works, there is no such
option. SM stores everything as HTML-- even the Unicode characters
themselves-- and so the Mnemosyne importer has to do a special trick
just to even recognize the SM Unicode.
Regards,
Patrick
Unchecking the allow HTML results in a text file with question marks
instead of Japanese (which is what I am using SRS for). It just shows
up as random
But leaving the HTML in results in a text file containing a lot of
gibberish too, as cited above.
On Nov 27, 7:29 pm, Peter
On Thursday 27 November 2008 13:06:56 [EMAIL PROTECTED] wrote:
Unchecking the allow HTML results in a text file with question marks
instead of Japanese (which is what I am using SRS for). It just shows
up as random
But leaving the HTML in results in a text file containing a lot
(Note that I'm not a user of Supermemo, and I did not write the importer or
that decription on the website myself).
What happens if 'allow html' is unchecked?
Does the exported file already contains lt; or are the tags still fine there?
Peter
On Wednesday 26 November 2008 23:02:37 [EMAIL
Yes, the gibberish is present in the text document I exported from
Supermemo. I tried replacing all the lt with and all the gt with
. Then I imported the file into Mnemosyne, but unfortunately there
are still a lot of tags present in the Q and A portion of the
flashcard. From what I can tell,
I can't improve the importer but I can provide some more details on the
problem. The problem is that when SuperMemo decided to add Unicode
support, they hacked it on using HTML. So, all Unicode is displayed in
SuperMemo as HTML rendered through Internet Explorer. When you export
from
