The button "approve glosses" does not advance all windows to the next verse

Question

I looked for another thread on this, but was unsuccessful finding any.

Since Paratext 9, I have encountered a problem where hitting “approve glosses” in the interlinearizer causes the interlinearizer to advance 1 verse, but other open windows do not advance with it. It happens about half the time.

My normal workflow is to exegete with my MTTs using Zoom and Paratext Live. Several of my teammates have this same issue on various kinds of Windows computers so I don’t think my particular configuration is an issue here. I also use Logos and have Paratext set to send/follow references.

Is this a known issue or is there a way to fix it?

Answer 1

I would like to also an issue related to interlinear glosses in case it is related. I work with a translator and he is often the one making changes during our checks. Frequently, he will make a change in the text (mother-tongue), click save, but the interlinear window will not refresh, so he cannot gloss the changes he has just made and approve them (for the back translation). The only way he can resolve this is to change verses and then come back to the correct verse so that the Interlinear window will refresh again. This does not happen every time, and I can’t seem to make it happen on my machine, but I’ve watched it happen to the translator on numerous occasions.

Comments

This may be something to submit for feedback to the Paratext team, especially if you can figure out the steps to make it happen on the user’s machine.

---

@james_post . That’s been the problem, it doesn’t seem to occur every time, and we haven’t worked out exactly which circumstances cause it. But I can go ahead and send a problem report, and maybe the circumstances will become more clear later.

Answer 2

If this is intended behavior, it would be helpful to have an option to choose between Paratext 8 behavior and the new behavior.

Answer 3

Yeah, it’s hard to nail down something that doesn’t happen consistently. Maybe you could wait until when it happens, and then send a problem report right away, detailing what was happening at the time. That may give the developers more to go on (and a better window of time to look for clues).

Comments

I have done this right after it happened. I hope a clear cause can be found.