9 Replies Latest reply on Oct 30, 2008 1:48 PM by Ben Minson

    About internationalization..

      i need to work with internationalization, keeping two -equals- Help files but in different languages.
      Example: one english help, another one in spanish but they have the same content.

      Does Robohelp have some tool to help it? If not, anyone has a suggestion?
        • 1. Re: About internationalization..
          RoboColum(n) Level 5
          Hi delgaudio and welcome to the RH community.

          No I'm afraid not as each RH project has language settings that control the TOC, index, etc. You would have to maintain two separate RH projects.
          • 2. Re: About internationalization..
            delgaudio Level 1
            but robohelp doesnt have a tool even to help keeping the folder structure and contained files?
            • 3. Re: About internationalization..
              Even with conditional text settings?
              • 4. Re: About internationalization..
                delgaudio Level 1
                sorry, i've never used conditional text settings... how do i use it?
                • 5. About internationalization..
                  delgaudio Level 1
                  I afraid I wasnt too clear. i need to keep in a easy way two helps, with the same content, but in different languages. Colum, thanks about the welcome.
                  • 6. Re: About internationalization..
                    grammatophile Level 1

                    Originally posted by: delgaudio
                    sorry, i've never used conditional text settings... how do i use it?

                    I was asking Colum, since I am about to create a dual-langauge, English-Japanese, RH7 project. I've done this in FM8 and figured that it's the same use of conditional text settings in RH7.

                    Colum, am I wrong here?

                    • 7. About internationalization..
                      Ben Minson Level 2
                      You could do it with conditional tags, but I wouldn't recommend it. You can still have only one project language set, and that controls toolbar buttons, the left pane, and error messages. Otherwise, you would have to change the project language every time before generating the output.

                      Another problem is that you can specify your topic titles (not headings) in only one language. This means that when you use the index or search, the results appear in that language only.

                      The best way is to create your help completely in English (or whatever your authoring language is), then have it translated. That way, you can copy the English project files to a separate directory so that your TOC and other structures are maintained, then drop your translated files into the copied project.

                      • 8. About internationalization..
                        delgaudio Level 1
                        Benjaminson, thanks for your help... but the greatest worry is about the folder and file tree, cuz we cant let a costumer give a click and receive a 404 error, cuz that page doesnt exists. then, we need to certified ourselves that all the html(help) files are there. some easy way to do it? so, we need when we modified the structure of the default project(english), the secondary project will also be changed. do i make myself clear?
                        open to suggestions! xD tnx 4 all.

                        anyone who could give a closer help -> msn: diogo.delgaudio@hotmail.com
                        • 9. Re: About internationalization..
                          Ben Minson Level 2
                          If you've authored the complete help in one language, then copied it and put your localized files in that copy, then you shouldn't have any missing files or bad links.

                          If you are adding to your help as development goes on and you're also delivering to the customer in stages at the same time, then that adds a bit to the challenge. What I recommend in that case is whenever you create and finish a new help topic in your original project, import it into each of your localized copies. Then the file will be there (untranslated), and links will be preserved. Then, for example when you get the Spanish version of the file back, drop it in to the Spanish copy of the help project so that it saves over the top of the untranslated version.

                          In this same case, with TOC, glossary, and index files, you would update the files in the original version of the project. Then submit the files to be translated. When you get the translated files back, drop them into the localized projects.

                          If you're asking for an automatic way to compare, say, an English project and a Spanish project to make sure all the same files are in each project, I don't know about that. You may have to go with some third-party tool to compare file directories. Or go the good old-fashioned way and eyeball the directories yourself.