Translation - what could cause problems?

Question

Hi there,
another question from my side:
As written before we have some problems converting cross references from FM8 to FM9 when we don't use xml documents, but structured FM documents.
The cross references are fixed, but maybe there is some problem here for translation as well...
I'm not sure how the Translation Memory Systems work.
But will they detect a change, if the attributes of an element have been changed?
And if yes: Is it possible to tell the Tool to just skip some of the elements and do not check them?
From your expierence regarding structured documents/ xml documents and translations:
What might cause issues?
What might be detected as change, even though maybe there is no change which is relevant for translation?
What might cause costs which can be avoided?
Where is time wasted?
Regards,
Anna

Answer 1

Anna,
I don't know anything about translation memory systems. I can say, though, that I have had structured documents translated before, where the markup (attribute values) indicated areas that did not need translation. The vendor was able to handle this fine. We also had the requirement that the content was returned to us with the same markup as the original language, which the vendor was also able to do. So, I would say that a competent vendor should be able to read instructions from your markup and preserve that markup if desired.
Russ