Enrico Rosso

Enrico Rosso said:

Sadly it recognizes as an Alphanumeric String even the [0-9]-[A-Z]+ regular expression, producing wrong results as you can see below:

I don't really understand this... if this is a filtered set of results why is this wrong as they all match your expression?

Default settings on a TM should give this which seems to be correct:

Have you tried reindexing your TM?  It feels as though it's getting confused.

Enrico Rosso

Enrico Rosso said:

Sadly it recognizes as an Alphanumeric String even the [0-9]-[A-Z]+ regular expression, producing wrong results as you can see below:

I don't really understand this... if this is a filtered set of results why is this wrong as they all match your expression?

Default settings on a TM should give this which seems to be correct:

Have you tried reindexing your TM?  It feels as though it's getting confused.

Hello Paul and thank You for answering.

I'm afraid I wasn't clear enough in explaining my issue:

The translation should be like that:

2-LENTA = 2-SLOW

3-VELOCE = 3-FAST

4-RALLENTA = 4-SLOW DOWN

Instead Studio considers them as placeables and just copy them to the target, accounting those segments as a CM or 100%, instead they're no matches.

So the TM actually works as expected, but the mechanism generates an issue.

If the character "-" wasn't considered in an alphanumeric string, it would work like a charm, i would have a number and a word for each segment.

I can separate and join again the strings before and after translation, but this could add a lot of overhead to the translation process.

I understand this kind of settings are like a blanket too short to cover everyone, I'm writing this in hope something can be done or planned for a future release, in order to always improve studio the way SDL keeps doing.