Localization framework Knowledge Article Machine Translate - Wrong language

[FredricS]

Hey!

I'm trying to use localization framework and dynamic translation to translate knowledge articles. Basically I want to tasks for all new KB articles and want to be able to bulk translate all the current knowledge articles. And of course, build a task management around it, so people approve the translation and corrects it. 

All our knowledge articles are written in Swedish but their language is set to English (hence, we didn't have localization framework before). So when I try to translate them, it tries to translate from English and cannot translate the Swedish text. 

The language field on the knowledge base articles are locked and cannot be changed and when I'm trying to translate KB articles to Swedish (from Swedish but its registered as English) it doesn't create a Localization Task. It only creates a LRITM (Localization Requested Item) but then it cannot be translated or approved. I've also changed the settings on the Knowledge base, so it creates automatically tasks when it's a new KB article but it doesn't work when I use the "request translation" button for KB articles. 

How do I solve one of these problems? 😄 

[Alex Coope - SN]

Hi @FredricS,

So, it sounds like a few things need to be done to sort this:

1.  To be able to change the language of the articles (which is required to be able to translate them properly via any third-party) you would need to un-publish all the articles to then be able to change the language value. You should be able to do this via a "fix script" to mass un-publish the articles, then update the language value. Have a look at this blog post on how I show how you can call the publish methods of KB articles.
2. To translate articles in bulk there's two ways you can do this:
   • In the Localization Framework you can do this via the list view on the [kb_knowledge] table.
   • Install the Localization Workspace which will let you do it centrally from here. It still runs LF and generates LRITMs / LFTASKs but it groups every thing that's requested at that time into a Localization Project. The bulk scenario is one of the key reasons we created this Workspace.
3. The "auto generation" feature you are referring to, is actually from an old (Madrid days) feature called "Translation Management" which doesn't apply any more I'm afraid.

If after all of that, you are finding that an LFTask is not being generated, this suggests you don't have the correct "setting" created in the Localization Framework for the artifact. It should create an LRITM (your request) with a child LFTASK (the actionable activity).

For future reference, it is always best-practice to ensure that any article is always created in the correct language from the onset to avoid these kinds of challenges (regardless of whether you are using the Localization Framework or not),

Many thanks,

kind regards