Caution about Paratext 7 Send/Receive


The new Paratext 7 Send/Receive functionality can be used on a single machine to keep a project history of the files on that machine and to make an offsite backup of that history on the Internet server. There appear to be relatively few problems with this usage. When used in this way files must be moved between machines using Backup/Restore as in previous versions of Paratext.

There is a more complex multi-machine way to use Send/Receive to share files across machines ...

A Wonderous Tale (Fixing Up A Laundry Mess)

At our house when the laundry has been washed and dried it is supposed to be neatly folded and placed in a basket so the next person knows it is clean. Sometimes someone (who shall remain nameless) gets in a hurry and just piles the clean laundry unfolded in a basket. Someone else comes along and places a basket of dirty laundry next to the basket of clean laundry. Once we start moving these baskets around a sad tale of woe and gloom begins with no one being quite sure what baskets contain dirty laundry and what baskets contain clean laundry.

At this point you are probably wondering two things:

  1. How did anyone ever develop such a masterful story telling ability?
  2. Is there a deeper level of meaning to this story known only to the enlightened ones?

Two Warnings About Send/Receive


  1. When anyone on a project deletes a book Paratext 7 remembers that change. When you do a Send/Receive that change is sent to everyone else on the project and the book is deleted from their copy of the project also. I am planning to add a warning to this effect to the Project/Delete Books command. There will still be many copies of the book in the project history and the latest one can be recovered by following the instructions in the first "sheep" message.
  2. If you give your Paratext user Id to someone else (perhaps for a short time while they are waiting for their own Id) any changes they make to books or books they delete will be sent to your copy of the project on the Internet server. When you next do a Send/Receive all those changes will appear on your system and it will look as if you made them yourself. This can be dangerous and very confusing.



Keeping all the Sheep

When I wrote a couple days ago we still had not figured out exactly what went wrong. I think we know more about this now. It is a matter of keeping all your sheep

Keeping all the Sheep the Old Way

Traditionally when a project had multiple computers we would  assign editing a given book to just one computer at a time, e.g.: Joe will edit GEN on his computer but we will tell Bob not to make any GEN changes on Bob’s computer for now. After a while we use File/Backup on Joe’s computer, do a File/Restore on Bob’s computer. Now Bob can edit GEN and we have to tell Joe not to make any more changes for now.

The old way works pretty well as long as Bob remembers to hold off and not make any changes on his machine until he gets the backup from Joe. If Bob forgets, all Bob’s changes will be lost (without any notification that they have been lost!) as soon as Bob restores the backup file from Joe.

Lost Sheep

I have a lot of ground to cover here but I think it will be valuable to most Paratext 7 users to read this carefully. Let me start with something I saw a long time ago (altho I don't recall the markup exactly):

\q1 Little Bo Peep has lost her sheep
\q2 And doesn't know where to find them.

If you have been involved with Bible Translation for more than a few weeks you have probably at one time or another experienced some of your text going lost just like Ms. Peep's sheep. Text may go missing due to hardware failure, insufficiently omniscient programmer error, or even "I can't believe I just did that" error. What to do?

Syndicate content