3 Replies Latest reply: Jul 28, 2014 4:42 AM by RoboColum(n) RSS

    English content to be translated to French

    prologicfirst

      I have created a help of a product in English, using Robohelp11. I need to distribute this help to a few people who know only French. How do I get the entire help translated to French using Robohelp11?

        • 1. Re: English content to be translated to French
          RoboColum(n) MeganK

          You have a number of options and plenty of questions that need answering:

           

          • Is the translated content to sit in the same RH project?
          • Will you be doing the translation?
          • If someone else is doing the translation, what tools will they be using.
          • If they are not using RoboHelp, how easy will it be to bring that back into RH?

           

          Try looking at the following link for some pointers. It still applies for RH11

           

          Generating help in multiple locales using Adobe RoboHelp 10

          • 2. Re: English content to be translated to French
            prologicfirst Community Member

            Thanks so much for your reply. To answer your questions -

            • I would prefer if I can manage the foreign language from the same project.
            • Yes, I will me doing the translation.

             

            Actually , what I am trying to figure out is, does Robohelp11 have a inbuilt translator that can translate all the content that I have written in English, to any other foreign language (any of the 36 languages that it claims to support).

            • 3. Re: English content to be translated to French
              RoboColum(n) MeganK

              OK. You will need to ensure you keep the two pieces of content sepearte. This also means haiving seperate TOC, index, search and glossary (if used). You could have all the content in the same project and use conditional build tags to filter out the content. Then you'd just need to have seperate files for the TOC, index and glossary. You could have two single source layouts - one for each language - with the required conditional build tag expression and the properties set to pick up the right TOC, index and glossary.

               

              Depending on your output type you may also have to change things like the skin.