Have you defined the TXT embedded content processor in your XML file type? If so, did you enter a proper structure information in all relevant tags?
If yes, try to use {[^}]*} or at least {.*}, but the second one will mask ANYTHING between [ and }, which will result in wrong parsing. Your rule has an error - you used {*.}... You can also test {.+?} - this means { followed by at least one character and stopping when } is found (lazy rule).

But why don't you simply use XML parser with legacy embedded content and use the same regex, but there?

Thanks for your reply Jerzy,

I defined the TXT ecp in the XML file type. {.+?}, and defined the below settings as the rule (also tried with "{[^}]*}" ), but the brackets are still shown as plain text..

I haven't tried the legacy embedded content processer, is it better? Will give it a shot on Monday morning!

Wish you a good weekend,
Simon

May I join the discussion? I had a very similar problems and using Embedded plain text plus correctly configuring the ECP in the filetype worked well.

The only thing i couldn't do is this:

Between my XML segments I have something like this:

La corretta installazione della macchina.{CR}La conoscenza del funzionamento

 Where {CR} would be the paragraph break character.

Is there any way I can tell trados to use it as a segment split character (and of course hide it)?

May I join the discussion? I had a very similar problems and using Embedded playing text plus correctly configuring the ECP in the filetype worked well.

The only thing i couldn't do is this:

Between my XML segments I have something like this:

La corretta installazione della macchina.{CR}La conoscenza del funzionamento

Where {CR} would be the paragraph break character.

Is there any way I can tell trados to use it as a segment split character (and of course hide it)?

BTW, you will not use all this information in Trados - it is SDL Trados Studio, where it is applicable :=

Unknown said:

Between my XML segments I have something like this:

La corretta installazione della macchina.{CR}La conoscenza del funzionamento

 Where {CR} would be the paragraph break character.

Is there any way I can tell trados to use it as a segment split character (and of course hide it)?

Hi Enrico,

To do this you need to create a segmentation rule on your TM.  I guess the lack of a space after the period is preventing the segmentation normally.

Regards

Paul

Paul: I did this, but it leaves the {CR} inside the segment. (and this produces huge amount of fuzzies :-P )

Hi Enrico,

ok - after you managed to split the segments with a segmentation rule and you end up with this:

La corretta installazione della macchina.{CR}

La conoscenza del funzionamento

You just need to make a tag excluded like this:

Now it should be perfect!

Regards

Paul

Unknown said:

Oh, this is what exclude stands for. And now I understand, why it does NOT segment here.
Would it be possible to add that so far to the embedded content? Otherwise we will need to create special TMs for such cases...

Hi Jerzy,

I recall asking for this a long time ago and there are technical limitations apparently because of the way the files are converted to sdlxliff.  I think you just need to knock up a set of rules for your TMs when needed, and use them for segmentation only with no read/write capability.  Would be easier if it was possible on the filetype I agree... but it's not :-(

Paul

Unknown said:

Oh, this is what exclude stands for. And now I understand, why it does NOT segment here.
Would it be possible to add that so far to the embedded content? Otherwise we will need to create special TMs for such cases...

Hi Jerzy,

I recall asking for this a long time ago and there are technical limitations apparently because of the way the files are converted to sdlxliff.  I think you just need to knock up a set of rules for your TMs when needed, and use them for segmentation only with no read/write capability.  Would be easier if it was possible on the filetype I agree... but it's not :-(

Paul

Hi Jerzy,

I recall asking for this a long time ago and there are technical limitations apparently because of the way the files are converted to sdlxliff. I think you just need to knock up a set of rules for your TMs when needed, and use them for segmentation only with no read/write capability. Would be easier if it was possible on the filetype I agree... but it's not :-(

Paul