Forum: CAT Tools Technical Help
Topic: QC with Language Tool Box (LTB)
Poster: Samuel Murray
Post title: @Annett
[quote]Annett Roessner wrote:
This was very time consuming because as far as I could tell the report didn’t indicate the segment number. [/quote]
This may depend on what the XLIFF file looks like that is exported from LingoTek. I know that some XLIFF files use "trans-unit id" numbers that do not start at 0 or 1, and the "trans-unit identifier" can be a long, nonsensical number, and may not even be in numerical order from the top to the bottom of the file. I don't use either LingoTek or LTB, but I can imagine that perhaps LTB uses the XLIFF's trans-unit ID it its own "String ID" column, while in LingoTek the segments are numbered from 1.
You have my sympathy -- it is not uncommon for QA reports to use string numbering that has no connection whatsoever to the segment numbers in the files. When that happens, and if I'm required to mark both fixed and non-fixed issues on the QA report, I simply mark those segment in the QA report as "not found". In most cases, however, clients only want me to mark the segments that I *do* change, so if I can't find some text, I just skip it.
[Edited at 2020-05-30 11:35 GMT]
Topic: QC with Language Tool Box (LTB)
Poster: Samuel Murray
Post title: @Annett
[quote]Annett Roessner wrote:
This was very time consuming because as far as I could tell the report didn’t indicate the segment number. [/quote]
This may depend on what the XLIFF file looks like that is exported from LingoTek. I know that some XLIFF files use "trans-unit id" numbers that do not start at 0 or 1, and the "trans-unit identifier" can be a long, nonsensical number, and may not even be in numerical order from the top to the bottom of the file. I don't use either LingoTek or LTB, but I can imagine that perhaps LTB uses the XLIFF's trans-unit ID it its own "String ID" column, while in LingoTek the segments are numbered from 1.
You have my sympathy -- it is not uncommon for QA reports to use string numbering that has no connection whatsoever to the segment numbers in the files. When that happens, and if I'm required to mark both fixed and non-fixed issues on the QA report, I simply mark those segment in the QA report as "not found". In most cases, however, clients only want me to mark the segments that I *do* change, so if I can't find some text, I just skip it.
[Edited at 2020-05-30 11:35 GMT]