David Earnshaw We will be pleased to help you with this problem so have logged a support case on your behalf. We do prioritise customers who have a support contract so please keep in mind it could take up to 48 hours, especially over a weekend, but rest assured we will contact you as soon as we can. You will be contacted at the email address used for this Community. Support Case Id : 00828181 .

HI,

What do I have to do to get support? It has been a week now...

Best

David

Hi David Earnshaw 

An RWS engineer wrote to you on the support case I logged on 05/12/2023 16:08 and 07/12/2023 16:44, CET proposing a remote session to resolve the issue. 

Please check the email address (Inbox / Spam folder) used for this forum an reply on the support case to get further assistance. If you use another email address let me know 

Thank you,

Sorin

Hi,

Thanks for the reply. There is nothing in the Spam folder or in the inbox. I receive notifications about posts normally.

Perhaps they could try this address: david@earnshaw-translations.de

Would be happy to do a remote session..

Best

David

Hi David Earnshaw 

I added the second email address to the support case, the RWS engineer will most probably contact you on Monday.

As a suggestion, if the path contains double slash or backslash that is causing the issue. Try to copy the termbases on a locations without double slash or backslash and see if it works. 

Thank you,

Sorin

OK, I will take a look.

Thanks

Hi,

It indeed seems to have something to do with the double backslash...though that would be a real pain.

Best

David

did you finally get an answer ? apart from the backslash that is hard to resolve since I guess you are working on a mac, just like me...

HI,

It seems there is an issue with an UNC path.

(https://learn.microsoft.com/en-us/dotnet/standard/io/file-path-formats).

I have put my projects now off the MAC share and under OneDrive in Windows, which is the direct C: path and not the MAC double slash.

Studio then finds the termbases again in my case. Perhaps this will help you.

Best

David

HI,

It seems there is an issue with an UNC path.

(https://learn.microsoft.com/en-us/dotnet/standard/io/file-path-formats).

I have put my projects now off the MAC share and under OneDrive in Windows, which is the direct C: path and not the MAC double slash.

Studio then finds the termbases again in my case. Perhaps this will help you.

Best

David

David Earnshaw Aurélien BIGOT 

David Earnshaw said:

I have put my projects now off the MAC share and under OneDrive in Windows, which is the direct C: path and not the MAC double slash.

I would strongly recommend you do not do this unless you are certain you have configured OneDrive to always keep the files on your local drive as well as being in the cloud.  If you don't do that the default settings for OneDrive will at some point remove your files to cloud only and just leave a footprint behind. This will put you back into the same problem of files not being found.

Windows also creates a Documents folder that is not OneDrive\Documents.  I suggest you use that one.

Thanks ! I think i'll just wait for a new update that might solve that problem, let's hope it does, I can't afford waisting time right now I'm in the middle of a huge legal translation

Other than that, i'm using a collaborative TB in dropbox, it works fine, I might try to use it with SR2, i'll test that solution

Thanks a lot for you answer !!!

Aurélien BIGOT 

Aurélien BIGOT said:

I think i'll just wait for a new update that might solve that problem, let's hope it does

That is very unlikely.

I found a workaround, I've installed SR2 and as predicted, it disabled my termbases but then I clicked Browse and searched for a different path to the same termbase and found somehow a path in the form of "Z:/Documents..." and it works

I'm not sure how it works but the termbase is activated and the one in dropbox still works too so that's 2 different ways to resolve the problem

Good to hear!

After spending some hours with this issue, too, I have copied my termbases from the Mac side to the PC side in Parallels. Now it works. I can confirm all issues described above and also that locating the termbases on the Mac side (despite the // at the beginning of the path) worked in the past. This is obviously a bug; someone has forgotten about flexible paths and created paths for Windows systems only. I hope this will be fixed SOON.