Hayley

I just checked this scenario, at my side it works fine. All the QA settings from the template are correctly migrated to the project created. After the project creation I also changed some settings in Project settings > Verification > QA Checker 3.0, again the settings are applied correctly when translating in Editor.

Note that the settings you define at language-pair level override the global settings. So if you defined the QA settings in both places (under specific language pairs and under global QA settings), you will get the QA results defined under specific language pairs.

For testing I used Studio 2019 CU6.

Hi Adrian,

Well that's rather puzzling.

My project template settings are indeed transferred to the project, so I agree that there's no problem there.

You say that the settings at language-pair level override the global settings. At one point I did define the settings at language-pair level, but then deleted/unticked them all to continue testing. Could they somehow have got "left behind" somewhere and explain why the global settings aren't working?

Hayley

Hayley

Hello Hayley,

It is possible that some setting under the language pair level are causing the issue.

I suggest you to reset the QA settings at specific language pair from the template. If the issue is caused by some reminiscent setting, this should do the trick.

Hayley

Actually you need to reset to default all QA checker sections from template under specific language pairs.

• Punctuation
• Numbers
• Word List
• Regular Expressions

Hi Adrien,

I've just clicked "Reset to Defaults" in each of the four categories under the specific language pair. The effect of doing this is that it copied the global settings for each category into the specific language pair settings. So yes, everything is now flagged correctly in the Editor - thank you!

I will try setting up a brand new project and see if configuring only the global settings works there (which it presumably should do if I don't touch the specific file pair settings).

Hayley