How to deal with changes in an already translated artifact

[Philippe Luickx]

Hi,

We started implementing localization framework covering the main artifacts (articles, catalog items, portal,..). Creating initial translations works great and with the help of machine translation, we can speed up the translations quite a bit.

However, how do we best deal with artifacts that change after translations have already been done?

Let's say we have an article A in English. We translate it to another language, so we have article B.

If we then make changes A > A', what is the best approach (without TMS) to do B > B'?

Ideally I would see

- a new localization task being created whenever A changes (manually or automatically?)

- an interface that combines the article version comparison (green / red to highlight what changed between A and A') and the translation interface (where I can then manually change B to B')

- would it be possible for the machine translation to help with only doing translation for things that have changed? I know this is a bit of a stretch.

Thanks for your insights!

[JoefromTheCloud]

Hello Philippe,

I have been thibking about this for a while and working in HR and Knowledge Management for a while, I understand this.

For knowledge articles especially policies or longer documents, small changes can sometimes chnage the meaning, so partial translation can create inconsistencies and a bit of confusion. Because of this, I often recommend that you treat each translated version as a standalone article. Here anytime the English source article changes, even if it is only a word, the article owner uses “Request Translation” again so the full article is re-translated. Article versioning ensures the translators always work on the latest version if you are not using any MT.

Hope this helps! @Alex Coope - SN what do you think?