Hi Valentina De Cosmis

Are you talking about Studio 2017 or 2019?

You say "Studio does not detect errors in the source" - do you mean in the target? Studio doesn't check the source text.

If verify is taking too long, do you have Studio and MultiTerm added to your AntiVirus exceptions lists?

I have not heard of an 'original file before conversion' error - The closest thing I can guess is that you verified the source SDLXLIFF rather than the target. This would happen if you had the Source language selected on the left hand pane rather than the Target language, which would bring the source file/s into view instead of the target file/s and then the batch task would attempt to run on the source sdlxliff file instead of the target sdlxliff file. 

OR you might have attempted to verify a reference file, which would then have been a single language file, PDF or Word for example, which would also have triggered an error message.

Now we come to F8. This function key triggers only the verifications that have been set up here:

F8 will only trigger the verification for which the boxes have been ticked, along with everything as selected in the corresponding dropdowns such as here:

As you'll see I don't have number checks ticked, because I have the Number Verifier plug-in added and select what I want checked numerically and alphanumerically there. This will also be triggered by F8.

You have the grammar checker added I presume as you need this to check grammar.

Do you work with packages from a client? If so, it is likely that they have not selected the correct settings for verification in the above sections of their project settings. You can select these yourself. You can also select the termbase you wish to verify terminology with, here:

Then of course you need to select the correct options here:

Feel free to ask further questions if the above does not help your situation.

All the best

Alison

Hi Valentina De Cosmis

Are you talking about Studio 2017 or 2019?

You say "Studio does not detect errors in the source" - do you mean in the target? Studio doesn't check the source text.

If verify is taking too long, do you have Studio and MultiTerm added to your AntiVirus exceptions lists?

I have not heard of an 'original file before conversion' error - The closest thing I can guess is that you verified the source SDLXLIFF rather than the target. This would happen if you had the Source language selected on the left hand pane rather than the Target language, which would bring the source file/s into view instead of the target file/s and then the batch task would attempt to run on the source sdlxliff file instead of the target sdlxliff file. 

OR you might have attempted to verify a reference file, which would then have been a single language file, PDF or Word for example, which would also have triggered an error message.

Now we come to F8. This function key triggers only the verifications that have been set up here:

F8 will only trigger the verification for which the boxes have been ticked, along with everything as selected in the corresponding dropdowns such as here:

As you'll see I don't have number checks ticked, because I have the Number Verifier plug-in added and select what I want checked numerically and alphanumerically there. This will also be triggered by F8.

You have the grammar checker added I presume as you need this to check grammar.

Do you work with packages from a client? If so, it is likely that they have not selected the correct settings for verification in the above sections of their project settings. You can select these yourself. You can also select the termbase you wish to verify terminology with, here:

Then of course you need to select the correct options here:

Feel free to ask further questions if the above does not help your situation.

All the best

Alison