Proof of concept for automatic translation of a site #63
Assignees
Comments
stoerr
changed the title
stoerr
added a commit
that referenced
this issue
Mar 1, 2024
Implementation of #63 . A quite basic interface to trigger an automatic translation is at http://localhost:4502/apps/composum-ai/components/autotranslate/list.html allows automatically translating a page tree in one go. It currently assumes that it's a live copy of the original language (though that'd be easy to remove) and cancels the live relationships and replaces the texts by it's translation. Documentation is in featurespecs/8AutomaticTranslation.md . To create a translate it's necessary to create a livecopy of e.g. /content/dam/wknd/en , /content/experience-fragments/wknd/language-masters/en , /content/wknd/language-masters/en and autotranslate them in that order. For the normal site /content/wknd/de again the livecopy mechanism can be used. Currently the translation is done for properties that are "obviously" text (have whitespaces and letters) and for some hardcoded property names like jcr:title etc. The paths are changed as well to the corresponding paths in the translated language. It's not 100% clear whether using live copies for the different languages makes sense or if we just use copying. If the page is not too long all it's text fragments are translated in one request. That improves speed and likely the translation quality. We make provisions for later translation updates: the original and machine translated text are saved, so that we can: - automatically recognize where translations have to be updated because of changes in the original text - possibly support updating the translations by trying to have the AI replicate any manual changes when re-translating a changed text
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We create an automated way to translate a whole site (AEM, Composum as a second step).
Basic idea: the other languages are a live copy of the basic language. The inheritance is broken whereever a text property is found that is translated. That way the translation can be updated later via the livecopy mechanisms. In #61 we created a translation prompt - that can be used to re-translate the properties, or the automatic mechanism.
The text was updated successfully, but these errors were encountered: