Hi Torkjell Hareide

Please check if you have the termbase enabled in Project settings, here:

And have you ticked the box here:

Ticking the boxes after the event you'll have to re-verify.

If you're working using 'Translate single document' and you want the same termbase to be used each time, using the same settings as above under File>Options will enable this in future single document translations.

Hope this is enough info to help you...

All the best,

Alison

PS: If you're working via 'Project > New project' from the start, you can select the above before or after you create the project. Using 'Translate single document' adops the settings under File>Options but you can change the settings in the automatically created project after creation.

Hi Torkjell Hareide

Please check if you have the termbase enabled in Project settings, here:

And have you ticked the box here:

Ticking the boxes after the event you'll have to re-verify.

If you're working using 'Translate single document' and you want the same termbase to be used each time, using the same settings as above under File>Options will enable this in future single document translations.

Hope this is enough info to help you...

All the best,

Alison

PS: If you're working via 'Project > New project' from the start, you can select the above before or after you create the project. Using 'Translate single document' adops the settings under File>Options but you can change the settings in the automatically created project after creation.

Hi Torkjell Hareide

A few facts...

A termbase is a list of source words with preferred target translations, a type of bilingual glossary. Each entry can have explanations/notes/images and other resources added.

I must have given you a wrong impression. A termbase is not required in any version of Studio for F8 to work. It is only required if you wish to use Terminology Verifier itself to check that translated terms match a list that the client provides or that you compile as you work.

If you've never used a termbase, then you will only have been verifying with QA Checker which verifies a list of things. You will have made this work by ticking the correct boxes. You may also have been verifying with Tag Verifier, the second verification tool that is part of SDL Trados Studio.

Take a look here to see a description of the 3 types of verification that were available as standard with both Studio 2015 and 2017:

Verification

Now, here's an explanation of verification in 2019:

Verifying translations

You'll see a Search box at the top right of the page and you can also click the SDL Trados Studio link top left and look through the index to the whole of Studio 2019 Help manual. There's also a searchable MultiTerm Help manual site.

Happy reading! Feel free to come back and ask further questions on the Community

All the best

Ali

Hi again Torkjell Hareide

It may be that you use a different target language number localisation than that which is programmed into Studio for your specific target language.

However, many do report that QA Checker's number verification isn't accurate.

Personally I don't use that part of QA Checker, i.e. I have all the number options unchecked here:

this is because I prefer to use the Number Verifier plug-in. I do this using the following settings, customised for my target language:

That works pretty well for me.

You can download the Number Verifier plug-in from the SDL AppStore, here:

Number Verifier

You have to sign in to download it. Unzip if necessary and run it to install. Then you can select it in the Verification section of your Project settings (or via File>Options if you use Translate Single File rather than Create Project. Then you can select the settings that work best for your target language.

It isn't perfect but it's pretty good! It also verifies alphanumerics (letter and number combinations) which is pretty useful (that is where I find it isn't perfect because it will include full stops or other punctuation in alphanumeric verifications). On the whole though, it's better than the QA Checker's number verifier.

I keep QA Checker ticked for verification though as it has a lot of other very useful functionality which can be customised to search for all kinds of things.

All the best,

Ali

Hi Torkjell,

I reported this problem for Austrian->English long ago, and apparently Studio date recognition does not work for Austrian.

Probably the same problem for Norwegian (based on the image you included, that appears to be the language you are working with).

But don't hold your breath waiting for a fix.

It has been so long since I reported the problem for Austrian that I have no idea anymore whether it was one year, two years or more. SDL probably classifies these as "cosmetic" bugs, and I doubt they will ever make their way to the top of SDL's bug list.

I believe Paul recommended at the time that I use anyTM as a workaround, but I quickly ran into problems taking that approach, so I have just accepted it as another problem I have to put up with when using Studio.

Best regards,
Bruce Campbell
ASAP Language Services

Hi Bruce Campbell

Have you tried using Number Verifier?

All the best

Ali