Forum: Transit support
Topic: Transit NXT translation memories w/ different number of source/target segments
Poster: Gary Hess
I am trying to create a custom QA tool for my own use and was analyzing some .DEU and .ENG files. Sometimes there is a mismatch between the source and target files, e.g. source file has 30 segments and target file has 31 segments. I would assume that some other translator during the translation process split 1 segment into 2 segments (that would explain the discrepancy).
I have a technical question: How does Transit NXT know which segments belong to one another? I have looked at the XML quite a bit, but I can't figure it out yet.
BTW: I loaded a pair of mismatched .DEU and .ENG files into XBench, but Xbench doesn't correctly align the mismatched segments either.
Thanks,
Gary
Topic: Transit NXT translation memories w/ different number of source/target segments
Poster: Gary Hess
I am trying to create a custom QA tool for my own use and was analyzing some .DEU and .ENG files. Sometimes there is a mismatch between the source and target files, e.g. source file has 30 segments and target file has 31 segments. I would assume that some other translator during the translation process split 1 segment into 2 segments (that would explain the discrepancy).
I have a technical question: How does Transit NXT know which segments belong to one another? I have looked at the XML quite a bit, but I can't figure it out yet.
BTW: I loaded a pair of mismatched .DEU and .ENG files into XBench, but Xbench doesn't correctly align the mismatched segments either.
Thanks,
Gary