Hints or tips for translation would be very much appreciated!
Don't know what the exact issues are, but one place to look in Styler is Tools > Language Properties. This will let you configure generated text in different languages.
Translation issues can relate to various aspects of documentation, from finding a translator or Language Service Provider to managing the various versions of various languages for various documents. If you like, we can discuss this offline.
Thanks for your response. We have already translated with a vendor and our styleheets have been built for all of our languages. Here's more detail about the types of questions/issues we are noticing.
For example, German and Greek languages both include uppercase letters that need to appear with a different character when they are lowercase. For example, in German, our heading in the XML file should be BESTIMMUNGSGEMÄSSE VERWENDUNG (all caps), but the automated TOC should be Bestimmungsgemäße Verwendung (not all caps). With our stylesheet, the headings match in both, so we see the BESTIMMUNGSGEMÄSSE VERWENDUNG (all caps) heading in both the XML file and TOC. Is there a setting to control this?
Also, is there a specialized setting or setup for Arabic. I know the text should read from right to left, but it is currently reading from left to right. Is any easy fix for this?
If you are using Styler then your options for doing what you want are pretty limited. There are very few configuration items it has related to language support. You would have to do such things as "source edits", which means you need to know a bit about programming and so on. Arabic mode will be particularly challenging for Styler, and will almost surely require the use of the APP print engine if you are not using it already.
There are consultants and specialist companies out there who can help you, an example of which is our organisation GPSL (www.gpslsolutions.com).
There are techniques in Styler that allow you to create a different title specifically for use in the table of contents. Depending on how you are supporting translations, that could be an answer to your dilemma. Check the documentation for more on ways to customize the table of contents format object. And of course, we would be happy to discuss possible solutions with you too.
The APP print engine offers many advantages when it comes to formatting, and composing text that reads from right to left is one of them. It's likely you're already using the APP print engine to format your output; if not, you may want to consider changing your stylesheets over. Check out "Logic for Print/Preview Engine Selection" in the Arbortext Editor online help.