Apparent disconnect between Wasta dictionary and Windows dictionary

Question

I have a project that is on the latest versions of Paratext on Windows and on Wasta. The original project was set up on Windows. Two of the Wasta computers are also Flex. For the Wasta machines making a change or addition to the dictionary seems to sync across Wasta machines, but the change doesn’t show up on the Windows Paratext and doesn’t show up in Flex anywhere. Searching for a word that is in the lexical project draws a blank if it hasn’t been added in the Wasta version of Paratext.

On the Wasta machines, going into Project Properties and Settings and choosing Associations shows the right lexical project and Choose is grayed out, so there doesn’t seem to be a way to check whether Paratext is recognizing the lexical projects or not.

Multiple send receives on both programs and all computers hasn’t changed anything. Am I missing something?

Answer 1

I have no more insights. It’s probably best to create a problem report (Help > Report a problem) so we can look into it.

Comments

Thanks for taking time to look at this. I am sending two reports with the same title. One from the windows machine and one from Wasta. They are both on the same Paratext administrator account. I hope that proves helpful.

anon349755

Answer 2

If a change to the FLEx data is not syncing, that’s likely a FLEx problem and not a Paratext problem. FLEx and Paratext do not share the same synchronization system (i.e. a S/R in one program does not do a S/R in the other program).

Comments

Thanks, I thought it might be a FLEx problem, but FLEx is consistent across all machines. So, I thought I’d start with Paratext.

Paratext changes done on the Windows machine show up across the board in FLEx, and FLEx changes done on any machine will show up in Paratext on the Windows machine. Whether made in FLEx or in Paratext (on the Windows machine), those changes aren’t showing up in Paratext on the Wasta machines, but changes made in Paratext on the Wasta machines show up on the other Wasta machines after a send/receive.

It may be obvious, but I think I ought to mention that both the language data and the translation data are syncing with Language Depot.

If you think it would be better, I can post to the FLEx site and see what they say.

Answer 3

I thought I’d try re-framing the problem.

I have miss-spelled glosses in Paratext on our team’s Wasta machines. I miss typed a couple of glosses while working on my laptop, during a power outage. The miss-typed glosses show up in the Paratext dictionary across the Wasta machines but not in Paratext in Windows 10.

Our team is using one Windows machine which is isolated from the Paratext dictionaries of the rest of the team for some reason, but it is the only dictionary that communicates with Flex.

We’re beginning to have a fair amount of work in the Paratext project dictionary on the Wasta machines, both good and incorrect info. The good info we can’t access or augment. The bad info we can neither correct nor delete. Not all of it agrees with the Paratext dictionary on Windows machine but there’s no way to know how bad of shape we’re in until we can access the info.

There are no warning symbols showing in the Project Properties and Settings menu, and there is no reason to believe that Send/Receive is having any difficulties. Everything seems to be working as intended except for the Paratext project dictionaries.

Any insight would be appreciated.

Answer 4

What are the versions of Paratext used in each of the machines?

Comments

They are all Paratext 8. The Windows machine has [Phone Removed], and the Wasta machines are all using 8.0.0.10292.