TOC not displaying in translated files

Question

Using RH8 (HTML).
Translating English RH source files using TRADOS TagEditor.
Translations to Chinese and Japanese have worked fine.
In translations to European languages the TOC does not display in RH nor compiled chm.
This appears to be caused by the use of 'alpha codes' for the extended character set. For example, an .hhc file with
<?xml version="1.0" encoding="utf-8"?>
<toc version="1.0"><properties imagewidth="16" windowstyles="8388642" exwindowstyles="256"></properties>
                <item name="Introducci&oacute;n">
                </item>
</toc>
does not display.
But one with
<?xml version="1.0" encoding="utf-8"?>
<toc version="1.0"><properties imagewidth="16" windowstyles="8388642" exwindowstyles="256"></properties>
                <item name="Introducción">
                </item>
</toc>
or
<?xml version="1.0" encoding="utf-8"?>
<toc version="1.0"><properties imagewidth="16" windowstyles="8388642" exwindowstyles="256"></properties>
                <item name="Introducci&#243;n">
                </item>
</toc>
does display.
Unfortunately, on return from the translators our .hhc files are littered with 'alpha codes' for extended characters.
Any confirmation of our suspicions and suggestions as to:
1) How we can rectify the situation, bearing in mind that a manual replacement is not an option due to the number of files and occurrences within those files.
2) What should have been done to stop this happening.
would be gratefully received.

Answer 1

Hi there
And I too hope that Willam and Peter will forgive me for popping in.
Peter told you that you need to be creating WebHelp, not WebHelp Pro as you initially stated. By reading this, I'm comiing to the conclusion that you believe you must create WebHelp Pro because you are using the RoboHelp_CSH file.
"We don't use the Robohelp server, becuase we use the context sensitive help so we lunch the htm via the script RoboHelp_CSH.js within our own web application."
The thing is, if you are still outputting as WebHelp Pro, you are getting a *DIFFERENT* set of output files that are coded specifically to work within the unique environment that the RoboHelp Server provides. This would explain why the calls aren't being made as expected.
I could be wrong on this but I don't believe I am. If so, one of the others will surely set me straight. You need to generate your output as WebHelp, NOT WebHelp Pro, then publish that set of files to the server. And the RoboHelp_CSH file will happily use the new set of files. (assuming, of course, that all mappings are correctly set)
Cheers... Rick
Helpful and Handy Links
RoboHelp Wish Form/Bug Reporting Form
Begin learning RoboHelp HTML 7, 8 or 9 within the day!
Adobe Certified RoboHelp HTML Training
SorcerStone Blog
RoboHelp eBooks