Hi Simon Cole,

The version difference shouldn't cause any real problem.

I think you may find the solution is to turn off Match Repair, here in Project Settings:

Give it a go and see if that solves the problem...

All the best,

Ali

No, it still crashed. But I just completed a small package project in which F8 worked. But this was created by a Studio expert (SDL trainer, beta-tester since the inception of Studio on 2009 - I expect you know Gaetan?), so I am not surprised. There are a lot of agency users out there who don't know the half of what they are doing!

Hi Simon Cole,

Yes, I know Gaetan, I presume you meant Gaetan Chretiennot though I didn't realise he'd been a beta tester as long as I though I should do as we weren't as many in those days.

There could be any number of reasons why this happens, though I've never found it to be due to PMs who don't know...what they are doing. The wonderful agency who I do most of my work for are super, I'm happy to say.

When it happens to me, I run the individual components of the verification separately, by ticking only one of them at a time, here in Project Settings:

Sometimes, if I run one process at a time, I can push the whole verification through successfully. If not, I can at least ascertain which process is causing the failure.

If I really can't achieve the full verification, I deliver the SDLXLIFF file zipped...

Maybe Paul or can impart wisdom on this subject...

All the best,

Ali

(a workaround enthusiast)

Hi Simon Cole,

Yes, I know Gaetan, I presume you meant Gaetan Chretiennot though I didn't realise he'd been a beta tester as long as I though I should do as we weren't as many in those days.

There could be any number of reasons why this happens, though I've never found it to be due to PMs who don't know...what they are doing. The wonderful agency who I do most of my work for are super, I'm happy to say.

When it happens to me, I run the individual components of the verification separately, by ticking only one of them at a time, here in Project Settings:

Sometimes, if I run one process at a time, I can push the whole verification through successfully. If not, I can at least ascertain which process is causing the failure.

If I really can't achieve the full verification, I deliver the SDLXLIFF file zipped...

Maybe Paul or can impart wisdom on this subject...

All the best,

Ali

(a workaround enthusiast)

Hi Alison

You = Genius! I ran the verification steps individually. I was the SDL Number Verifier that caused Studio to crash. Other options worked individually and all together. I uninstalled SDL Number Verifier and all worked fine on another package project that had given problems.

Then I reinstalled SDL Number Verifier version 3.0.2.0 for Studio 20201 from the Welcome Page AppStore. And running F8 crashed Studio again. So for now I am dropping SDL Number Verifier.

Simon

Nice work Alison Field !

Simon Cole said:

Then I reinstalled SDL Number Verifier version 3.0.2.0 for Studio 20201 from the Welcome Page AppStore. And running F8 crashed Studio again. So for now I am dropping SDL Number Verifier.

It would be helpful if it was possible to see the package where this problem arose so we can fix it.  If this isn't possible perhaps anyone else who finds a problem with this could share their finding?

Paul, I am sending you my 'test package' privately. Simon.

Hi Simon Cole

I'm pleased that my suggestion solved the puzzle.

Using the verification tools one at a time is also helpful if one has a big, buggy or old file that might crash because it's too huge or complex, or a big termbase for that matter. 

I'm having no problem with Number Verifier, I'm glad to say 

All the best,

Ali 

Paul Filkin said:

Nice work Alison Field !