Translated content using the file system

Hi,

My role as a DITA tools engineer has not included performing workflow related tasks. I am familiar with object levels, and I have some familiarity with the web services API. At my current job I have a task to research using multiple languages. There are no plans yet to use a translation management system.

Should it work to change the status of objects, which have translation management enabled, to "To be translated" send an export the report. Create translated copies of the exported files changing xml:lang and keeping the same GUIDs. Then use Import translations?

What I have tried is to add status transitions and inbox actions to add a Change2ToBeTranslated action and status transitions from Review to To be translated, but when I try to generate a workflow report, the transition does not appear.

In the web client there is a recycle symbol next to the status transitions. Is there some action that I need to perform?

Parents
  • Hi Kendall - the short answer is that you don't need a translation management system to make localizing content out of the CCMS efficient. You just push the English content to translation then import the translated objects. At FICO, we translate entire publications only. Here's what we do:
    "Push" the objects to translation using the out-of-the-box translation processes in the CCMS > export/download the files for translation and send them to the translators > change the status of the objects to "In Translation" (using the web UI Inbox - very easy) > Import the translations > build the output > work with the translators to make any outstanding fixes until the output looks ready to go.
  • Hi Elizbeth. Thank you! It is good to know that it should work. I will have to do more experimentation to see why I am unable to to complete the push to In translation from the web client.
  • You are welcome! Dave can confirm, but you should probably log a support ticket to help get your translation workflow set up.
  • Thanks. Since I only have 2 simple questions, I am hoping those can be answered.
  • No one knows? Is Translation Coordinator the same as Translation Service? Also, does the recycle symbol in status transitions in the web client indicate that something needs to be done? What would that be?
  • I am probably not the person to answer this, so I'd appreciate it if someone would correct me.

    It is my understanding that the Translation Service is your translation management system (SDL's TMS, WorldService, XTM, etc). The Translation Coordinator is the person pushing the objects from LCA/Knowledge Center/Tridion Docs to the translation service. And that seems to be what the documentation for LCA explains.

    I do see a recycle symbol as part of the status transitions icon in the Web client (Settings menu), but I'm not sure where else you are seeing this icon. In what screen of the Web client does this appear? The only other "recycle" symbol I'm seeing is the refresh icon.
  • Hi. Thank you for your answer. There is a section in the documentation describing configuring the Translation Service role. So, I think you are right. And, I guess the recycle symbol in the web client for Status Transitions is always present and doesn't represent a status. So, as far as I can tell, I have everything configured as described in the documentation. When I try to create a translation report (all the objects are in "To be translated" state) it won't let me finish, because I have to have the "Translator" field filled. I have no idea how to specify a value for that, so I am stuck at the moment.

    The documentation "Integration requirements for Content Manager and File System" refers to a dedicated user (typically ServiceUser) having the role TRANSLATORSERVICE. I've assigned myself that role, but I don't appear in the drop down for "Translator" (it is empty).
  • I got help from support. Details that were not in the documentation were: A user with role "Translator" is required to start the export for translation. Export happens in 2 steps. The files have to be in released state before the other languages can be generated (the first step). This is done from the Translation button in the web client. The 2nd step exports the files.

    The report was started from the publication object in the web client.

    In the translation report window, you have to click in just the right place on the very bottom of the page to make the report expand (repeatedly click on the words until the window opens. Then if you click the checkbox next to files, above, it selects the files in the corresponding state.

    Aside from inbox definitions (Change2Released and Change2ToBeTranslated) and status transitions for Translator and TRANSLATORSERVICE, the file x:\InfoShare\Web\Author\ASP\XSL\WorkflowReportConfig.xm has to be modified to include status transitions.

Reply
  • I got help from support. Details that were not in the documentation were: A user with role "Translator" is required to start the export for translation. Export happens in 2 steps. The files have to be in released state before the other languages can be generated (the first step). This is done from the Translation button in the web client. The 2nd step exports the files.

    The report was started from the publication object in the web client.

    In the translation report window, you have to click in just the right place on the very bottom of the page to make the report expand (repeatedly click on the words until the window opens. Then if you click the checkbox next to files, above, it selects the files in the corresponding state.

    Aside from inbox definitions (Change2Released and Change2ToBeTranslated) and status transitions for Translator and TRANSLATORSERVICE, the file x:\InfoShare\Web\Author\ASP\XSL\WorkflowReportConfig.xm has to be modified to include status transitions.

Children
No Data