• State Suggested Answer
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 432 subscribers
  • Views 3328 views
  • Users 0 members are here
Options
Related

Modifying a TM: splitting translations, separated by a soft line break

Jerzy Czopik

Does anyone have an idea, how could I modify my TM, so that instead of a segments like these:

• Ölauffangwanne und Kondensatsammelbehälter, Absperrhähne und Zuleitungen im einsehbaren Bereich reinigen <manual soft line break>
• Sichtprüfung durchführen

I could have

Segment 1:
• Ölauffangwanne und Kondensatsammelbehälter, Absperrhähne und Zuleitungen im einsehbaren Bereich reinigen

Segment 2:
• Sichtprüfung durchführen

_________________________________________________________

When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Does this not work? It should...
    community.sdl.com/.../49117
    There is also a knowledge base article saying basically the same...

    If it doesn't work, then you are maybe also hit by the linebreak segmentation issue present in Studio 2017 SR1 and newer...
  • 0 in reply to Evzen Polenka

    Different story here.

    In my case I have an old TM, where the translation was done for an Excel file and at that time the "manual line break" was not set to be a segmentation rule.

    So I have segments inside like those:

    Now I have pretty the same file, but I did get it via MemoQ from Transit and the same segments are now split by the manual line break, like this:

    So what I needed was to produce a translation memory, having the segments shown previously split like the files are now.

    In the end of the day I've managed that by exporting that part of TM, which contained the translation for the files from the past to TMX. Then I've located the places where the manual line breaks were (it was a bit tricky, as I did only need to keep those followed by •), then I've done some search and replacing, exported to Wordfast TXT, opened in Excel, replaced all the codes I entered by a manual line break in Excel. Then copied the whole table to Word and back to a new Excel sheet. As the manual line break from Excel is recognized by Word as ^l (manual line break), but this manual line break (^l in Word) is NOT recognized by Excel as manual line break, but as a line break, Excel broke the units as needed to separate lines - and this way, after having copied the Excel to Notepad++ I stored that as tab delimited file and created a new TM out of it in Olifant.

    That's the whole story - and it seems to have worked, so might very well be, that I saved me about one day on translation work that way.

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

Reply
  • 0 in reply to Evzen Polenka

    Different story here.

    In my case I have an old TM, where the translation was done for an Excel file and at that time the "manual line break" was not set to be a segmentation rule.

    So I have segments inside like those:

    Now I have pretty the same file, but I did get it via MemoQ from Transit and the same segments are now split by the manual line break, like this:

    So what I needed was to produce a translation memory, having the segments shown previously split like the files are now.

    In the end of the day I've managed that by exporting that part of TM, which contained the translation for the files from the past to TMX. Then I've located the places where the manual line breaks were (it was a bit tricky, as I did only need to keep those followed by •), then I've done some search and replacing, exported to Wordfast TXT, opened in Excel, replaced all the codes I entered by a manual line break in Excel. Then copied the whole table to Word and back to a new Excel sheet. As the manual line break from Excel is recognized by Word as ^l (manual line break), but this manual line break (^l in Word) is NOT recognized by Excel as manual line break, but as a line break, Excel broke the units as needed to separate lines - and this way, after having copied the Excel to Notepad++ I stored that as tab delimited file and created a new TM out of it in Olifant.

    That's the whole story - and it seems to have worked, so might very well be, that I saved me about one day on translation work that way.

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

Children