Paratext 7 has an option "View > By Chapter". If this is checked Paratext does all its editing one chapter at a time. This is much much faster especially for a big book like Psalms. If it is unchecked Paratext tries to handle the whole book at once. If you notice editing has become very slow, check this menu item. Normally if you are only viewing a book and not editing this may not be too big of a problem.
[You can skip all the rest if you are not interested in knowing why Paratext 7 is worse about this than Paratext 6]
Paratext 7 attempts to be polite. Polite programs, like polite people, remember your preferences and don't keep asking you over and over again how you would like something done. How is this dangerous?
Imagine that I had strong feelings about coffee and was easily shocked. Supposed I asked you how you would like your coffee and you said "Frozen solid.". Immediately I go into shock, faint, and fall on the floor. The next time you walk up to me and say "I would like some coffee." and I fall on the floor again. How did this happen? As a polite person I remember your preference for frozen coffee. As soon as you ask for coffee I assume you want it the same way and the shock of it all causes me to faint yet again.
There is a problem with Paratext 7 on some machines (3 that I know of) that occasionally causes the following:
When you are editing a paragraph the last verse of the paragraph is erased leaving only the verse number.
We have not been able to determine why this happens on some machines and not others or what triggers the problem. The problem is actually in some Microsoft supplied code, but Clayton has found a way to circumvent this code.
You can do the following:
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 ...
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:
- How did anyone ever develop such a masterful story telling ability?
- Is there a deeper level of meaning to this story known only to the enlightened ones?
- 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.
- 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.
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.
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?
If Paratext 6.1 crashes on startup after Paratext 7 is installed
- Go to http://paratext.org
- Enter your Paratext website user Id and password.
- Click on Downloads > Paratext button at top of screen.
- Click on Service Pack 1f Update and download the file. Unzip the file on your system and then double click on the PT6.1.106-Update.PUD file to install it.
Here are few important items to know when making the transition to Paratext 7:
- If Paratext 7 is very slow when you edit in a window or go to a new book: Check the menu item View > By Chapter. If this is not checked all editing or going to a new book will be quite slow since we have to update the display of the entire book instead of just a single chapter. Click the menu item to switch to viewing/editing a single chapter at a time.