Segmentation rules foe Excel files with DeepL integration

Hey!

I have been researching segmentation rules, but I didn't find a solution that works for my case. From what I have seen, the regular approach would be to do a segmentation rule within a new translation memory. However, I didn't find a way to use DeepL íntegration as well. Whenever I use the DeepL integration and a translation memory, DeepL gets an orange highlight in the list alongside an error message.

I have a client who sends over Excel files with several big cells containing HTML code. The lines would always start with < and end with >.

Now, I would love to load the project file in and having it separated by each paragraph. At the same time, it could also be automatically be translated using the DeepL integration, so I only have to fix issues from there. Not using a line break rule so far only ends me up getting the entire cell in one line and manually line breaking in the target takes way too long.

Since I don't know if you could use a TM with a segmentation rule and DeepL as a translation source for it to work out, I guess I will also need a new project template to make it work? The files are always rather extensive, so I would love to not having to translate it manually.

How do you set up the segmentation rule for <> lines apart from that setup?

Thanks!

emoji
Parents
  • Hey!

    Thank you for making that video. I followed the steps and entered all of the separate rules for the tags. However, when I let it translate using my usual project template, the overall quality is a lot worse due to all the tags in the segments, I guess. Translating the cells in Excel one by one is a lot more manual work, but the translations end up being better by a long shot. Too bad that I might not be able to use Trados for this client. Is there something else we could try to improve the overall translation quality as well? The translation volume of this client is pretty high and I have yet to find an optimal way to make it efficient.

    Thanks!

    emoji
  • However, when I let it translate using my usual project template, the overall quality is a lot worse due to all the tags in the segments, I guess.

     

    I don't really understand this, what do you mean by your usual project template?  You just changed all the rules so that you use a project template with the new rules for all your projects using these files.  The tags are in there because they are html tags and they are inline.  You cannot avoid them based on the type of content you have.  If you exclude them all then the sentences will also break up into small chunks and I doubt you want that either.  From what you have written in reply I suspect you simply don't know how to work with tagged files... but I can't be sure because the problem may be you just don't know how to work with project templates.  I really don't know.

    Maybe you can share a screenshot of what you see when you have finished translating a few segments, and show us the Excel filetype settings for your new project?  It's really hard to truly understand what you are saying and match that to what you should be doing.  The example file you gave me should be trivial to handle in Trados so I really don't know why you think you cannot use Trados for this.

    Is there something else we could try to improve the overall translation quality as well?

    I think we need to make sure you are handling these files properly first!  The translation quality is something that is 100% down to you and you surely know this.  So let's just make sure we're both talking and thinking about exactly the same thing!

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
Reply
  • However, when I let it translate using my usual project template, the overall quality is a lot worse due to all the tags in the segments, I guess.

     

    I don't really understand this, what do you mean by your usual project template?  You just changed all the rules so that you use a project template with the new rules for all your projects using these files.  The tags are in there because they are html tags and they are inline.  You cannot avoid them based on the type of content you have.  If you exclude them all then the sentences will also break up into small chunks and I doubt you want that either.  From what you have written in reply I suspect you simply don't know how to work with tagged files... but I can't be sure because the problem may be you just don't know how to work with project templates.  I really don't know.

    Maybe you can share a screenshot of what you see when you have finished translating a few segments, and show us the Excel filetype settings for your new project?  It's really hard to truly understand what you are saying and match that to what you should be doing.  The example file you gave me should be trivial to handle in Trados so I really don't know why you think you cannot use Trados for this.

    Is there something else we could try to improve the overall translation quality as well?

    I think we need to make sure you are handling these files properly first!  The translation quality is something that is 100% down to you and you surely know this.  So let's just make sure we're both talking and thinking about exactly the same thing!

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
Children
No Data