Startindex cannot be less than zero. Parameter name: startindex

Hi folks,
I have 7 xlf files (as exported from Transifex). I am done with translation, and now I want to run QA. However, when I press F8, I get the above-referenced error message.
First I tried to run QA for all [multiple] files. Then I did it for each file individually and I could find the file (1 out of 7) that gives this error message. I have translated 300+ such xlf files for this client. This is a first for me.
Any idea how can I fix it? It is not that critical to me because only a single file is affected, but I would appreciate any help. Thank you.
Error dialog box in Trados Studio with message: Failed to verify document; StartIndex cannot be less than zero. Parameter name: startIndex.
Detailed error report in Trados Studio showing a System.ArgumentOutOfRangeException and a stack trace with multiple method calls.



Generated Image Alt-Text
[edited by: Trados AI at 3:56 AM (GMT 0) on 29 Feb 2024]
emoji
Parents Reply Children
  • Yes, there is a segment that only contains a nonbreaking space. Originally, it was a code ( ), but then I ran the Cleanup Source batch task to replace all html codes with true symbols. So now there is a true nonbreaking space in the source segment. After a trial, I found that when I import a translated file back into Transifex, it does not affect the source part of the file, and even though I run the Cleanup Source batch task in Trados, the source part remains unchanged in Transifex. Hence I decided recently to run the Cleanup Source batch task for all my future Transifex jobs before starting my work.
    Screenshot of Trados Studio showing a segment with a nonbreaking space symbol highlighted in blue, with a green checkmark indicating no error.

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 3:56 AM (GMT 0) on 29 Feb 2024]
  • Wow! Once I replaced ° with  , the F8 feature works fine again.
    That means I have to edit my Cleanup Source regex rule by removing  . Ok.
    Genius! Thank you so much 

    *It was my second time that I used the Cleanup Source batch task (btw thank you for this batch task too) for this client's files. Probably, there were no space-only segments in my previous jobs. That is why I came across this behavior only now, this second time.



  • Glad you solved it :).
    To explain, the QA verifier removes any trailing (and leading) spaces in the source and target in order to check the punctuation.
    However, it assumes that all segments contain something other than just spaces, so this is why the error occurs.

    Glad that the batch task tool comes in handy too. Looking back, I wish I could of made it more user friendly as I think it would be used by more people if it was.

  • Oh yeah, it would be just marvelous if it was as easy as Advanced Display Filter for example. I use 150% scaling on my PC, which makes the Cleanup Source window unusable because the most important part of it ('Edit' button) gets hidden with 150% scaling, and I have to set 100% scaling, then reboot, then edit the conversion file, then set 150% scaling again, then reboot again...
    However the feature itself is just irreplaceable. Great help.