sampleCRLF Plain.xlsx

..somewhat tricky though.. done..

my steps are,, I am writing it just because descripting what I have done and do not have any kind of other meanings.

1. changed NewLine into some extremely used special character (in Korean "힣") at Excel OOXML level

2. made a Trados project while subjecting modifiedSegmentationRules (seperate sentences on the basis of "힣")

3. at the Target sdlxliff file, kills all "힣"

4. now you see the result.

-end-

..somewhat tricky though.. done..

my steps are,, I am writing it just because descripting what I have done and do not have any kind of other meanings.

1. changed NewLine into some extremely used special character (in Korean "힣") at Excel OOXML level

2. made a Trados project while subjecting modifiedSegmentationRules (seperate sentences on the basis of "힣")

3. at the Target sdlxliff file, kills all "힣"

4. now you see the result.

-end-

Hi Kelly,

I appreciate you taking the time to reply to my post with such detail.

Indeed, something was wrong: Excel and Trados XLSX/XLX processor. The solution? Save a copy as an Open Document Spreadsheet (ODS). That mitigated the segmentation issue.

However, I sacrificed a few perks, like the embedded content processor and the color/column filter.

Your clever solution keeps you in the XLSX/XLX processor, and you'd only need to find/replace the special character later with a line feed char.

I am taking notes and adding this to our knowledge base.

Have a fantastic weekend,
JD

—

Paul, it's worth mentioning that this file came from Google Sheets and that we have experienced similar segmentation or unexpected content error messages in the past few weeks.

do not have to stick strange Korean character.

Just use rather familiar character, for instance "bullet" or something

and keep it at the end of the game

I hope you got my point here clearly.

Good Luck to You

Joshua D. Velásquez

The problems seems to stem from the formatting on the text.  If you remove the formatting and work with plain text it works as expected.  We have logged a bug for this which is our reference CRQ-27921 just so it's easier to follow up if needed in the future.

Thank you so much, Paul. Yes, it's something between Excel and the complex (?) cell formatting. Another workaround is to save it as an ODS document. I appreciate you for submitting this bug to the dev team.