Issues using 'node_clone' together with 'localizer' module

Not sure whether this problem is more related to the localizer or to the node_clone module, I'm now reporting it here:
I'm using node_clone together with the latest version of localizer (5.x-3.x-dev) and I'm experiencing the following problem:
I invoke "Clone" on an arbitray node and presented an edit screen with the cloned node. So far, so good. Not changing anything in the form, I press save and I'm running into the following error message:

A translation for English language is already present in this set.
Remove the translation Titel of the cloned node from this set before proceeding

The only way to get the node saved is to select a different language for the node to be saved. If your set already contains nodes for all languages present in our system, you are not able to save the node at all.
The currrent behaviour does not allow you to create a clone with the same language as the original (which is the most common scenario if you clone a node IMHO).

IMHO it would be much better if a new set were created if you clone a node, containing a node in the same language as the original node. In case you need a different language, you still simply could select a different language from the dropdown menu (and optionally add that node to the set the clone was derived from afterwards again, if that is your requirement).
Currently, you have to a) remove the clone form the set b) (optionally) change the language from the set and c) add the node to an existing set (or start a set with the cloned node as base version).