- Home
-
Training Materials
- Keyboards and Fonts
- Linguistics
- Literacy
- Oral Translation
- Others
- Scripture Use
-
Translation
- Scripture Forge
- Adapt-It
- OmegaT Translation Memory Tool
-
Paratext
- Paratext 9 Materials
- Paratext 8 Course Manuals
- Paratext 7.5 Course and Handbook
- Paratext 7.1 Basic Training
-
Paratext Tutorials
- Basic Editing
- Language Source Tools in Paratext 7.6
- View menu tutorial
- Basic introduction to USFMs
- Tips and Tricks
- Introduction to Using Notes
- Cookbook for Consultants
- Menus vary by active project
- Vérifications
- Help! Paratext has stopped working
- Help, send and receive is not working!
- Bible Modules
- Which Paratext Tool When
- Paratext-FLEx Integration Tutorial
- Back Translations and Interlinearizer
- Send-receive and backing up your data
- ParaTExt 8 Test Projects
- New features in Paratext 8
- Voice Marking Tools
- Animated introduction to Paratext and the stages of a translation project
- Setting up a Paratext Project for Success
- Import TXT or Word DOC Files into Paratext Using SILAS
- Illustrations and Maps
- Advanced Unicode handling
- Create a Custom Python Script in the Paratext Menu
- Create a Custom Scripture Check in the Paratext Menu
-
Translator's Workplace
- Adding BdT Menu to Logos 10
- Adding TW Menu to Logos 10
- Logos Bible Software
-
Translator's Workplace Logos Edition
- Logos 8 Get Started Manual
- Opening Logos
- Opening a Resource
- Navigating a Resource
- Reading Multiple Versions
- Basic Search
- Bible Search
- Looking for Bible Facts
- Using the Home Page
- Using the Passage Guide
- Using the Exegetical Guide
- Using the Bible Word Study Guide
- Using the Sermon Starter Guide
- Using the Topic Guide
- Studying English Words Using the Bible Word Study Guide
- Studying Hebrew and Greek Words Using the Bible Word Study Guide
- Prepare a Bible Lesson Using the Sermon Starter Guide
- Look for Information on a Topic Using the Topic Guide
- Saving Your Workspace or Layout
- Arranging the Windows
- Study a Word Using a Reverse Interlinear
- Study a Word Using a Morphology Search
-
Logos edition
- Logos 8 Get Started Manual
- Set up TW Logos for Success
- Quickstart Guide
- Advanced Tips
- Scrolling with other Translation Programs
- Transition from TWFolio
- Troubleshooting
- External Resources
- Low Bandwidth Installation and Updates
- Turn off Logos internet use when visiting a low bandwidth area
- Logos for Beginners Video-based Training
- Translation Workplace - Folio edition
-
Consultant Training
-
Regional Workshops
- Africa Kenya Workshops(LTCT)
- 2021 Africa Virtual Workshop
- 2020 Africa Nairobi
- 2019 Africa Nairobi
- 2018 Africa Nairobi
- 2017 Africa Nairobi
-
2016 Africa Nairobi
- Course Objectives 2016
- Course Schedule 2016
-
Course Program 2016
- HearThis Session 4
- FLEx 8 Lexicon Edit
- FLEX 8 Using text to build lexicon
- LTCT2016 FLEx - Export
- Scripture App Builder Day 1
- LTCT2016 WeSay New Projct
- Create a new project from a FLEX Lift File
- LTCT2016 Wesay Wordlist
- LTCT2016 WeSay Collaboration
- Scripture App Builder Day 1B
- Scripture App Builder Day 1C
- Scripture App Builder Day1D
- Scripture App Builder Day 2A
- Scripture App Builder Day 2A
- Scripture App Builder Day 2B
- Scripture App Builder Day 2C
- Scripture App Builder Day 2D
- Scripture App Builder Day 3A
- Scripture App Builder Day 3B
- Scripture App Builder Day 3C
- Scripture App Builder Day 3D
- LTCT2016 RegExp
- LTCT2016 Paratext1
- Evening Sessions 2016
- Morning Sharing Time 2016
- Responsibilities 2016
- LTCT 2016 Evaluation
- 2015 Africa Nairobi
- 2014 Africa Nairobi
- 2014 Africa Kara, Togo
- 2013 Africa Nairobi
-
2012 Africa Nairobi
- Course Objectives 2012
- Course Program 2012
- LTCT2012 Friday Jan 20
- LTCT2012 Thursday Jan 19
- LTCT2012 Wednesday Jan 18
- LTCT2012 Tuesday Jan 17
- LTCT2012 Monday jan 16
- LTCT2012 Saturday Jan 14
- LTCT2012 Friday Jan 13
- LTCT2012 Thursday Jan 12
- LTCT2012 Wednesday Jan11
- LTCT2012 Tuesday Jan 10
- LTCT 2012 Monday Jan9
- LTCT2012 Evaluation
- Proactive Software Training
- Teaching a Workshop
-
Paratext for Consultants
- 1 Arranging your workspace
- 2 Consultant notes
- 3 Searching and Dictionaries
- 4 Send and receive
- 5 Taking notes during checking
- 6 Keeping track of Biblical term renderings
- 7 Using the Biblical terms tool
- 8 Seeing history and comparing versions
- 9 Understanding the vernacular text
- 10 Spell checking
- Video lessons
- Paratext Supporters
- Digital Publishing
-
Regional Workshops
- Webinars
- Resources
-
»
- Paratext Supporters
Supporting Paratext
Licensing
Applying for a license
Conditions for license
- Involved in Bible translation in an agency that agrees to FOBAI guidelines for Bible translation.
- Active involvement in a translation project, in any of the roles Paratext recognizes.
If someone is not part of an organization but still wants to use Paratext, they may apply as an Independent translator. Information is available on the registration page at pt8.paratext.org
Training organizations
Training organizations may also apply for using Paratext.
Installation and updates
The installation page has several files which may be useful to you:
- Online installer
- Smaller file which is easier to run and install online. It is a smaller installer because it doesn't contain the files that may already be on the computer system. If it discovers they are needed, it will download them during the installation.
- Offline installer
- Larger file, but it contains all the files that might be needed during the installation.
- Patch file
- Download this also when installing offline because it contains the cumulative updates to Paratext since the release version. Just running the patch file on an existing computer will bring Paratext up to date.
- As a Paratext supporter, you should have access to download the latest updated MSP files (Windows Installer Patch files). The are currently available on the old Paratext site after logging in here: http://paratext.org/download/pt/updates-all
- Checksums
- This file can be used to ensure the install file is not corrupted. You can use this MD5 and SHA Checksum Utility to validate your installer.
Paratext update channel
Pressing shift when clicking the help menu allows you to select: Advanced | Release Stage | Beta (warning unstable)
It is recommended that all support personnel receive the beta releases in order to detect and report errors before they become part of the standard release.
The update channel only works for versions with a stable release. If you are running the beta of a version of Paratext that has not yet been released as stable, you will have to download and install your updates manually from the link above.
Downgrading Paratext
If a patch has rendered Paratext unusable, you can try downloading the previously released MSP file and installing it over top of the current version. If that doesn't work, then uninstall Paratext, reinstall the base version and then install the previous patch. Then uncheck the automatic updates on the Help menu or the bad patch will get reapplied. You will want to report this bug to the developers using the option on the help menu of Paratext.
First Aid
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 when you open the project. 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 8 Projects directory.
My Paratext 8 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 My Paratext Projects 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 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.
- Start Paratext
- 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.
Installing resources offline
To obtain resource files for offline installation, you will need to copy them from a computer that has already downloaded them in Paratext using the File -> Download/Install Resources… menu.You will find the downloaded resources stored in .p8z files that are found in the _Resources directory in \My Paratext 8 Projects. Copy these files to a flash drive. Now you can install them in Paratext on any computer from the Download/Install Resources… menu.
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.
Tech help
To read help topics in Paratext that are designated for technicians like yourselves, type #tech in the search box.
Reporting bugs
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.