Hi Hayley

Hayley said:

If I set "mille" = "million" as forbidden in my Termbase, "million" gets flagged up everywhere as forbidden, even in segments where it's perfectly correct

This is a shortcoming of the MultiTerm integration in Studio and there is an idea to change this, which you can support: https://community.sdl.com/ideas/translation-productivity-ideas/i/trados-studio-ideas/studio-behaviour-with-forbidden-terms

Hayley said:

I added "million", "millions", "thousand", "thousands" (and more) to the Word List and set the "Correct form" as "CHECK THIS", but these words are not flagged up by the QA check at all.

No really what the Word List is for. If you want to use a certain spelling of a word in your target language, then you can enter it here. It's not a very powerful feature because it does not support Regex. Useful in some cases though. (E.g. instead of "child friendly" always use "child-friendly".)

The Number Verifier can't do it.

As Jerzy pointed out, the Regex check in QA Check can do what you describe above. It is a very powerful, versatile feature of Studio, but you have to manually enter everything.

What do you do if both "a million" and "a thousand" appear in one French source segment - you will and should get "a million" in the target once...

It would be good to have a tool that knows that "1000" is "one thousand" or "a thousand" etc, but it gets very complex very quickly here... Some people use Xbench for QA, but I don't know whether they check for the meanings of words.

Daniel

Thank you Daniel and Jerzy.

Yes I realise it's not the intended function of the Word List, but it was my best attempt at a workaround thus far...

I'll have a look at the regex check idea, but could you confirm where I should change the settings: Options, All language pairs, or the specific language pair?

Thanks,

Hayley

ALWAYS in your project settings. Never in OPTIONS.
And if you just have one language pair, it does not matter where in Project settings. With several language pairs for each language pair separately.

Can you explain why you say never to use Options?
I would have thought that was the most logical place to configure a setting if you want it to apply to every customer and every job...

Hayley

Can you explain why you say never to use Options?
I would have thought that was the most logical place to configure a setting if you want it to apply to every customer and every job...

Hayley

Options will affect ONLY your future projects, based on the template marked as "default". Any other future project based on other templates and ALL already existing projects will NOT be affected by changes done via Options.
The best way to deal with Studio is creating project based on individual templates. The fact, such settings exist in Options is one of the drawbacks in Studio and results from the option "Translate single document". Would I decide, I would have removed this option years ago, as it leads only to a lot of misunderstandings. Studio is the only tool on the market, where you can use "Translate single document". But what nearly all people simply do not recognize then is the fact, that they ARE creating a special kind of a project, based on the default template...

Hmm ok, that might help. But let me check I've understood you correctly:

A setting that is configured in Options...

• ...will affect a future project that's based on the Default template?
• ...will not affect a future project that's based on one of my Project Templates?

That appears to mean that the Project Settings override the Options IF (and only if) a Project Template is being used. Is that right?

NB. For each new job I always set up a new project. I have Project Templates for a few clients, but often I just use the Default template. I never use Translate Single Document.

Hayley