Translation of classes, objects and content/design layers

Friday 26 September 2003 1:16:52 am

I have some trouble with this problem:
Where is the right level for translation?
I think that there is a design problem in eZ publish.
In effect you can (partially) translate objects, but non classes.
I have to translate a simple Select (Yes, I do this ...; No I don't) but it seems to be impossible: in the translation interface I see only the two options and I have only to select one in the original language.
I think that the translation now could be made at template level using the Enum Type (template belongs to new extension to have a little translation.ts file) taking care of the enum value with the i18n operator but this seems to be difficult to mantain and seems to break the content/design layers.
I think that "stable" data types should be translated at class level, taking care that the translator can't edit your class.

Any Suggestion?
Thanks in Advance

Daniele