Marie Soltendieck

It is possible:

I guessed your file looked something like this?

simple.po

I achieved this by using a TM that has paragraph segmentation which forces the normal sentence rules to be ignored in favour of what Trados considers a paragraph.  So just use a TM when you create your project that has paragraph segmentation rules:

Marie Soltendieck

It is possible:

I guessed your file looked something like this?

simple.po

I achieved this by using a TM that has paragraph segmentation which forces the normal sentence rules to be ignored in favour of what Trados considers a paragraph.  So just use a TM when you create your project that has paragraph segmentation rules:

Hi Paul! Thanks a lot for all this!

I've tried using the paragraph segmentation - and it actually made matters worst. Here's a photo of just one of problematic segments. (What happens is that studio considers each MSGTR as single segment.)

The sentence based segmentation works better - but I still end up with segments looking like this:

Ideally, I'd like to continue using the sentence-based segmentation, which already breaks down the strings from the PO file into more manageable segments, and enhance the feature to define \n, and even </p> as break characters in the segmentation rules, much in the way a period or a hard break is handled in regular text documents. Is it possible?

I tried the following from one of your earlier posts: 

Before break:

.[\n]+

After break

.

But it didn't work.

There's gotta be a way to make this work - am I wrong in thinking the answer lies in a clever regex segmentation rule? 

Marie