Ian Keith Jones Williams

Where did you make these changes and when?  So was it in File -> Options or your Project Settings?  If you're changing under File -> Options after the project was created this will have no effect at all.

Project settings after the project was created

Ian Keith Jones Williams

Could it be that you have also used the language specific verification settings?  Perhaps this is overriding your choice?

Under Language Pairs? I don't touch Verfication under Language Pairs if that is what you mean

Ian Keith Jones Williams

Did you add your TMs at that level?  I'm not sure if this is the cause, just exploring the possibilities until I'm in a position to test this myself.

Yes

Ian Keith Jones Williams

In this case try adding the verification setting at the specific language level too.

Sorry for not getting back sooner but I was busy and verification failed on this project in the end. I am now doing similar projects. I have now changed to Studio 2021 but I am still getting the same problem. It does not matter whether the language specific verification settings are configured or not.

Hi, I am having the same problem with Studio 2022. Was it solved?

Also, please note that it is not detecting the "30", also present in the Spanish segment.

Any ideas?

Thank you,

Pilar

Hi Pilar García-Romeu ,

Pilar García-Romeu said:

Hi, I am having the same problem with Studio 2022. Was it solved?

Could you please test the following? If PMs are locked, as they are by default, untick the first check box to exclude PMs and then Verify.

Solved?

If it is not soved, test the other way around: tick to exclude PMS, untick to exclude locked segments.

Pilar García-Romeu said:

Also, please note that it is not detecting the "30", also present in the Spanish segment.

I think this is due to fact that min is a measurement, and Trados didn't find any measurement in Source (Minutes is not recognized by default). To test this assumption, please change min to something else, such as minutos, and Verify again.

Warning gone?

Don't forget to revert it back to min with CTRL+Z.

Hi Jesús,

Thanks for your reply.

I did both things, but Studio still detects errors in exact matches and even locked segments. Strangely enough, it didn't find the same mistakes it found before I closed and re-opened the project to try your suggestions. Sometimes I find that Studio 2022 has an inconsistent behaviour.

Also, it keeps pointing out missing numbers that are present in the translation.

Thanks,

Pilar

Hi Pilar García-Romeu ,

I know that one because I just changed it a couple of weeks ago!

The symbol of área (as a surface measurement) is the single letter a. Again, Trados takes 81 a as 81 áreas, so it gets a bit confused (81 to in Source is not a unit) and notifies you accordingly…

As I had the very same issue as you, in order to get rid of this error for good, I removed the measurement a from list of Spanish measurements (in general, from the Target language).

If you remove the a measurement here, the next Verify operation will be fine.

I did it for myself and so far so good. Nowadays we don't often measure surfaces using areas, de we?

By the same token, I removed also the capital A (Amperes) from all TMs that won`t ever mention this electrical unit.

Hi Pilar García-Romeu ,

I know that one because I just changed it a couple of weeks ago!

The symbol of área (as a surface measurement) is the single letter a. Again, Trados takes 81 a as 81 áreas, so it gets a bit confused (81 to in Source is not a unit) and notifies you accordingly…

As I had the very same issue as you, in order to get rid of this error for good, I removed the measurement a from list of Spanish measurements (in general, from the Target language).

If you remove the a measurement here, the next Verify operation will be fine.

I did it for myself and so far so good. Nowadays we don't often measure surfaces using areas, de we?

By the same token, I removed also the capital A (Amperes) from all TMs that won`t ever mention this electrical unit.

Hi Jesús,

Thanks for your reply. I have applied this change in my local TM, but I am not allowed to change it in the remote one, so the problem keeps happening. Anyway, the problem I pointed out was with a a "missing number", not an "additional measurement".

It also shows QA errors in excluded segments.

Is there anything I can do regarding these issues?

Thanks again,

Pilar

Hi Jesús,

Thanks for your reply. I wasn't able to do that because I am not allowed to edit the remote TM. Anyway, my problem was with "number not found" rather than with "additional measure". Also, Studio keeps signalling errors in excluded segments.

Any idea how to solve those issues?

Thanks again,

Pilar

Hi Pilar García-Romeu ,

Pilar García-Romeu said:

Anyway, my problem was with "number not found" rather than with "additional measure".

I get these 2 errors after Verify step:

Both the the 1st and 2nd error highlight the string 81 a in this segment:

After removing measurement a as mentioned above, I've tested that both errors are gone.

I hope other colleague can help you with the Exclude issue. If you could post an XLIFF with the issue, I'd be able to help.

Hi Jesús,

Thanks again for your reply. It looks like whenever I make a change in a project settings, I need to save and close it. Then it will respect the settings chosen. It still detects errors in excluded segments, but just spaces before and after tags, which I pay no attention to. I haven't been able to create a project that allows me to re-create the issue and I cannot send a real one because of confidentiality issues. As for the measurements and numbers issue, I will try your suggestion in my next project and will let you know.

Thanks once again for your interest.

Pilar