Hi Michael,

I'm not sure if this is a problem we have logged but a quick test gives some interesting results for me.  Just a few tests and their results:

Using your source:

Changing the & symbol to a % symbol:

Changing the & to another letter:

So I think you're right that the $ symbol is causing a problem here and I'll follow this up.  But in the meantime maybe you could use a workaround for this and search replace the source using the SDLXLIFF Toolkit using something unlikely to appear in other scenarios, maybe %%% instead of the $.  Then search replace again afterwards?

I know this is far from ideal, and you would probably want to update your TM again when you were done so it didn't contain %%% in the source TUs, but if you use a scratch pad TM for updating during the translation itself then it might not be too much work.

But I will make sure this is logged.

Regards

Paul

Hi Michael,

I'm not sure if this is a problem we have logged but a quick test gives some interesting results for me.  Just a few tests and their results:

Using your source:

Changing the & symbol to a % symbol:

Changing the & to another letter:

So I think you're right that the $ symbol is causing a problem here and I'll follow this up.  But in the meantime maybe you could use a workaround for this and search replace the source using the SDLXLIFF Toolkit using something unlikely to appear in other scenarios, maybe %%% instead of the $.  Then search replace again afterwards?

I know this is far from ideal, and you would probably want to update your TM again when you were done so it didn't contain %%% in the source TUs, but if you use a scratch pad TM for updating during the translation itself then it might not be too much work.

But I will make sure this is logged.

Regards

Paul

Just slogging through 21k words and 90% of them start with <p> which means I'm not getting ANY matches for anything. Sure would be have been nice if ...

Hi Michael Bauer

&lt; and &gt; are "<" and ">" in escaped HTML. Are you working on an XML file? &lt;p&gt; is <p>. I think you should be eliminating these characters at the parsing stage. Wrong file format?

Daniel

You'd be surprised at the number of big software houses that do their localization by sending out xml or html as text for translation ... yes, I agree it's not a good format to be working in but I can't change what the clients send out, sadly.

if it's a software house, then you get the files in source format, not as (already screwed-up) SDLXLIFF, I suppose...
I.e. you can easily process them as it should be, right?