I'd say it's related to the segmentation issues described at  (though that post describes different issue).

Basically, the segmentation component does not concern the internal tag being the "anything following the space which follows the punctuation" part of the segmentation rule...

AFAIK, there is nothing you can do about it.

BTW, I'm wondering if the segmentation would work as expected even without this problem... the thing is that in the last two cases of <br> on your screenshot there is no space after the fullstop, so it's questionnable whether the segmentation engine would catch this as well...

Hi Paul,

I had a look and yes, the source text is already copied into the target segment :-(

Two further questions:

1) Is this target-copy an option that the customer can chose on exporting the file? So we can ask him not to copy the source to the target?

2) Do you have an idea how to batch delete all target segment text? Ist there a regex for deleting everything inbetween <target state="needs-translation">einmaliges akustisches Signal</target>

Thnx a lot.

Burim

Hi Paul,

thnx a lot. The regex find all segments that start with <target... but I need only the ones starting with <target state="needs-translation">.

And when replacing I get: $1$2

Best regards

Burim

Hi Paul,

the two problems:

1. I tried deleting the target segments that need translation only in excel and it does work. The new empty segments are correctly segmented. The other translated ones stay as the are.

2. I use Notepad++

$1$2 replaces exactly with $1$2

\1\2 deletes the first letter inbetween the tags

Burim