Today I used this function for the first time within a single file successfully.
Verification > QA Checker 3.0 > Inconsistencies
Now, I have 20 files in a project and need cross checking too.
So, I used batch process.
Looks good though, the result makes me puzzling.
It is a .xml format. I can not read it with my bare eyes.
How can I see the result properly ?
-Just like the nice result of (PlugIns) "Sdl.Community.XliffCompare" ?
THANKs
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
Is it CROSS_checking ? Looks like it is just processing many files separately. If so it's not what I wanted.
All the files are belong to the same project, so it should have the consistent consistency.
Indeed, it's processing each individual file... SDL never thought about cross-checking.
If you want to cross-check multiple files, you have to virtually merge them first (open them all in editor) and then run the QA check inside editor.
Though, the result is still half-useless since it tells you only the inconsistent segment number, but without telling from which file the segment comes... so you need to manually filter by the text of each inconsistency to see the segments... which is terrible manual work (depending on how many inconsistencies you have, of course).
Since SDL does not see this as bug (it was never designed to work this logical way, thus it's not a bug according to SDL), you can hardly expect any fix to be implemented in next few years (based on past experience).
Indeed, it's processing each individual file... SDL never thought about cross-checking.
If you want to cross-check multiple files, you have to virtually merge them first (open them all in editor) and then run the QA check inside editor.
Though, the result is still half-useless since it tells you only the inconsistent segment number, but without telling from which file the segment comes... so you need to manually filter by the text of each inconsistency to see the segments... which is terrible manual work (depending on how many inconsistencies you have, of course).
Since SDL does not see this as bug (it was never designed to work this logical way, thus it's not a bug according to SDL), you can hardly expect any fix to be implemented in next few years (based on past experience).
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
Done..
15 files in One Go
Translate
