style line feeds/breaks

Question

Is there a way of making Trados interpret 
 type line breaks as line breaks, rather than as words? 
 Developers seem to be really bad at handing off stuff for translations with that kind of formatting. The problem is that it's most common in fairly long chunks of text, like marketing stuff about software. Because Trados interprets them as text, when you have something like 
 This exciting new tool lets you:
Open files
View documents
Make coffee
Channel Elvis 
 Trados interprets this as one long string or (depending on the punctuation) segments this in strange places. As a result, even though I might have 4 matches for the 4 above, I get zero matches from Trados because I don't have the whole string in the TM in its entirety.

Sébastien Desautel · Accepted Answer

Hi Nora, Paul, Walter and Michael, I've tested your testfiles and I get everything fine. I work with Studio 12.0.4996.3 and MS Word 2010 (14.0.7166.5000 , 32 bit). I also took a look inside the docx you sent: = unpacked the docx and looked for the document.xml, this is the file where the strings are: in Noras file, everything is fine, here the code part where the text is This exciting new tool lets you: Open files View documents Make coffee Channel Elvis in Paul, there are spellcheck tags which are exactly where the false segmentation occurs. As \ and n are separated, the TM rules can't apply. and here a couple of lines: ...This exciting new tool lets you: \nOpen files \... I bet the segmentation takes place on computer where the newest word version is installed (not used to create the doc)... : ) Nice riddle Kind regards Sébastien

Paul · Answer

What's the filetype?

Paul · Answer

Hi Nora, 
 I've been spending the last 20 mins or so doing exactly the same thing and I could not make it work! I started with what you got here and it failed, so I created all kinds of complicated rules to try and do this and I could not. 
 So I then thought, after seeing your post, why does it work for you and not for me. I was originally using the new Word filetype and I get this: 
 
 So I changed the filetype and used the old one... now I get this: 
 
 Until now I had no idea that the filetypes for Word could cause this difference. I don't know what to make of this so will log it with support to confirm whether it's a bug or otherwise. But thank you... I was beginning to think there was a problem with the segmentation rules editor!! 
 Hopefully this will work for Michael too. 
 Regards 
 Paul

Paul · Answer

Sorry Michael... I hijacked your question! Hopefully changing the segmentation rules will work for you and the filetypes you are working with.

Paul · Answer

Hi Sébastien et al, 
 
Nice work tracking this one down. I did log a case but will send a copy to our filetype developers as this is really interesting and worth a look. 
 
Cheers 
 
Paul

Paul · Answer

Hi Sébastien et al, 
 
Just a brief update on this one. A defect has been logged with development for resolution because this can affect segmentation under the "right" circumstances as I found out completely by accident! 
 
The workarounds if you have this for the time being are: 
 
- process the file with Word 2007 v 2.0.0.0 
 
or 
 
- mark text as “not to be spellchecked” (Review>Language>Do not check spelling or grammar), re-save and process with ML v. 2 filter. 
 
Thanks again for working through this one! 
 
Regards 
 
Paul

Trados Studio > 1. Trados Studio

\r\n style line feeds/breaks