This content has been marked as final. Show 2 replies
Some of our colleagues in the US and Australia may disagree but there is not much difference between our three "languages". We document for our US offices (we don't have any in Australasia) but just say we will stick with UK english. If you really need the three versions, I'd tend to think the best way would be in a single project. You could handle the different spellings by using conditional build tags and only including the required tag when you generate the output. Another way would be to use the RH variables feature remembering to change the variable value before generating.
As far as the output is concerned, both the above approaches would need a separate ouptut folder. You could duplicate your Webhelp single source layout and just change the build tag statement to save you having to change it each time. You should also be aware that right to left languages (e.g. Arabic) were not supported in RH7. I think it is the same in RH8. Maybe someone else can confirm this.
If you adopt this approach, you'd only have a mapid for each help call. You'd have different output but the structure and file paths would be identical. Therefore you'd only need a single application call using the mapid for the call to work. The caveat is that the help output would have to be installed in exactly the same location regardless of the location.
Ok. I understand that to base the help system on a specific English is better. I shall still await details on handling different languages. Thanks for your time.