Localisation workflow using external translation application

Question

Hi everyone,If there is already a good answer for this question out there somewhere just let me know. Unfortunately, I haven't been able to find it yet.We're about to start translating all of our documentation in Robohelp 2017 into a few different languages starting with German. However, I can't find a good workflow to stick to. The one I've found in the Robohelp documentation doesn't quite cover it.Apply French language project settings by selecting French Language.Open an English topic, create a topic for the French language, and translate the content, including the topic title from English to French. (Do not translate topic filenames.)Create French tables of contents, indexes, and glossaries.Create a conditional build tag, such as FrenchContent.Apply the FrenchContent conditional build tag to French content and topics.Generate output for the French language.The main issue is that we want to use a translation application (Transit NXT) so we will need to export the source files for translation. For this I could use the following workflow:Apply French language project settings by selecting French Language.Create a new folder at the top level called French.Create a copy in the French folder of all the files and folders.Create French indexes and glossaries.Send French topic files, index file and glossary file for translation. Translator translates the content, including the topic title from English to French. (Do not translate topic filenames.)Overwrite French topic files, index files and glossary files with the translated copies.Create French tables of contents.Create a conditional build tag, such as FrenchContent.Apply the FrenchContent conditional build tag to French content and topics.Generate output for the French language.Does this seem the best way to do it and are there any translation steps that I'm missing?Thanks in advance for any help you can give me.Tom Jenks

Gesand · Answer

I use RoboHelp 11.0.4.291 and SDL TRADOS Studio 2015 Professional SR3 – 12.3.5262.0Iam the technical writer for software and I start the Robohelp-project in german, it is translated into serveral languages.I don't use multilingual projects because for some products we translate up into 8 other languages.For example product aaa_V9.0 is translated into 4 languages but next release aaa_V9.1 needs to translate into 7 languages.I use Robohelp and Trados since many years this way.RoboHelp-Projekts in "Responsive HTML5" an "Microsolft html"1) The folder with the RoboHelp-project has the name "product_DEU", the RoboHelp-project has the ending "..._DEU.xpj"2) I copied the whole folder including all sub folders and rename the new folder to "product_ENG" or "product_ITA" etc.3) I open the RoboHelp-project in the new folder and rename the RoboHelp-project (in german ) ".._DEU.xpj" to ".._ENG.xpj" or ".._ITA.xpj" or ".._FRA.xpj"4) All project-files will be rename, except *.hhc (content), *.hhk (index) and *.glo (glossary). These new files are empty. 5) In "Projectmanager" open content (Inhaltsverzeichnis) You see two files "..._DEU(Standard)" including your table of content and the new empty file "..._ENG".6) Delete the new file "..._ENG" and rename the standard to "..._ENG", after that it is "..._ENG(Standard)"7) You have to do the same for "Indes" and "glossary"8) Change the language in the project settings from german to english. (in german )TRADOS or Transit NXT (I think it works in the same way)9) I create a new Trados-project for every translation. "Product_V92_DEU_ENG" or "Product_V92_DEU_ITA"10) I import all sub folders with the files "...*.htm" to the Trados project. Trados can easily read the *.htm file, I had to do nothing else. For *.htm files Trados use the filtersettings "XHTML 1.1 V1.2"12) I do NOT rename any htm-file and the translator only see the text no link.13) To translate the table of content, index and glossary you need to translate the RoboHelp-project files *.hhc - content *.hhk - index *.glo - glossar For these files Trados needs a special filter, *.hhc and *.hhk are XML format files These filter settings are no standard in Trados and not in Transit NXT Perhaps you ask the support of Transit NXT to create filter settings for these files. I can give you the filter settings for Trados, may it helps to create filter settings for Transit NXT. In Trados the translater only see the words of the content or index, he can't overwrite the link.14) After translation I export the "sub-folders" with the translated files and copy it back to the new RoboHelp folder from 2)RoboHelp15) Start the RoboHelp project ".._ENG.xpj" and all files are in the new language and all links or hyperlinks are still fine.16) Pictures - If you use pictures in the help, you perhaps need to translate the pictures.17) If you have a titel in the output window you need to rename the titel (in german ) and compile the new help. I hope it helps you a little bit with your problem or to find you own way to translate RoboHelp-projects.Best regards JuttaP.S.TRADOS - filtersettings for *.hhc + *.hhk + *.gloFor Trados you have to copy it to a file with the ending <*.sdlftsettings>. In Trados you have to import it for each new project again.TrueglossaryTrueTruefalsefalsefalseglossdefTrueversionTruefalsefalseglosstermTrueTruefalsefalseglossentryTrueTrueTruefalseglossaryTrueTrueTrueTrueyesTrue//section/@name//glossentryyes//glossdef//item/@nameTrueTrue//glosstermtocTrueindexTrue//glossaryTrueXML v 1.3.0.0(^[\d\D]*\.[gG][lL][oO]$)|(^[\d\D]*\.[hH][hH][cC]$)|(^[\d\D]*\.[hH][hH][kK]$)*.glo;*.hhc;*.hhkRobohelpRobohelp-DokumentRobohelp-DokumenteRobohelp

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded