Yes, the wizard works correctly as far as I can see. The problem is perhaps more obvious with tagging for example (default XWiki.TagClass) ; if you want to tag the content of the same page differently depending on the page translation you have to add a TagClass instance for every translation and somehow bind them to translation in question(?) So is there a reason why the object's properties should be language independent? These are fundamental questions for me when planning the structure of my xwiki-based translation portal by no means impassable obstacles. Before fixing the custom class structure I would anyway very much like to hear your thoughts and developers' plans if the logic is going to stay this way in future releases. Thanks! Petteri