sample file ?

Hi Kelly,

Here is one example of the 4500+ errors I get from both the built-in QA system and the Number Verifier Plugin:

As you can see, the number it self hasn't changed at all - just the unit.

In other cases, a source number written like this "2000€" with a target number written like this "2 000 €" will trigger an error.

I have no idea why or how to solve this.

Can you or anyone help me?

Ingrid Fischer said:

"2000€" with a target number written like this "2 000 €"

this one is a different case.

In terms of "numbers" You should have warning.
"2000" vs "2" "000" is different, Period.

But, of course, You could have "Exception rules", I guess.
(for instance, should you have "units" at the end of "numbers and spaces" sequence then the spaces in that sequence could be omitted. etc..)
(of course, it cause You extra cost)

Lastly, it is not a "sample file".

Regards

as is

hmm, just out of curiosity
How did you put every and single space in big numbers as a thousand separator ? thousand of them, manually ?
-and again, a space between number and its following unit.

Hi and thanks for your answer :)

Well, I cannot just omit those space, as they are mandatory in French (separators between number & unit + between groups of threes). I do have this issue with each every file, always, even though my project is set on "French language" with French rules. I don't understand why and I have no idea how to change those parameters so that Trados know how to deal with numbers.

I admit I don't know how to create a "sample file" either. I guess I should create a new project by copy/pasting parts of an already translated file and then let the TM retrieve those segments? If so, I'll try later on as I'm smashed right now, precisely trying to come to terms with those numbers :/

As for now, I simple add those space manually. Propagation then helps a lot with the following segments, but I still have a lot of changes to do. This doesn't really matter to me. The biggest issue is that I get a wrong "error" result for each segment with a number in it :/

Is there any known way to tell Trados that those spaces are normal and it should only check for the number itself, not the alphanumeric sequence?

Hi and thanks for your answer :)

Well, I cannot just omit those space, as they are mandatory in French (separators between number & unit + between groups of threes). I do have this issue with each every file, always, even though my project is set on "French language" with French rules. I don't understand why and I have no idea how to change those parameters so that Trados know how to deal with numbers.

I admit I don't know how to create a "sample file" either. I guess I should create a new project by copy/pasting parts of an already translated file and then let the TM retrieve those segments? If so, I'll try later on as I'm smashed right now, precisely trying to come to terms with those numbers :/

As for now, I simple add those space manually. Propagation then helps a lot with the following segments, but I still have a lot of changes to do. This doesn't really matter to me. The biggest issue is that I get a wrong "error" result for each segment with a number in it :/

Is there any known way to tell Trados that those spaces are normal and it should only check for the number itself, not the alphanumeric sequence?

Ingrid Fischer

Have you tried using this setting

This works for me and always inserts a non-breaking space between the number and the unit.

Gbps => Gbit/sec is an exception as this isn't recognised.  But you would get this 200Gbps => 200 Gbps and then you could search replace the Gbps in the target afterwards.

Thank you Paul, this hack is exactly what I was looking for to speed up the translation process :D

I am not sure how it will impact my first issue of numbers in the source text being recognized as alphanumeric sequences, but i'll keep you posted :)

Ingrid Fischer

Ingrid Fischer said:

this hack is exactly what I was looking for

I'm glad... but this isn't a hack!

Hi Paul,

I tried this option (sorry, not hack ;)) on another project:

... but I still get the exact same error:

Do I need to do anything else to get the editor to take this setting into account?

Sometimes I feel like getting to know all the functionalities of Trados is harder than learning a new language

Ingrid Fischer

Ingrid Fischer said:

Sometimes I feel like getting to know all the functionalities of Trados is harder than learning a new language

Definitely not!!  At least not from my perspective.

When you show this screenshot can you make sure that this segment is the active segment please?

Thank you. 

Yes, here it is:

Do you have any idea what could be the matter?

Ingrid Fischer

I'm not sure... I ran a quick test and see this:

That was the out of the ox QA checker with these settings:

Do you have any custom QA rules set up?

Maybe we can take a quick look if you have the time right now?  Drop me an email if you do - pfilkin@rws.com

Before running QA Checker make sure the following option is ticked. This works for me.