Alberto Iturbe

Try creating a TM that has paragraph segmentation,  Then when you open your Excel file with this TM each cell should be a separate segment.

How can I do that?

Alberto Iturbe

You didn't tell us what version of Studio so here's 2021:

That is great! Thank you.

One last question, if I change those settings in a TM of project I am already working on, does it work on the files of that project which is half-way through?

Alberto Iturbe said:

One last question, if I change those settings in a TM of project I am already working on, does it work on the files of that project which is half-way through?

No. You have to start again, as the files are already segmented.

You can also use the same TM with no segmentation change, but instead of Excel file type use Bilingual Excel. This, however, will work only, if you have a source column and a target column. If the complete Excel file is to be translated, you have to change the segmentation.

Alberto Iturbe

Interestingly if you work the other way around you can do this.

First start with my Excel file:

Create a project using a standard sentence based segmentation.  Translate the sentences you want:

Now update the same source file with a paragraph segmented TM attached to your project (note I disabled my sentence based and enabled my para based):

Update the file:

Now I have this:

I have no idea why I'd want to do this, and nor do I have any idea why it doesn't work the other way around because I expected it to.  But it's interesting... and I'll log it as a bug/enhancement because I think it should work.

Alberto Iturbe

Interestingly if you work the other way around you can do this.

First start with my Excel file:

Create a project using a standard sentence based segmentation.  Translate the sentences you want:

Now update the same source file with a paragraph segmented TM attached to your project (note I disabled my sentence based and enabled my para based):

Update the file:

Now I have this:

I have no idea why I'd want to do this, and nor do I have any idea why it doesn't work the other way around because I expected it to.  But it's interesting... and I'll log it as a bug/enhancement because I think it should work.

Alberto Iturbe

There is a good argument for why it won't work the other way around of course.  If you had translated a paragraph, and used two sentences in the target, or four even, where the source had three then how should Studio handle this?  Where should it put the translations?

I think we could allow this if the para segments were empty, or always put the translations in the first segment only for example.  So some sort of rule... but I think this is probably why it doesn't work the other way around.

Why do you want to do this?  Is it because you want the right segmentation for each cell?  In this case perhaps the right answer is actually to simply delete the full stop rule and then you always get this:

Each cell treated exactly as you want.

Yes, that's right, I want the right segmentation for each cell. That full stop rule is what I was looking for initially, where is that?

Same place as you set the para segmentation Alberto Iturbe

Perfect, that's great.

Hi Paul,

If I need to translate 15 languages with a bi-lingual excel file, and there are already 15 TM files with sentence based segmentation, should I change the TM files one by one to paragraph based?

Is there are a convenient way?

And after the excel project's over, I need to change the segmentation in TM back to sentence based to apply word files in other projects.

Linus Wang

Linus Wang said:

If I need to translate 15 languages with a bi-lingual excel file, and there are already 15 TM files with sentence based segmentation, should I change the TM files one by one to paragraph based?

You tell me!  I have no idea what the content is in your files or why you might want to do this.

As you can see below, I don't want the contents in one cell to be split into different segments.

Should I change the segmentations in 15 TM files to paragraph based for this project?

Linus Wang

For this you should simply add "Maint." to your abbreviations list and then it won't segment there.  You will need to make this change to all 15 TMs but this is made easier if you use the ApplyTM Template application from the appstore:

https://appstore.sdl.com/language/app/applytm-template/966/