Nathanael Fourie 

Have you tried searching for \.$ and leaving the replace blank?

It seems so simple I'm wondering what you're not telling us?

Nathanael Fourie 

I just installed the toolkit and tested to be sure..

It finds it in the search:

The preview shows it replaced:

But then the actual replace operation fails!

So perhaps this is really what your question relates to?

Lydia Simplicio  - one to log for resolution :-)

Thanks Paul 

Your code worked. Searching for (.+). and replacing with $1 also works.

From SDLXLIFF Toolkit, I tried it on a few test sdlxliffs, and then on the actual, live project source sdlxliff.

Using Notepadd++, I can see that the full stops have been removed, but when I open the file in Editor the full stops are still all there. 

Is there something I'm doing wrong?

Nathanael Fourie 

Indeed... in fact a better code for me is \.+$

But this won't work anyway as it seems to be a bug in the toolkit.  It works in target... but not in source.  So yo are not doing anything wrong... the plugin needs fixing.

Ok, thanks, Paul !

Any other way you can perhaps think of (that actually works) to remove all the full stops from the end of the source segments, without having to do it by hand?

I've got close to 2000 source segments to edit, and I'd really like to get to the actual translation. Big deadline for tomorrow... :&

 Nathanael Fourie 

You could take a copy of the sdlxliff and do it in a text editor using regex?  Test the sdlxliff afterwards and if you didn't break it you're good to go.  For example:

Search for:

(<source>)([^.<]+)\.+(</source>)

Replace with:

$1$2$3

But be very careful and check it.  I don't have your files and the very simple test I just did with my own file may not match what you have.  So take this approach:

1. Back up your current sdlxliff file from your target folder by copying it into a new folder somewhere safe.  Then you can easily put it back
2. run the search and replace on the sdlxliff file in your project in a decent text editor
3. open the project and test it to make sure of the following at least:
   1. you can still open it,
   2. the changes are correct, 
   3. you can save a target file
   4. etc.

If anything is broken you easily recover by copying the one you backed up back into the project.  In fact I think I'd even back up the original project just to be sure!!  It's always risky playing with sdlxliff files natively, but it can indeed be a quick way to make changes if you're comfortable with it and understand the risks.

 Nathanael Fourie 

You could take a copy of the sdlxliff and do it in a text editor using regex?  Test the sdlxliff afterwards and if you didn't break it you're good to go.  For example:

Search for:

(<source>)([^.<]+)\.+(</source>)

Replace with:

$1$2$3

But be very careful and check it.  I don't have your files and the very simple test I just did with my own file may not match what you have.  So take this approach:

1. Back up your current sdlxliff file from your target folder by copying it into a new folder somewhere safe.  Then you can easily put it back
2. run the search and replace on the sdlxliff file in your project in a decent text editor
3. open the project and test it to make sure of the following at least:
   1. you can still open it,
   2. the changes are correct, 
   3. you can save a target file
   4. etc.

If anything is broken you easily recover by copying the one you backed up back into the project.  In fact I think I'd even back up the original project just to be sure!!  It's always risky playing with sdlxliff files natively, but it can indeed be a quick way to make changes if you're comfortable with it and understand the risks.