Frequently Asked Questions
A comprehensive list of changes since Paratext 7.5 can be found in the following post: What’s new in Paratext 8?
Go to http://registry.paratext.org and log in with an email address, preferably a Google account from your organization. If you are an existing Paratext 7 user, you can often be approved immediately when you submit your Paratext 7 code. Users who are part of a Bible translation organization will have access to more resources and features. See the Registration section of this site for more details.
The Paratext Registry will let you sign in with any valid email address, but if you then request a registration code as a member of a translation organisation, your organisation’s approver may expect you to be using your organisational email address, as this makes it easier to confirm your identity. It will also typically keep you from having to create and remember a password: if your organisation’s email is on Google Apps, you will see a “G” icon next to your email address and can simply sign in via Google.
If you are not a member of a translation organisation, you can use any email address. If it is not a Google/Gmail address, you will be prompted to create a password.
Paratext 7 users: You do NOT need to use the same email address that you registered with in Paratext 7. Once you are signed in, just provide your existing Registration Name and Registration Code, and your existing identity will be linked to your new Paratext 8 registration.
See also: How to register as a Paratext 8 user.
When you create a New Project from the File menu in Paratext, you are given the option to register the project online. Project registration is only available to users who have been vetted by a Bible translation organization. Registered projects have additional features that are not available in the basic tier projects as explained on the Registration page of this site.
When registering a project, Paratext requires an active Internet connection. It forwards you to a browser and you must sign in with the account you registered for Paratext with. Once the registration entry is complete, Paratext links the Paratext project with the entry in the registry.
No. You can create an unregistered project with the functionality that is available on the Basic Tier of use. See the Registration page for details.
You can change your mind later and register the project to gain full functionality.
Paratext version numbering is as follows – 8.0.x.y
If x is between 1 and 49, it is an alpha. Alpha versions are for early adopters only and are usually not fully featured or fully functional. They should not be used with live project data.
If x is Between 50 and 99 it is a beta. Beta versions are more functional, more feature-complete and stable than an alpha and may be appropriate to use with live projects. Sometimes a beta is offered as a “release candidate” to indicate it is a relatively stable beta version. Release candidates are the final beta versions before stable release versions.
If x is 100 or over, it is a full stable release. For example, 18.104.22.168 or greater.
Yes, Paratext 7 may continue to be used after installing version 8. However, the data will not be shared between versions 7 and 8; Paratext 8 can not collaborate with Paratext 7 and vice versa. Users must migrate their data from 7 to 8 using the migrate feature in Paratext 8.
Yes and No. Although Paratext 8 Scripture files are stored on your hard drive in the same USFM format as in Paratext 7.x, there are a number of different types of data that are also synchronized between users. This requires the use of a new Send/Receive server. Paratext 7 projects must go through a one way migration to Paratext 8 and are stored in a new My Paratext 8 Projects folder. After the migration, data can only be shared between them by exporting and importing books manually between the two programs.
Paratext 8 can run on any computer that boots Windows Vista or later. Windows XP is no longer supported. If you have 1 GB of main memory or less it may be better to not run other programs at the same time as Paratext.
No. Due to the changes in the new version, data can’t be shared back to Paratext 7.x via Send/Receive. This is the reason for a new Paratext 8 data directory and send/receive server. As a team, you must coordinate the migration of your data to Paratext 8 together. You can run Paratext 7 alongside of Paratext 8 as needed to access projects that have not yet been migrated. Paratext 8 will only be able to open Paratext 7 projects after completing the migration process. At that point it is advised to remove the project from Paratext 7 to prevent users from accidentally editing the data in 7.
When you work in Paratext 8, it will list the Paratext 7 projects on your computer in the Open Project/Resource… dialog, and also in the Send/Receive Projects… dialog. When an administrator opens them in this way, the two step Migration process is initiated.
- Online project registration via the Paratext Registry
- Migration of the data
It is not necessary to do both steps at once. The migration can be completed at a later time, when the team is ready.
Data migration should only be performed after the entire team does a Send/Receive and the administrator has the latest version of the data. After the migration, changes to the Paratext 7 data can’t be synchronized with 8, and the team must stop editing that project in Paratext 7.
More detailed information is available on the Migration Help page.
No. You can download and install Paratext 8 at any time, but you must register in order to use it. Registration is free to everyone.
Resources can be downloaded from the Internet directly in Paratext 8. You do not have to download and install them one at a time. Resources are downloaded from DBL and saved on your computer. These files can then be put into a network shared folder so other people can install and use them.
The resources available to you will vary based on the organization you work for. In previous versions of Paratext, a user either had access to all the resources or none of the resources, based on their license. In Paratext 8, resources are available based on the agreements a user’s organization has with the copyright holders of the content in the Digital Bible Library. There are currently 1,266 versions in the Digital Bible Library, although not all of them will be licensed for distribution in Paratext. Any DBL resource that is licensed for distribution in Paratext will be available to be installed in Paratext. Resources that have an open license will be available to all users. Other resources will only be licensed for use by projects with certain organizations.
Here is a list of known issues and incompatibilities which affect Paratext 8.
Paratext 8 is compatible with Publishing Assistant 6 but not with earlier versions of Publishing Assistant. At the time of Paratext 8 release, Publishing Assistant 6 is not yet available, but it will follow very shortly. Paratext 8 projects are stored in a different folder to Paratext 7 projects, and some of the files are a different format. Any Paratext 7 projects which are in the process of being typeset should not yet be migrated to Paratext 8.
Yes, anyone can download, install, and use Paratext, but registration is mandatory. For people who are not vetted as having a role in Bible translation there are limitations, explained on the registration page of this site.
In Paratext 8 the downloaded resources are stored in the \My Paratext 8 Projects\_Resources directory as .p8z files. These files may be copied to a flash drive and installed on other computers by using the Install Resources command and navigating to that directory.
Note that the copied resources will only be accessible if the receiving user has a registration that permits access.
You need to contact the Paratext Board of Governors to be considered as an independent translator, explaining the nature of your project. You may use this form.
A representative of your organization needs to send a request to the Paratext Board of Governors as described on the Registration page.
While an individual may upgrade to Paratext 8 to become familiar with its features, the team project should not be migrated until the team is ready. It is possible for the administrator to do a test migration of the data, but then the project must be deleted from Paratext 8 and remigrated when the team is ready to switch.
We know that scheduling a time to migrate can be very difficult in places where teams are spread out in remote locations. To help, we have a working document on Deployment Strategy that talks about various team scenarios and how best to handle migration of their data.
Paratext 7 and 8 may be installed simultaneously on the same computer but not for sharing the same project. If you are a consultant or administrator who works with more than one project, you may need to continue to use Paratext 7 with certain teams until they are able to migrate to 8. It is important not to confuse the two versions of Paratext! Once a project’s data has been migrated to 8, any notes you write in 7 won’t be seen in 8. Likewise, if the team has shared the project with you in 8, be sure they have removed their project from 7. If they reverted back to 7, you won’t be getting their updates in 8.
The Paratext 7 Send/Receive server will continue to work for a period of time after the release of 8, but we won’t have the capability to continue to support both platforms for long. We will give you as much time as we can to upgrade to 8, but we recommend that you try to upgrade within nine months of the stable release.
At first glance, there is not much that is different in the main working windows. So if you are comfortable using Paratext 7.5, you should have a smooth transition to 8. A number of the new features are optional to use and you don’t need to dive right in. However we would encourage you to use the help file and to get training for Paratext 8 so that you can work more efficiently. We hope to provide an online training program for Paratext 8. When it is ready, it will be available on the Help page.
No. There is just one edition which can be used by all users. It is available as either an Online or Offline installer.
If you have not been vetted as either a member of an approved organization or as an independent translator, you will not be able to register a projects. Please log into the Paratext Registry and select the organization you are part of on your profile page; once you are approved you will be able to register projects under your organisation.
If you need to request that your organisation be added to the Paratext Registry, you should follow the instructions in the “Organisation Registration” section found on the Registration page.
Yes. Paratext itself is the tool used to upload texts to the Digital Bible Library. Someone in your organization should be able to help you submit your text to the DBL. From there, the owners of the text can choose how widely to make it available: for specific organizations, for all vetted Paratext users, or for every Paratext user.
Unless your project is marked as confidential, certain information from your ParaTExt project will be visible to members of the Forum of Bible Agencies International. This includes:
- language and dialect
- scope of project (OT, NT, portions)
- translation type (new, revision)
- current status (active, completed, published)
- current level of progress (expressed as a percentage of the scope)
- rights holder
- any comments you additionally provide.
Paratext began as a tool to help Bible translators do exegesis of the original Greek and Hebrew texts. It was expanded into a translation environment and became the tool of choice for the United Bible Societies. SIL, on the other hand, had started developing a similar product, but one that would integrate with the lexical data that a translation team would collect as part of their foundational linguistic research in a language group. Their product was called FieldWorks Translation Editor, affectionately know as “T-E”. As UBS’ Paratext gained popularity, the two organizations found themselves in competition with each other. In 2010, administrators and developers from the two organizations got together and made the challenging decision to combine development efforts into a single product. Because Paratext had the biggest user base, it seemed the best way forward was to merge critical features from Translation Editor into Paratext, thus creating ParaTExt. We keep the TE in the logo as a tribute to collaboration that helped improve the Paratext we all use today.