Victor Lopez 

I guess the easiest way is this:

1. create a project with the first XML file
2. copy source to target
3. update to a new TM
4. add the new XML file to your project and analyse it against the TM to find the number of changes
5. pre-translate it to look at where the changes are based on the match values
6. use the display filter to find the segments that are not 100% matches

Would that help?

You could also use Post-Edit Compare to run an html report of only the segments that are not 100% matches and that might also be helpful.

Victor Lopez ,

To compare plain text files you don’t need Trados. For example, Notepad++ has plugins to do it and it’s far way easier than using Trados. You can check this video to assess this way: https://www.youtube.com/watch?v=XJrnqrczLZQ

Also, you voted up Paul's answer, so Paul  may not see this post anymore, as it’ll appear as already Answered. So I’m gonna try to answer on his behalf:

Paul said:

copy source to target

Select all segments in Editor, then right click on the left column with numbers and select Copy Source to Target.

Paul said:

update to a new TM

Select Batch Tasks button > Update Main Translation Memories

Before this 3rd step I guess you need:

• to set all segments as Translated in Editor,
• to create a new and empty TM,
• and to attach this TM to your Trados Studio project.

Hi, thanks for the advice about Notepad++. It is helpful to see the changes; however, do you know if I can get a report of changes? I'm trying to identify the number of changes between two book editions.

Hi, thanks for the advice about Notepad++. It is helpful to see the changes; however, do you know if I can get a report of changes? I'm trying to identify the number of changes between two book editions.

Victor Lopez 

If you create one xliff per XML version, the free plugin Post-Edit Compare (https://appstore.rws.com/Plugin/15) can create a report.

I use this app to compare different versions of the same basic XLIFF, but I’m not sure if it’ll go mad if there are additions or deletions of full segments... You can try.

If it doesn’t work, try Paul’s way, which will give you the number of segments with changes. Also, if you create a report (Analysis) you will know the workload in new words and fuzzies.

This is excellent feedback. Thanks a lot. I was able to solve my issue.

All the best,

Victor