Hi Fouad,

I usually use Olifant to clean up TMs. If you can identify a specific break character or pattern you could find and replace this pattern, adding the string [$SPLIT$] where you want the split to occur. See:

okapi.sourceforge.net/.../mnu_entries.htm

Stephan

Hi Stephan,

Basically, the break should be according to the default Studio segmentation.

Can this be set by a filetype setting that i've created?

Best Regards

Fouad

There's no way to perform this kind of operation directly in Studio, so I'm afraid it's not as simple as applying a file type to your TM (though that would be a neat feature for future versions of Studio, cause I have a similar cleanup job coming up myself ;)).

Assuming you do use Olifant to split the segments, and you just want to apply basic segmentation rules, it could be as simple as splitting at periods or semicolons.

So you'd open your TM in Olifant and use the following search/replace patterns:

Find: ". "

Replace with: ". [$SPLIT$]"

When you have done that, select all segments and use the split command. Then import the clean TMX into a new SDLTM.

If you need to, say, split after all tags in a TM, you'd have to use regex:

Find: \<.*\>

Replace with: $& [$SPLIT$]

Make sure that "use regular expressions" is checked when you do this.

There are some helpful examples of how to use regex in Olifant here: http://okapi.sourceforge.net/Release/Shared/Help/regex.htm

Hi Stephan,

This doesn't work.

Can i send you the TMX by email?

Best Regads

Fouad

Hi Fouad,

I can give it a shot, sure. I can't guarantee though if I can get to it straight away. I'll have a look at it, but if it's not straightforward I may have to deal with it later.

You can send it to stephan dot gasteyer at gmail dot com. Also, don't forget to let me know exactly where you want the break to occur.

Cheers

Stephan

Thanks

Just sent!

BR

Fouad

Oh dear... One problem might have been the regex I gave you didn't work. I'm Sorry.. :(

I just sent you a new copy of the file. This is what I did:

I first searched for <.*?> and replaced with $&[$SPLIT$] to add split markers after all the tags. For some reason Olifant won't split next to tags though. However, the tags don't look like they should go into translatable segments at all, so I stripped the file off the tags completely, and performed the split afterwards.

Then I simply split after periods as mentioned above, and removed any stray split markers that were left because of a mismatch of periods in the source and target segments.

I didn't touch the colons though, as different punctuation seemed to be used in EN and IT (e.g. dashes in EN were replaced with colons in IT), and I was worried I might break more than I fix.

I did a couple spot checks, and overall the new file looks OK. Still what I did was purely mechanical, so it might be advisable to apply a penalty to the TM just in case some segments are mismatched.

Let me know if you get better results with the new TM.

Ta

Stephan

Hi,

It will be good to know if this useful response from Stephen works... but in the meantime I'll add another that might be useful.  There is an application on the OpenExchange called SDLTmConvert which can convert an SDLTM to a CSV file.  So if your efforts with Olifant are unsuccessful you could use this to then create two CSV files, one with the source only and one with the target.  Then you align the two files in Studio and this time the paragraphs with multiple sentences will be segmented correctly allowing you to create a new SDLTM to use.

The drawback of this might be how it handles tags because I have no idea how complex the information in your TM is, but if you are happy with a text only TM then this might be a simple way to tackle the problem.

I like the Olifant solution though... it's a good tool if you're careful.

Hi,

It will be good to know if this useful response from Stephen works... but in the meantime I'll add another that might be useful.  There is an application on the OpenExchange called SDLTmConvert which can convert an SDLTM to a CSV file.  So if your efforts with Olifant are unsuccessful you could use this to then create two CSV files, one with the source only and one with the target.  Then you align the two files in Studio and this time the paragraphs with multiple sentences will be segmented correctly allowing you to create a new SDLTM to use.

The drawback of this might be how it handles tags because I have no idea how complex the information in your TM is, but if you are happy with a text only TM then this might be a simple way to tackle the problem.

I like the Olifant solution though... it's a good tool if you're careful.