Translations are automatic. Report a translation problem.

By

How soon must I upgrade to Paratext 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.

By

How hard will it be to learn to use Paratext 8?

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.

By

Why doesn’t Paratext allow me to register a project?

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.

By

Can I add additional resources to Paratext?

Yes. To add a text as a Paratext resource, the text must first be uploaded to the Digital Bible Library after passing required checks in Paratext. Once in the DBL, the owner may choose to license it to specific organizations, to all vetted Paratext users, or to every Paratext user.

  • If you are the rightsholder of a text you wish to add, you may work with the DBL curator in your organization to upload the text and make it available.
  • If you wish to request the addition of someone else’s text as a resource, you should contact the rights-holder and refer them to the text resources page to explain how we will use the resource:

By

How does UBS/SIL use the information it has about my translation project?

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
  • country
  • any comments you additionally provide.

By

Why did you capitalize the TE in the Paratext logo?

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. In Paratext 7 the TE in the logo was a tribute to collaboration that helped improve the Paratext we all use today. Since Paratext 8, we no longer capitalize the TE in the logo.

By

Must everyone on the team upgrade from 7 to 8 at the same time?

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.