Applying for a license
Conditions for license
Involved in Bible translation in an agency that has an agreement with SIL International or United Bible Societies..
Active involvement in a translation project, in any of the roles Paratext recognizes.
Otherwise, it is still possible to get someone a license who doesn't qualify above. They can have a…
no-resource version of Paratext
To create the no-resource version, the person approving the registration must put spacenr at the end of the username. They will not have the possibility of installing Scripture resources into their version of Paratext. However, please don't request this to circumvent proper authorization. After all, you are giving them a crippled version of Paratext, and I think we want our translators to have access to the resources if at all possible.
While there is no official “training license”, you can contact your license administrator and a reasonable solution will be worked out for your training need.
Installation and updates
Complete install instructions can be found here, as well as some troubleshooting tips for common install problems:http://paratext.org/download/pt/73
It is important to note that .NET 3.5 is required beginning with Paratext 7.3 normally you will not encounter any issues installing on Windows 7, but windows XP and Windows 8 do not have this installed by default. For XP you need to download and install .NET 3.5 manually, but for Windows eight you have to search for the install package using the Windows update feature. Someone who has Windows 8 can improve these instructions
Essentially, the install process is as follows:
Install .NET 3.5 if necessary
Download and unzip Paratext, and run the Paratext framework installer.
Download and install the latest PUD file
As a Paratext supporter, you should have access to download the latest updated PUD files. After logging in to Paratext, you should be able to find them here: http://paratext.org/download/pt/updates-all
Pressing shift when clicking the help menu allows you to select: Advanced | Release Stage | Beta (warning unstable)
It is suggested that all support personnel receive the beta releases in order to detect and report errors before they become part of the standard release.
To downgrade from Paratext 7.5 to 7.4 you need to run the complete install for 7.4: Setup Paratext Framework, and then running the associated PUD files.
For versions 7.4 down to 7.0, the installer hasn't changed and it is not necessary to run the installer. You can downgrade just by running the pud files for the version you want to downgrade to.
Getting past a failed upgrade
It has happened in the past that an auto update script has prevented Paratext from starting. This would only be the case if you were subscribed to the beta updates channel. To get past the failed update, you will have to download a newer pud file from the website if it exists, which will most likely solve the problem. If a newer one does not exist, then congratulations on being the first one to discover this bug. Report it, and get help.
If Paratext will not start, your first response should be to hold down shift while starting Paratext. Paratext will ask you if you want to reset all of the settings to default, you respond by clicking yes. Now start Paratext again. In more than half the cases, this will solve the problem and get Paratext running again. There may be, however, a project that is causing Paratext to crash. In that case, Paratext will crash again. However, by being able to reset Paratext to a default startup, you can troubleshoot which project or component is causing the crash. You'll need to contact support to resolve the issue.
If Paratext will still not start after using the shift method, you can do a complete uninstall and reinstall of Paratext. When uninstalling Paratext, it will never, never, delete the My Paratext Projects directory. (: Please say that again…)
My Paratext Projects directory
From a support standpoint, it is best to leave it in the root of the C drive as in the default install. People who are knowledgeable about the file system often like to move it elsewhere, but in this case I often see multiple MPP directories on computers. If you keep it in the root of C the chances of multiple directories or of Paratext getting confused are greatly reduced.
Moving the My Paratext Projects directory
To change the location of your My Paratext Projects folder.
Paratext 7.3 and later versions will automatically prompt you for the new location when a project that it expects to find is missing. When you give it the new path, it automatically adjusts all of the configuration files to reflect the new location.
So, if you come across a My Paratext Projects directory in an inappropriate location, the best way to move it is as follows
Copy the My Paratext Projects folder and paste it in the appropriate location.
Rename the original folder “Wrong Paratext folder” or something so that Paratext won't recognize it on startup.
Paratext will detect that the folder is missing and will prompt you for the location.
Browse to the correct location and Paratext will fix all of the incorrect links, and start up normally
When you confirm that everything is there, delete the renamed folder.
The best way to install Paratext resources are to keep them all available on a thumb drive. Prepare the thumb drive as follows:
The long way
Download all of the resources from the Paratext website.
Insert the thumbdrive
Run each file and select the thumbdrive for the extraction location
The faster way (requires 7-zip)
Download all of the resources from the Paratext website
Insert the thumbdrive
Create a directory on the thumbdrive called stdtexts
Place all of the downloaded exe files in it
Open file explorer
Select all the exe files, right click and select 7-zip from the context menu
Select Extract here
When 7-zip complains about duplicate files, tell it to skip them all.
Install Resources in Paratext
File | Install resources
Browse to the thumbdrive
Press Ctrl + Click to select multiple resources
Set destination as the My Paratext Projects directory
Send and Receive
When entering the name of someone, it has to be entered exactly, including upper and lowercase. For example John Chavez. If “john chavez” was entered, you do a send and receive, the directory with the wrong case will be created on the thumb drive for the data. When John tries to do a send and receive, his computer will say that there is no project for him on the thumb drive. Going back to the administrators machine, if you correct it to John Chavez, the problem still isn't fixed. Windows doesn't distinguish between upper and lowercase in directory names, and so instead of creating a directory “John Chavez”, it will see that “john chavez” already exists and considered to be the same. This is probably a bug, but to get around it to currently, you will have to manually delete “john chavez” directory off of the thumb drive and then do send and receive again from the administrators computer.
To read help topics in Paratext that are designated for technicians like yourselves, type #tech in the search box.
Please take the time to report bugs when you encounter them. When an error report can’t be sent automatically, please take the time to attach the file that is placed on the desktop into an e-mail and send it to the support address.
Reading your own bug reports
When a bug report is sent in, it goes to someone who tries to interpret it and get back to you with a suggestion. The last time I had an issue it was related to a Windows font that was installed incorrectly or missing. If you want to attempt to decipher a bug report to see if it is something simple that is causing the problem, look here:
Inside the bug report zip file you will find a file called “log.txt” that contains the messages from Paratext. Usually you have to go to the bottom of the file and move up, because it can cover several days or weeks’ worth of activity.
In the Send and Receive data, each project that is synchronized with the thumb drive or server has a separate directory for each username.