| Pages in topic: [1 2] > | Failed to save target content: Length cannot be less than zero. Parameter name: length Thread poster: Scott Saylor
|
|---|
Failed to save target content: Length cannot be less than zero. Parameter name: length
Can anyone tell me where this error comes from and how to fix it?
Several segments in my source document (that I made in Microsoft Word with the help of an OCR tool) set off the above alert and completely prevent me from saving my target. This happens a lot when I use TRADOS and its quite maddening! I have tried making the whole source document into unformatted text, and this error st... See more Failed to save target content: Length cannot be less than zero. Parameter name: length
Can anyone tell me where this error comes from and how to fix it?
Several segments in my source document (that I made in Microsoft Word with the help of an OCR tool) set off the above alert and completely prevent me from saving my target. This happens a lot when I use TRADOS and its quite maddening! I have tried making the whole source document into unformatted text, and this error still happens.
I have a hunch that it has something to do with sentences that have both Japanese and English in it. Either that or subscripts and superscripts.
By the way, all the segments have been translated so that is NOT the problem.
Please let me know how to fix this! ▲ Collapse
| | | | Kerstin Green 
United Kingdom
Local time: 07:38
English to German
+ ...
| Same problem! | Feb 24, 2011 |
I get the same message. I have 6 documents, they all were prepared in the same way (from pdf with OCR, then cleaned up). 4 work fine, and on the other 2 I get this error.
I have to turn this in tomorrow!
HELP!
| | | | Scott Saylor
Local time: 23:38
Japanese to English
TOPIC STARTER | Thanks for posting, too, Kersten | Feb 27, 2011 |
Thank you for posting, too, Kersten. I hope SDL will be able to answer this soon, because it is a really critical issue.
I have found a way to avoid it when I am preparing documents for Trados. It actually involves removing all of the formatting, though, but it works. I paste everything into notepad then I paste it from Notepad back into Word using the Paste Special unformatted text option. Then I save that as the file.
However, that is not a satisfactory workaround for... See more Thank you for posting, too, Kersten. I hope SDL will be able to answer this soon, because it is a really critical issue.
I have found a way to avoid it when I am preparing documents for Trados. It actually involves removing all of the formatting, though, but it works. I paste everything into notepad then I paste it from Notepad back into Word using the Paste Special unformatted text option. Then I save that as the file.
However, that is not a satisfactory workaround for me because it involves losing all the formatting. So SDL, please let us know!
[Edited at 2011-02-27 00:20 GMT] ▲ Collapse
| | | | Hector Aires
Local time: 03:38
Member
English to Spanish
+ ...
| I had the same problem today with Trados Studio 2009 but I solved (four hours) | Feb 27, 2011 |
Hi you both !!!!!
On the source MSWord file I had several terms as "N2" and "H2O2". To make the target more accurate I replaced the "2" in plain text with the "2" in subscript for, as example, "liquid N2" (liquid nitrogen), the same for the hydrogen peroxide "H2O2". When saving target as... the legend "Length cannot be less than zero. Parameter name: length" appeared.
And there was the problem. Inserting the subscripts placed new tags, hence, I deleted those tags and everythin... See more Hi you both !!!!!
On the source MSWord file I had several terms as "N2" and "H2O2". To make the target more accurate I replaced the "2" in plain text with the "2" in subscript for, as example, "liquid N2" (liquid nitrogen), the same for the hydrogen peroxide "H2O2". When saving target as... the legend "Length cannot be less than zero. Parameter name: length" appeared.
And there was the problem. Inserting the subscripts placed new tags, hence, I deleted those tags and everything went fine.
I replaced the plain text 2s with subscripts 2s on the MSWord translated file and that's all.
Have my best regards
El Étor ▲ Collapse
| | |
|
|
|
Scott Saylor
Local time: 23:38
Japanese to English
TOPIC STARTER
Hector, Thank you so much for your reply. I definitely had subscripts in my text, so that must have been the problem. Do you know if this problem is limited to subscripts or if it happens whenever you modify a Word document (i.e. any modifications make new tags)? I hope this only applies to subscripts.
| | | | Scott Saylor
Local time: 23:38
Japanese to English
TOPIC STARTER
Also, I just saw the subject of your reply. Congratulations for solving even though it took 4 hours! It took me the same amount of time to not be able to solve it.
| | | | | Thanks Hector! | Feb 27, 2011 |
I also had the same problem today and was able to save to target once I removed the two subscripts in my document. I would have never guessed that was the problem, so a big thank you for saving me a lot of time!
[Edited at 2011-02-27 04:26 GMT]
| | | | Kerstin Green
United Kingdom
Local time: 07:38
English to German
+ ...
| That was it! | Feb 27, 2011 |
Yup, that solved it for me, too. I had several times "CO2" with subscript in the document.
Thanks!!
| | |
|
|
|
Hector Aires
Local time: 03:38
Member
English to Spanish
+ ...
| I don't know | Feb 27, 2011 |
Scott Saylor wrote:
Hector, Thank you so much for your reply. I definitely had subscripts in my text, so that must have been the problem. Do you know if this problem is limited to subscripts or if it happens whenever you modify a Word document (i.e. any modifications make new tags)? I hope this only applies to subscripts.
I upgraded SDL Trados 2007 to Studio on last December and am applying it very slowly for MSWord, Excel and PP, in fact the Office Suite.
For InDesign and Quark we, my team and me, still use SDL Trados 2007.
Then, my experience with Studio is rather short. However, I think there should be another way to solve the problem. I have added several types of tags on TE other than subscripts and never had a problem. I think Studio should work in a similar way.
Hope this helps.
Cheers
El Étor
| | | | George Cook
United Kingdom
Local time: 07:38
French to English
+ ...
| New tags are the culprit | Mar 10, 2011 |
I have had this problem a few times today in a huge document I was working in. The problem is new tags.
After I received the error I went through the document and removed the new tags I had inserted (italics, superscripts, subscripts), either replacing them with nothing, or replacing them with the correct tag pair from the source text.
After each one, I saved the document and tried to Save Target As..., but to no avail, until all of them had been corrected. Th... See more I have had this problem a few times today in a huge document I was working in. The problem is new tags.
After I received the error I went through the document and removed the new tags I had inserted (italics, superscripts, subscripts), either replacing them with nothing, or replacing them with the correct tag pair from the source text.
After each one, I saved the document and tried to Save Target As..., but to no avail, until all of them had been corrected. There was then no problem.
My advice, therefore, is always use the tags from the source text, or do the formatting in the target Word document; adding italics/superscripts etc. from the toggle menu seems to generate this problem. ▲ Collapse
| | | | Scott Saylor
Local time: 23:38
Japanese to English
TOPIC STARTER
Hi George,
Yeah, I was kind of wondering if it might happen with other formatting tags. I agree that its just too much of a risk to format anything in the source if youre going to do an important project.
One thing I don't get is how Trados can see that you have made a "new" tag. Does Microsoft Word somehow secretly store this information when you modify a document that you generated via an OCR or other tool? I wonder.
Either way, it seems like a shame that... See more Hi George,
Yeah, I was kind of wondering if it might happen with other formatting tags. I agree that its just too much of a risk to format anything in the source if youre going to do an important project.
One thing I don't get is how Trados can see that you have made a "new" tag. Does Microsoft Word somehow secretly store this information when you modify a document that you generated via an OCR or other tool? I wonder.
Either way, it seems like a shame that we can't reliably format our own documents and take advantage of the formatting features in Trados Studio. SDL...are you listening....?
Scott ▲ Collapse
| | | | Michael-M
Local time: 08:38
French to English
| Confirmation | Apr 28, 2011 |
Hi -
Thank goodness for this thread. I only wasted an hour trying to fix my document.
The problem is new tags, as George says.
I had an occurrence of CO2 in my English source, with a subscript in the original, and it didn't come through with a subscript in the French target. I therefore added the subscript with Trados, and soon had the "Length cannot be less than zero" problem. Interestingly enough, the problem cell was identified as being a few sentences l... See more Hi -
Thank goodness for this thread. I only wasted an hour trying to fix my document.
The problem is new tags, as George says.
I had an occurrence of CO2 in my English source, with a subscript in the original, and it didn't come through with a subscript in the French target. I therefore added the subscript with Trados, and soon had the "Length cannot be less than zero" problem. Interestingly enough, the problem cell was identified as being a few sentences later than the cell with CO2.
After reading your posts, I edited the Translation Unit to remove the new subscript tags and my document now regenerates fine. Removing the tags with the subscript button DID NOT have the same effect.
Note: "Preview" and Shift-F12 (to generate the target) seem to be pretty much the same, so by keeping the Preview up to date on my 2nd monitor I was able to find out WHEN the document started to fail, rather than waiting until much later. Thus, the "subscript thing" was fresh in my mind when I saw your post.
I submitted this to SDL as something they definitely need to fix, as you also suggest in this thread.
Thanks again,
Michael ▲ Collapse
| | |
|
|
|
Scott Saylor
Local time: 23:38
Japanese to English
TOPIC STARTER | Preview Window Great Idea | Apr 28, 2011 |
Hi Michael,
Thank you for describing your technique of leaving the preview window open to see when the document fails. I am going to use that trick! Last night I actually encountered this problem all over again because I accidentally added subscripts -- but when I took them away using the Trados toolbar commands that remove the subscript, I still couldn't save the target. Now I also know that I have to edit the translation unit (or at least for a few spaces before and after whateve... See more Hi Michael,
Thank you for describing your technique of leaving the preview window open to see when the document fails. I am going to use that trick! Last night I actually encountered this problem all over again because I accidentally added subscripts -- but when I took them away using the Trados toolbar commands that remove the subscript, I still couldn't save the target. Now I also know that I have to edit the translation unit (or at least for a few spaces before and after whatever at one point had a subscript or superscript), as I learned last night when I meticulously checked the document for the faulty part.
Anyway, thanks for your message and thanks for sending to SDL! ▲ Collapse
| | | | Michael-M
Local time: 08:38
French to English
| Glad to help | Apr 29, 2011 |
How unusual to feel that I can actually give advice on this forum! I guess I just use Trados so much that I can figure out how to push it when I know it should be able to do something.
| | | | Trans-IT Tra (X)
Canada
Local time: 02:38
English to French
| Try this workaround while we get a patch from SDL | Apr 30, 2011 |
We ran into this problem today and found a turnaround that works without having to edit the final Word file (or at least it did for us!):
1- Read the original file in good old Tag Editor and create a TTX.
2- Read this TTX into Trados 2009
3- Translate the document
4- Save target directly as a Word file (ours was a DOCX).
The final document was formatted with the proper superscripts (in our case).
Somewhat cumbersome but what else is new ... See more We ran into this problem today and found a turnaround that works without having to edit the final Word file (or at least it did for us!):
1- Read the original file in good old Tag Editor and create a TTX.
2- Read this TTX into Trados 2009
3- Translate the document
4- Save target directly as a Word file (ours was a DOCX).
The final document was formatted with the proper superscripts (in our case).
Somewhat cumbersome but what else is new ▲ Collapse
| | | | | Pages in topic: [1 2] > | To report site rules violations or get help, contact a site moderator: You can also contact site staff by submitting a support request » Failed to save target content: Length cannot be less than zero. Parameter name: length | Trados Studio 2022 Freelance | The leading translation software used by over 270,000 translators.
Designed with your feedback in mind, Trados Studio 2022 delivers an unrivalled, powerful desktop
and cloud solution, empowering you to work in the most efficient and cost-effective way.
More info » |
| | CafeTran Espresso | You've never met a CAT tool this clever!
Translate faster & easier, using a sophisticated CAT tool built by a translator / developer.
Accept jobs from clients who use Trados, MemoQ, Wordfast & major CAT tools.
Download and start using CafeTran Espresso -- for free
Buy now! » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |
Login to reply/comment 
Translation news related to SDL Trados
