• State Not Answered
  • Replies 3 replies
  • Subscribers 47 subscribers
  • Views 2952 views
  • Users 0 members are here
Options
Related

preTranslation functionality in SDL

Akheil Jain

We are using the preTranslation feature available out of the box in Knowledge center, to do our translation compares. The preTranslation tags added by this functionality are not valid against our DTDs used in our XML editing tool. Is there a way for the editing tool, in this case XMetal to use a different set of DTDs compared to Knowledge Center? I see that there are two set of DTDs one under the Client Config folder and specific to the XMetal version and another under the DocType folder which are used by KC. Both of these DTDs get synced down to the users workstation, but the Doctype folder DTDs seem to take precedent. Would anyone be able to shine some light on this issue? 
Rate translation
×
Suggest better translation
×
  • 0
    Hey Akheil

    Just to make sure you aware: as of the KC 2016 release, the pretranslation feature got deprecated. It still works in that release "as is", but there are no plans to improve it nor further support it.

    That said, we don't expect that pretranslated files are edited in an XML editor. By definition they are invalid DITA files. Editing pretranslated files in an XML editor entails the risk that the complex pretranslation structure gets broken or modified, resulting in an incorrect translation.

    The expected translation process is that such pretranslated files are processed in Translation tools/Translation memories, and that after translation, they are are imported back into KC. When the import of pretranslated files happens, the source content is completely removed, and the pretranslation tags are removed from the pretranslated elements.

    Hope this gives a bit more context.

    Best regards
    Kurt
  • 0 in reply to Kurt Van Deun
    Hi Kurt,
    Appreciate your response and we are aware it's deprecated functionality, we face some unique challenges here, as we have a in house translation team and we need to compare different languages side by side. The pretranslation functionality seems to be a good fit as it allows the translator to translate in context the piece of text that need to be translated and not translate the entire document again. For this reason we need to open the pretranslation file in an editor.
    Akheil Jain
  • 0 in reply to Akheil Jain
    Ah, I understand. I have no quick workaround apart from not checking out the translations, but just opening them as standalone topics without DTD validation in the XML editor. Or any editor. And after making the translation changes, import them in KC. If the structure got broken by the translator, then the import will (correctly) fail.

    Maybe there are other customers who use pretranslation in combination with an XML editor...

    Best regards
    Kurt