>>> Every object is translated to the same language.
>>> But the same caption doesn't translate the same in all places.
>>> For example, when translating to Portuguese:
>>>
>>> The Caption «Quote», can have different Portuguese Translations depending on the Context.
>>> ...
>>
>>I don't see, why You use the Class as the key. Why do You not simply a "Text-Key"-Property
>>to Your classes and use this. like 'Quote-Long', 'Quote-short'. By this You could even use the
>>same translation for several purposes if You like
>
>
>Well, I don't want the developers to be worried with creating Context Keys each time they write Texts in Captions, Status Barr Text and ToolTips.


Yes, sorry I already followed the thread further down.

On the other hand someone definitely needs to worry about the context and will have to tell the Developer "Please do use this class" (by this implicitly defining the context). If so, they also could
get Context-Key's for specific objects.

To me this sounds highly performance problematic and somehow complicated.

But certain tasks sometimes demand certain actions that are not easy to see from the outside.