Translation Question
Michael Sedley
Hi guys,
I have just been asked by our Russian office what the easiest way would be to make a Russian translation of certain documents.
They will be employing an in-house translator and will only need to translate a small part of a large documentation set.
I don’t think that there will be many future changes to the documents that they will be translating.
I think that the easiest way for them to work would be to get a separate Author-It license and for me to send them a complete copy of the database, and they can translate and publish whatever documents that they need.
If there are future updates to those documents, I could do a search for any objects in the relevant books that have been modified since the last update, and send them an XML file of those objects.
Because they would be publishing the books themselves, I don’t think that we would need to use the localization module (which I had a license to until last month)
Are there any obvious problems with handling translation in this manner?
Thanks in advance,
Michael
Debbie Pulver
We work in a similar way, but in-house at my end. However, I use the
localisation module to track the changes. If you do it the way that
you suggested, make sure that along with the topics that you send in
the future, you remember to also send any associated hyperlink
objects, graphics etc. etc.
If you are worried about them messing up the import, you could ask
them to send you their library and you could do it and send it back to
them. Last week I tried importing a few objects directly from the Eng
library to the Russ library, without using the XML option. That also
worked fine.
Good luck,
Debbie