Merge doesn't work as expected

[Marcin M.]

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)

Btw. maybe the duplicate check could be possible for the second (answer) field too?

[Peter Bienstman]

> -----Original Message-----
> From: mnemosyne-...@googlegroups.com [mailto:mnemosyne-
> proj-...@googlegroups.com] On Behalf Of Marcin M.
> Sent: 10 October 2014 21:22
> To: mnemosyne-...@googlegroups.com
> 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

[Marcin M.]

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.