Hi karansheel,When the destination language copy (page, asset etc)
already exists, "AEM treats this situation as an update translation. A
launch is created and a copy of the page is added to the launch, and
included in the project." This functionality is same for single
language as well as multi language projects. For details please refer to
. Managing Translation Projects
Hi,In the effective "Translation Integration Configuration" for the dita
file, please go under Assets tab and check "Translate Assets" option.
Once done, please try the workflow again and let us know your
Hi again,As of now, translation workflows do not look for templates.
Therefore, please use Experience Fragments directly inside pages or use
i18n. Refer to Translating Editable Template for more details.
HiIt seems that the Experience Fragments are used inside editable
template. For translating content, please use Experience Fragments
directly inside pages and not through templates. Let us know if you face
issues with the same.
Hi,This observation is due to Java's Locale class where "id" is replaced
with "in". As a workaround, please use dictionaries with language in_id.
In case you face more related issues, please let us know.
Hi,Reject functionality would initiate update translations, if supported
by translation partner. Once a user rejects translation objects,
translation partner will be notified with the same. If you are working
with a partner, please request your translation partner regarding the
support for reject workflow. If you are building your own connector or a
partner, this process is initiated via
updateTranslationObjectState.Also, as this needs reading comments and
updating translations accordingly, i...