In edit mode, when SDL encounters a repeat match of a previous segment with a tab at the end of the segment, it does not insert the tab at the end of the repeat match segment. That's not good. The Verify function picks this up (flags the segments as inconsistent translations), but if you run Verify again after manually correcting the bad segments it happily deletes the terminal tags in the repeat match segments and flags them as inconsistent translations again. That's even worse.
Unknown said:In edit mode, when SDL encounters a repeat match of a previous segment with a tab at the end of the segment, it does not insert the tab at the end of the repeat match segment.
ok - I also have the test file from Kenneth. I think it's quite a feat to have been able to create a file like this in the first place!! But indeed, Studio will not save the tab at the end of the segment. I started with this and confirmed it:
Then if I redid it Studio does this from the TM:
So this does look like a bug. Clearly not something you see everyday and far easier to avoid it in the first place than it is to get into this situation, but it seems like a bug. I'll report this to development along with the test file.
Thanks for finding it, and I hope you'll have a better way to handle these CSV files in the future using the Excel text import wizard!
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
I also had a play with the tab delimited file created by Kenneth. This is also easily handled by adding one rule to the segmentation rules to segment on a tab. Then you get this with no trailing tabs and no tags in the file either:
The quotes are in there because of all the messing around, but note there is no trailing tab and the TM match is perfect. I still can't actually create a source file as the one Kenneth did on purpose!
As Kenneth said I doubt this will be a bug handled with any real urgency as it's really hard to get yourself into this situation in the first place. Much easier to handle them without a problem.
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
I also had a play with the tab delimited file created by Kenneth. This is also easily handled by adding one rule to the segmentation rules to segment on a tab. Then you get this with no trailing tabs and no tags in the file either:
The quotes are in there because of all the messing around, but note there is no trailing tab and the TM match is perfect. I still can't actually create a source file as the one Kenneth did on purpose!
As Kenneth said I doubt this will be a bug handled with any real urgency as it's really hard to get yourself into this situation in the first place. Much easier to handle them without a problem.
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
ok - now I know how he did it, and it's Studio's fault, not his!!
If you don't use the new Word filetype like this then the same process I just tried to replicate creates the very problem Kenneth got into:
So the other lesson to come from this, in addition to using Excel in the first place, is to always make sure you are using the new Word filetype by default.
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
