And my idea about duplicates was: (sorry for this primitive example, but nothing better comes to my mind at the moment)
a user has a card "cat/die Katze". He wants to add a card: "a cat/die Katze". Expected outcome: the duplicate guard should shout that there's already such a card, but with a different quesiton. Actual outcome: the user will have 2 cards, which are semantically the same. In case when the QA format is Q:native language, A:foreign language you'll rather have difference in the Question field than in the Answer field. On Saturday, October 11, 2014 9:12:28 AM UTC+2, Peter Bienstman wrote: > > > -----Original Message----- > > From: [email protected] <javascript:> [mailto:mnemosyne- > <javascript:> > > [email protected] <javascript:>] On Behalf Of Marcin M. > > Sent: 10 October 2014 21:22 > > To: [email protected] <javascript:> > > Subject: [mnemosyne-proj-users] Merge doesn't work as expected > > > > When merging two cards, the old one is "deleted" and the new card > contains > > only the newly input content. (at least it's what I'm experiencing) > > Bug confirmed, I'll fix this for the next release. > > > Btw. maybe the duplicate check could be possible for the second (answer) > > field too? > > At the moment, the philosophy behind 'find duplicate questions' is to find > the duplicate questions, so that you are never in a situation where there > is ambiguity if there is a question. > Feel free to open a uservoice request for your feature request, though, so > that I can see how popular this is. > > Cheers, > > Peter > > -- You received this message because you are subscribed to the Google Groups "mnemosyne-proj-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mnemosyne-proj-users/c329584b-1ac0-499e-b9dc-9981e1ff01ed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
