This content has been marked as final. Show 9 replies
Ben had some great advice for KathyM in that thread. Read it again.
Girl, I don't envy your situation!
* You've never used RH HTML.
* You've never worked a localization effort.
* They won't pay the extra to get translators that work with RH.
What form of suicide do you think you'll settle on, in the end?
Unfortunately there aren't too many people with experience of this area supporting to the forum.
I posted some basic information in this thread earlier today. http://tinyurl.com/67sep6
I hope someone else can add something. Better still would someone like to write an article to go on my site as a permanent source of information? Sorry, no fees!
Leon and Peter --
I did go back and re-read the threads each of you referred to. Since I had gathered my thoughts to post my questions, I was better prepared to read the information this time!
It still seems that the development process will require some serious manual handling...
Any ideas how to find translators that work with RH?
I think I will break out my second question (what to do with the outout) into a separate posting...and leave this one for the development process only.
Our in-house translation group does not use RoboHelp, but I give them the HTML files (and the glossary and index files when necessary), and then I bring them into the appropriate copies of the project. It works pretty well without the translators having RoboHelp. They have their own system that pulls strings out of Word files, HTML files, etc., and then puts them back in, so they don't have any interest in using RoboHelp anyway.
My point is merely that the workflow doesn't have to involve the translators using RoboHelp for things to come together. How easy the process is depends largely on the translators.