Versions Compared

Old Version 11

changes.mady.by.user Jules DELEUZE (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Jules DELEUZE (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction

The general principle of "duplicating" an entity in a context different from that of origin is called "declination".

...

All the translations of the same instance are presented in a "translations" tab accessible from the visualization action.

Prerequisites for translation

To be able to translate content, you must have the following components installed:

  • an object to be translated must inherit from the object contentobject at least the following information:

    • property master

    • property lang

    • property mediagroup (not required)

    • property media (not required)

    • property notranslation (not required)

  • the product plugin WXM_Mediacore must be enabled and the parameter isTranslationActive must be set to yes

Do a translation

In the back-office, the "translate" functionality allows you to easily perform a translation from the visualization of an object:

...

then select the language in which your object should be translated.

...

Ignoring the principle of translation

It is possible to ask the system to ignore the notion of language on an entity. For example, as part of an object storing images, these are not necessarily language-specific (no text displayed) it must therefore be the same body for all languages.

...

  • the translate button will not appear in the back office

  • an error is raised if you try to translate it with the action datatranslate

Warning

Caution

The value of the lang field will always be filled with the value of language of creation. Unlike the media field, the system does not handle objects whose lang property is empty.

Updating of allocations

...

During the translation action, the system creates a new object for the selected language context by duplicating the source and changing some properties automatically:

  • the language will be the target language

  • if the object to be translated is linked to other object instances via the attribution concept (child, childmulti) and these objects are also translatable, the system will automatically retrieve equivalent translations to update the property

Warning

Caution

If no matching object is found in the desired context, the property will be empty. This implies that if the property is required by its structure configuration, an error will be removed and the translation action canceled. (see article on standard errors).

Warning

Caution

We don’t do a cascade translation: if you want this kind of behaviour you need to customize it.

Manually configure a property during translation

You can manually overload a property during translation.

...

java.util.HashMap properties to force properties to force

Standard errors

When translating from dataview, errors are displayed via the standard popup.

...

  • associations must be translated before translating the requested object

  • the error is raised by a structural obligation. If this obligation is only functional, you can create a facet to render it mandatory only as a back-office contribution

  • Customize the field to manage a default value.

FAQ

Why is the Translate button not available on my item or a message tells me that the feature is not available?

...