Translations are automatic. Report a translation problem.
Applying a Project Plan to an existing project is one of the biggest frustrations for teams that are starting to use the Project Plan to manage assignments and keep track of their progress. You may have a dozen books that are already consultant checked and some that have already been printed. Yet, when you or your administrator applies a new plan to your project, you find that you are unable to mark tasks as done for work that is already completed. The Stages Table provides a simple grid (below) that is supposed to make this easy, but as you will soon see, it doesn’t work as expected.
With a single click, the administrator can check off all the tasks in a stage as being complete. Let’s suppose that Genesis has already been consultant checked and printed. We want to mark all six stages as having been completed. We start by marking Drafting as complete:
Now all the tasks in the drafting stage have been marked as complete for the book of Genesis. …
We are pleased to announce that Paratext 9 is now available as a beta version. Paratext 9 will help translators work more efficiently, creating better layouts, and providing easier access to reference materials through Enhanced Resources. It has already gone through a lot of testing and users have been very happy with it. You may encounter some minor problems that we aren’t aware of yet, so there will continue to be some minor changes over the next couple months as we work towards the official release. However, we are confident that it is stable enough for everyday use.
Yes, if you:
A recent update has added a new normalization setting.
We are recommending that users review this setting and determine if a change should be made for their projects.
The majority of projects migrated from Paratext 7 will have normalization set to “Off”. This might not be the best setting for your project. The rest of this article describes in very brief form what Unicode normalization is, and the meaning of the three available settings for it. It will be up to you to determine what the best setting for your project.
Unicode normalization is the process of establishing the rules for how characters that can be represented in more than one way under the Unicode standard should be represented in a given project. Lack of consistency in how these characters are represent in a Paratext project leads to problems with searches and filters not working as expected, and can cause poor looking publications. …
Have you ever discovered quoted text in a footnote, but can’t find that text in the verse? This happens when the verse text is updated and the footnote is no longer relevant. Have you ever struggled to verify the references cited in a footnote, or had trouble keeping book abbreviations consistent? This article will show you how to make your footnotes in a way that Paratext can help you check them for problems like these.
Any time you quote words from the translated text in your footnote, you should mark them with the quoted text marker “fq”. This will let Paratext know that the word or phrase is a quotation and the quoted text check will alert you when the verse and footnote no longer match. During the life of a project, it is very common to change the renderings of biblical terms of modify the spellings, causing footnotes to be out of date. …
The Paratext website is an obvious place to list training events for people to learn Paratext or improve their skills. To facilitate this, we have launched an events section on the website where Paratext training events will be listed, starting with a Paratext Training Course in Dallas, Texas, December 3-10. Since there are so many organizations using Paratext, we can’t know about all of the training events going on around the world. So we are including a link on our events page for training event submissions. If your organization is hosting a training event and is able to make it open to others, we would encourage you to list it here.
If you have a larger group that needs training, please write to help@paratext.org and we will see if there is a trainer who is available to travel to your area. Our goal is for every Paratext user to be working effectively with the software. …
Now that we have been doing migrations of Paratext data for quite some time, we have put together a list of things that should be considered at the time of migration. This is great news if you are at the point of migrating your Paratext 7 project to Paratext 8. But don’t worry, even if you have already completed the migration, we’ve provided instructions for you too. It isn’t too late, but you might have some extra steps involved. Please read through the list below, and follow these topics to the website for more information if you should deal with any of these issues. …
Applying a Project Plan to an existing project is one of the biggest frustrations for teams that are starting to use the Project Plan to manage assignments and keep track of their progress. You may have a dozen books that are already consultant checked and some that have already been printed. Yet, when you or your administrator applies a new plan to your project, you find that you are unable to mark tasks as done for work that is already completed. The Stages Table provides a simple grid (below) that is supposed to make this easy, but as you will soon see, it doesn’t work as expected.
With a single click, the administrator can check off all the tasks in a stage as being complete. Let’s suppose that Genesis has already been consultant checked and printed. We want to mark all six stages as having been completed. We start by marking Drafting as complete:
Now all the tasks in the drafting stage have been marked as complete for the book of Genesis. …
We are pleased to announce that Paratext 9 is now available as a beta version. Paratext 9 will help translators work more efficiently, creating better layouts, and providing easier access to reference materials through Enhanced Resources. It has already gone through a lot of testing and users have been very happy with it. You may encounter some minor problems that we aren’t aware of yet, so there will continue to be some minor changes over the next couple months as we work towards the official release. However, we are confident that it is stable enough for everyday use.
Yes, if you:
A recent update has added a new normalization setting.
We are recommending that users review this setting and determine if a change should be made for their projects.
The majority of projects migrated from Paratext 7 will have normalization set to “Off”. This might not be the best setting for your project. The rest of this article describes in very brief form what Unicode normalization is, and the meaning of the three available settings for it. It will be up to you to determine what the best setting for your project.
Unicode normalization is the process of establishing the rules for how characters that can be represented in more than one way under the Unicode standard should be represented in a given project. Lack of consistency in how these characters are represent in a Paratext project leads to problems with searches and filters not working as expected, and can cause poor looking publications. …
Have you ever discovered quoted text in a footnote, but can’t find that text in the verse? This happens when the verse text is updated and the footnote is no longer relevant. Have you ever struggled to verify the references cited in a footnote, or had trouble keeping book abbreviations consistent? This article will show you how to make your footnotes in a way that Paratext can help you check them for problems like these.
Any time you quote words from the translated text in your footnote, you should mark them with the quoted text marker “fq”. This will let Paratext know that the word or phrase is a quotation and the quoted text check will alert you when the verse and footnote no longer match. During the life of a project, it is very common to change the renderings of biblical terms of modify the spellings, causing footnotes to be out of date. …
The Paratext website is an obvious place to list training events for people to learn Paratext or improve their skills. To facilitate this, we have launched an events section on the website where Paratext training events will be listed, starting with a Paratext Training Course in Dallas, Texas, December 3-10. Since there are so many organizations using Paratext, we can’t know about all of the training events going on around the world. So we are including a link on our events page for training event submissions. If your organization is hosting a training event and is able to make it open to others, we would encourage you to list it here.
If you have a larger group that needs training, please write to help@paratext.org and we will see if there is a trainer who is available to travel to your area. Our goal is for every Paratext user to be working effectively with the software. …
Now that we have been doing migrations of Paratext data for quite some time, we have put together a list of things that should be considered at the time of migration. This is great news if you are at the point of migrating your Paratext 7 project to Paratext 8. But don’t worry, even if you have already completed the migration, we’ve provided instructions for you too. It isn’t too late, but you might have some extra steps involved. Please read through the list below, and follow these topics to the website for more information if you should deal with any of these issues. …