Black strikethrough lines in Trados 2009 source text Thread poster: Richard Hill
| Richard Hill Mexico Local time: 10:30 Member (2011) Spanish to English
Hi All I'm getting black strikethrough lines in Trados 2009 source text after loading an MS Word 2007 .docx If I save the document as MS Word 2003 .doc then reload into Trados the problem goes away but I'd still like to know why this happens in the case of MS Word 2007 .docx files. It only happens sometimes, and actually only started today, with two s... See more Hi All I'm getting black strikethrough lines in Trados 2009 source text after loading an MS Word 2007 .docx If I save the document as MS Word 2003 .doc then reload into Trados the problem goes away but I'd still like to know why this happens in the case of MS Word 2007 .docx files. It only happens sometimes, and actually only started today, with two separate files. Any ideas? I was surprised I couldn't find anything on this problem in the forum. Thanks Rich ▲ Collapse | | | Abrigela Local time: 17:30 Hungarian to English + ... In the original maybe? | Sep 17, 2011 |
Hi Rich, The problem (or rather purpose) with a CAT is that it will pick up all the tags that control the text. So maybe they are really in the file and Studio is just displaying what's there. You can show all tags and formatting, and also use the display filter to see all content. Maybe this will shed some light on why this is happening? Abrigela | | | Nora Diaz Mexico Local time: 08:30 Member (2002) English to Spanish + ... Do you get any error messages? | Sep 19, 2011 |
Hi Rich, A colleague I'm working with recently had this happen. As far as I can tell, this was caused by her not having Word 2007 installed in her computer. I suspect this is the case because: 1. I created the original file in my computer and was able to see it fine, no strikethrough lines 2. Saving the DOCX (Word 2007) as DOC (Word 2003) solved the problem for her 3. When I went into her folder structure and opened the SDLXLIFF file for the or... See more Hi Rich, A colleague I'm working with recently had this happen. As far as I can tell, this was caused by her not having Word 2007 installed in her computer. I suspect this is the case because: 1. I created the original file in my computer and was able to see it fine, no strikethrough lines 2. Saving the DOCX (Word 2007) as DOC (Word 2003) solved the problem for her 3. When I went into her folder structure and opened the SDLXLIFF file for the original DOCX in her source folder, I saw a note saying "This file was created using a file type definition that does not exist on your system (Word 2007)..." So I wonder if you see the same kind of message. ▲ Collapse | | | Richard Hill Mexico Local time: 10:30 Member (2011) Spanish to English TOPIC STARTER
Hi Nora I tried to follow your advise and tried to open the SDLXLIFF file directly (double click) and after seeing that I couldn't open it, I selected the file, right click, choose default program, forgot to un-check "always use the selected program to open this file type" (it say's something like that as my OS is in Spanish), then I chose open with "SDLTradosStudio" in the hope I'd see the message you were talking about. So the file extension has obviously changed I now I don't kno... See more Hi Nora I tried to follow your advise and tried to open the SDLXLIFF file directly (double click) and after seeing that I couldn't open it, I selected the file, right click, choose default program, forgot to un-check "always use the selected program to open this file type" (it say's something like that as my OS is in Spanish), then I chose open with "SDLTradosStudio" in the hope I'd see the message you were talking about. So the file extension has obviously changed I now I don't know how to change it back again so all the files in all "Files Type" folders appear with the Trados Studio icon. Do you know how I can change it back to how it should be? As for the original problem, I actually doubt that it's the same reason as with your colleague because it only happens with some .docx 2007 files and not others, but like you say, saving it as .doc 2003 does "solve" the issue. And even if I work a .doc.x 2007 file with the strike through lines, there is apparently no problem with the file saved as doc.x 2007 after translation in Trados. Anyway, I hope you are able to tell me how I can undo my blunder with the file association? Thanks for your response. Rich ▲ Collapse | |
|
|
Nora Diaz Mexico Local time: 08:30 Member (2002) English to Spanish + ...
Hi Rich, If you mean how you can re-associate SDLXLIFF files with Studio under Windows, this is what I would do in Windows 7: Control Panel - All Control Panel Items - Default Programs - Set Associations Then right-click on the SDLXLIFF file extension and click on the Change Program button and choose SDL Trados Studio. But it's strange that you wouldn't be able to open the SDLXLIFF with Studio in the first place, though. The messa... See more Hi Rich, If you mean how you can re-associate SDLXLIFF files with Studio under Windows, this is what I would do in Windows 7: Control Panel - All Control Panel Items - Default Programs - Set Associations Then right-click on the SDLXLIFF file extension and click on the Change Program button and choose SDL Trados Studio. But it's strange that you wouldn't be able to open the SDLXLIFF with Studio in the first place, though. The message I'm talking about should be visible in the Editor view in Studio after the file opens. If you click on View - Messages you should see it there. In my case I saw it under Notes. As extra info in case this helps, our original file for this entire issue was a PDF that I ran through OCR, then saved as Word 2007, then added to an existing project in Studio. But... I have just today realized that my OCR software (ABBYY Finereader 11) doesn't save an actual DOCX file when you choose Save as Word, but a "disguised" RTF.
[Edited at 2011-09-19 22:40 GMT] ▲ Collapse | | | Richard Hill Mexico Local time: 10:30 Member (2011) Spanish to English TOPIC STARTER I tried to open "SDLXLIFF.sdlfiletype" | Sep 20, 2011 |
Hey Nora The file I tried to open was “SDLXLIFF.sdlfiletype” in the “File Types” folder not the "(file name).doc_es-MX_en-US.sdlxliff file". Did I mess things up trying to open this file and changing the file association? Rich | | | File association | Sep 20, 2011 |
Hi Rich, Years ago once I was tampering with several file types, and, like you, forgot to uncheck the box saying „always use the selected program to open this file type” so I accidentally mixed two different file types into one, needless to say with cathastropic consequences. With my limited knowledge in this field, with XP, I was not able to restore the original associations as I was able to convert any association into another, but was unable to separate the origi... See more Hi Rich, Years ago once I was tampering with several file types, and, like you, forgot to uncheck the box saying „always use the selected program to open this file type” so I accidentally mixed two different file types into one, needless to say with cathastropic consequences. With my limited knowledge in this field, with XP, I was not able to restore the original associations as I was able to convert any association into another, but was unable to separate the original files with that association from the files with the unintended new association. Fortunately, I found a little program on the net which could restore the original file associations in seconds. The bad news is that I have lost that program and cannot remember its name. If you are in the same situation with Windows 7, using a similar program seems to be an option. ▲ Collapse | | | Richard Hill Mexico Local time: 10:30 Member (2011) Spanish to English TOPIC STARTER Extra info did the trick for problem 1. Great!!! | Sep 20, 2011 |
Nora Diaz wrote: If you mean how you can re-associate SDLXLIFF files with Studio under Windows, this is what I would do in Windows 7: Control Panel - All Control Panel Items - Default Programs - Set Associations Then right-click on the SDLXLIFF file extension and click on the Change Program button and choose SDL Trados Studio.[/quote] I did as you suggested and I think it's sorted, but I'm not sure as the image of the files seems to be different. I can't remember! Are the file icons supposed to look like this? Nora Diaz wrote: But it's strange that you wouldn't be able to open the SDLXLIFF with Studio in the first place, though. The thing is that, in attempting to follow your original advise for the original problem, I didn't try to open the regular "sdlxliff" (lowercase) file in the project folder, but rather, I made the mistake of trying to open the "SDLXLIFF" (UPPERCASE) found in the "File Types" sub-folder, and as this file does not open automatically with double click, this is why I changed the default program to open the "SDLXLIFF" (UPPERCASE) file with Trados. Nora Diaz wrote: As extra info in case this helps, our original file for this entire issue was a PDF that I ran through OCR, then saved as Word 2007, then added to an existing project in Studio. But... I have just today realized that my OCR software (ABBYY Finereader 11) doesn't save an actual DOCX file when you choose Save as Word, but a "disguised" RTF. Problem one is solved. Now that you mention it, I use ABBYY Finereader 10, and I've just been trying to open a couple of .doc.x files created with Abbyy and just like you say, the first file created with Abbyy receives the error message you mentioned, then when I resave as another .doc.x file, there they are, those dreaded strike-through lines, then when I resave again as a .doc 2003 file, there are no strike-through lines. Mystery one SOLVED. Thanks so much. I don't know how long it would have taken me to work out the common denominator and realize that the problem was with Abbyy. Rich | |
|
|
Richard Hill Mexico Local time: 10:30 Member (2011) Spanish to English TOPIC STARTER
Hi István Thanks for you reply. As you can see, thanks to Nora it's sorted. Cheers! Rich | | | Nora Diaz Mexico Local time: 08:30 Member (2002) English to Spanish + ... I see what you mean | Sep 20, 2011 |
Hi Rich, I now see what you mean. The icon looks fine to me (a wrench in front of a two-column document icon). Thank you for confirming you were also using ABBYY Finereader. I spent most of the afternoon yesterday talking to their support people trying to work out an issue with images that are not processed in Studio in documents saved as Word 2007 in Finereader. I think they have a bug in their Word 2007 converter, but they haven't realized it because th... See more Hi Rich, I now see what you mean. The icon looks fine to me (a wrench in front of a two-column document icon). Thank you for confirming you were also using ABBYY Finereader. I spent most of the afternoon yesterday talking to their support people trying to work out an issue with images that are not processed in Studio in documents saved as Word 2007 in Finereader. I think they have a bug in their Word 2007 converter, but they haven't realized it because things look fine at first sight, it's only when you process the file further (in Studio in this case) that things start jumping out. My solution for now is never to save Finereader output as Word 2007, but only as Word 2003 and to save once again in Word, for good measure, as Finereader seems to think it's ok to save documents with a DOC/DOCX extension but with an RTF structure. ▲ Collapse | | | Post removed: This post was hidden by a moderator or staff member for the following reason: empty posting | Ridha Harwan Indonesia Local time: 22:30 English to Indonesian + ...
Nora Diaz wrote: Hi Rich, I now see what you mean. The icon looks fine to me (a wrench in front of a two-column document icon). Thank you for confirming you were also using ABBYY Finereader. I spent most of the afternoon yesterday talking to their support people trying to work out an issue with images that are not processed in Studio in documents saved as Word 2007 in Finereader. I think they have a bug in their Word 2007 converter, but they haven't realized it because things look fine at first sight, it's only when you process the file further (in Studio in this case) that things start jumping out. My solution for now is never to save Finereader output as Word 2007, but only as Word 2003 and to save once again in Word, for good measure, as Finereader seems to think it's ok to save documents with a DOC/DOCX extension but with an RTF structure. @Nora thank you very much. Same problem (still in 2015) and thank you for you information. I have save it in 2007 and I save as 2003, then the line is disappear. | | | To report site rules violations or get help, contact a site moderator: You can also contact site staff by submitting a support request » Black strikethrough lines in Trados 2009 source text Trados Business Manager Lite | Create customer quotes and invoices from within Trados Studio
Trados Business Manager Lite helps to simplify and speed up some of the daily tasks, such as invoicing and reporting, associated with running your freelance translation business.
More info » |
| 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 » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |