maybe I'm wrong but the content should be delivered by the backend. As far as I know the portal sends also the language of the user to it and the backend should send the content in the appropriate language. This shouldn't be done by VC.
Thanks for your answer. But I'm talking about the worklist of strings to translate in the Portal Content Translation menu, it is possible to translate labels and metadata, but it doesn't appear the text of HTML objects.
Do yoy know how to add this string on the worklist?
I see. But I'm afraid this is not possible for VC models. For CE there is a translation tool but not for 7.00 / EHPs or lower versions. There is a workaround for this but to be honest it is not a nice one. To be more specific: there are 2 workarounds:
1. You may create a VC model for each language you like to support. In the portal create a role for each language refering to the matching VC application. Via different desktops and desktop rules you can now decide for which language to choose which desktop.
2. Another option would be to have a formular for each label in your model. You need to have a user data object in your model. Therein you can find text field named 'LOCALE'. This will provide the language the user has set. Via IF you can not change the label of each part in the model.
Both of these options are not really comfortable and may result in huge effort in case of modification done later.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.