When attempting to finalise one or more target files, error task(s) are produced. Accepting them in your Inbox, and opening them, the error detail shows:



One or more of the segments in the source file(s) are split across two or more lines.

 

Workaround for Current Projects

 

1. Having accepted the task in your Inbox, and opened it, click the Open in Online Editor button.
    
2. Locate the first segment that is split across two or more lines.
    
3. Copy / paste the target segment into a text editor. We recommend using Notepad++.
    
4. Click the Clear Target button on the Home ribbon.
    
5. Copy / paste only the first line of text from the text editor into the target in Online Editor.
    
6. Press [SHIFT] + [ENTER] on the keyboard to insert a valid end-of-line (EOL).
    
7. Copy only the second line into the target segment. If there are more segments then press [SHIFT] + [ENTER] to insert another EOL, and repeat the process for additional segments, however do not press [SHIFT] + [ENTER] after the final line.
    
8. Insert any tags in their correct places according to the source.
    
9. Open the Revisions Panel using the button on the right hand side.
   
   
    
10. Click the Accept All button.
     
11. Locate the next segment split across two or more lines, and repeat steps 3 to 10.
     
12. Close Online Editor.
     
13. Click the Retry button to retry the Error Task.

Workaround for Translation Memories

If the problematic translation(s) came from the Translation Units (TUs) of one or more of the Translation Memories (TMs), then we recommend exporting the affected language pair(s) to a TMX file, removing any occurrences of 
 and then recreating that language pair in the TM.
 

Removing the code from small to medium Translation Memories

Having identified the language pair(s) in the TM(s) that contained the problematic TU, follow the steps below for each one:

1. Export the language pair to a TMX file.

2. Open the TMX file in Notepad++.

3. Click Search -> Replace...

4. In the Find what : field, put 
 and make/leave the Replace with : field blank. Set the rest of the options as below:
   
   

5. Click the Replace All button, followed by the Close button (when the replace operation completes).

6. Save the TMX file, and exit Notepad++.

7. Delete the affected language pair from the TM, and save the changes.

8. Add the affected language pair to the TM, and save the changes.

9. Import the TMX file you modified into your TM.

Removing the code from large Translation Memories

WARNING: These instructions should be followed by advanced users only. If you are not confident in performing these steps the please log a Support Case, and we will be happy to assist you.

If your TMX file is very big then Notepad++ may be unable to open it, or your computer may freeze. The solution below may be used in place of steps 2 to 6 above.
 

awk (UNIX / Cygwin / macOS / Linux)

Where export.tmx is the name of the TMX export, and fixed.tmx is the name of the version with the code stripped:

awk '{gsub("
", "");print}' export.tmx > fixed.tmx

 

Underlying Cause

This issue occurs because there is a code before the end of the first line of the segment, which is the Unicode hex character for a carriage return (CR). This code is converted into an actual CR and then, before generating the target, Trados Trados Cloud / Enterprise / Live attempts to convert DOS/Windows-type end-of-lines, which use CRs plus line feeds (LFs), into UNIX-type end-of-lines, which are LF only. So, instead of being able to convert CRLF into LF, the affected lines have CRCRLF, and the process fails.
 

Scenario 1 - Copy / pasted text from other applications

This can happen if you copy / paste text from a web browser or a rich text application such as Word, Excel, etc. into one or more target segments in either Trados Studio or Online Editor.
 

Scenario 2 - Translation came from a Translation Memory

During Translation Memory (TM) matching, the affected target segment came from a Translation Unit (TU). In this situation it is sensible to export the TM (or at least the affected language pair) into TMX format, check the entire TMX for other occurrences of 
 and, if found, to remove them and recreate the TM / affected language pair.
 

Defect

A defect has been logged for this issue, and a fix is expected in a future release of Trados Cloud / Enterprise / Live.