If Track Changes is activated in Studio, the format is changed in the target Word file (docx): my changes and all text following them in a segment are converted to Times New Roman 12pt (same thing if I use 'Open for review' in the project folder btw).
If Track Changes isn't activated, no problem. I tested with the same file: the initial translation was in Arial 9pt and everything stayed in Arial 9pt after my changes.
Hi Antonella,
Thank you for the file. I can now reproduce this with any file, but only if I use the 2007-2013 filetype:
If you use the new Word filter by disabling the old one and enabling the new one as shown in the screenshot above then this does not happen. It's clearly a bug in the old one that we will report to development, but you can work around it by using the newer filtype that is part of Studio 2015. You'll need to reprocess the source files with this new filetype, but other than manually correcting the target files this is the best solution I think. If you use this filetype in the future you won't have this problem,
The bug is reproduced by changing the font from the default font in the word file manually and then applying tranck changes in Studio. So if the author uses the styles feature in Word this won't happen, but if they manually change fonts (as so many do!) and you correct something that has been changed then this bug is reproduced.
The new filetype is more forgiving generally and also has some nice features to get a target file out even if there are errors in the file, so it's worth taking a look at it anyway I think.
Regards
Paul
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Hi Antonella,
Thank you for the file. I can now reproduce this with any file, but only if I use the 2007-2013 filetype:
If you use the new Word filter by disabling the old one and enabling the new one as shown in the screenshot above then this does not happen. It's clearly a bug in the old one that we will report to development, but you can work around it by using the newer filtype that is part of Studio 2015. You'll need to reprocess the source files with this new filetype, but other than manually correcting the target files this is the best solution I think. If you use this filetype in the future you won't have this problem,
The bug is reproduced by changing the font from the default font in the word file manually and then applying tranck changes in Studio. So if the author uses the styles feature in Word this won't happen, but if they manually change fonts (as so many do!) and you correct something that has been changed then this bug is reproduced.
The new filetype is more forgiving generally and also has some nice features to get a target file out even if there are errors in the file, so it's worth taking a look at it anyway I think.
Regards
Paul
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Translate
