0 votes
491 vues

In Paratext 8.0, a project created in an earlier version of Paratext must be migrated in Paratext 8.0 in order to use it in Paratext 8.0 (and later).
Some of the new features in Paratext 8.0 (and later) are:

Within a year of the release of Paratext 8.0, the Send/Receive server for Paratext 7.x projects will be shut down and it will no longer be possible to share Paratext 7.x projects via the Internet.

:checkicon: Only project administrators and consultants can migrate a project.

Ancienne publication - affichée dans sa langue d'origine
Paratext par [Expert]
(735 points)

réaffiché | 491 vues

3 Réponses

0 votes
Meilleure réponse

Is this indeed true? This would be a huge problem for projects where translators work in remote locations with only very occasional access to better internet. I hope that “sometime in 2017” is to be taken in a very elastic way.
Our group recently met for the first time in years; this would have been one of the rare opportunities to migrate to Paratext 8, were it not for the fact that PT 8 is not yet stable. The next opportunity may not be for another few years.

Ancienne publication - affichée dans sa langue d'origine
par (517 points)

It’s partially true. The servers will shut down, but management has, last I heard*, said the time would be 8 months to a year after the release of 8.0. This would probably put the deadline in 2018.

*This information is months-old and it might have changed since.

Ancienne publication - affichée dans sa langue d'origine
0 votes

This is news. Not necessarily the good kind… Is this just to “encourage” adoption of PT8?

Ancienne publication - affichée dans sa langue d'origine
par (642 points)

This may have been our plan at one point, but given the late release of Paratext 8, it won’t be until sometime in 2018 that the P7 server gets shut down. The motive, is not to encourage a move, but to reduce the time and effort spent maintaining the two separate servers. You get sufficient time to upgrade, then we shut down the old server.

Ancienne publication - affichée dans sa langue d'origine
0 votes

For what it’s worth, the line in question now reads:
Within a year of the release of Paratext 8.0, the Send/Receive server for Paratext 7.x projects will be shut down and it will no longer be possible to share Paratext 7.x projects via the Internet.

Ancienne publication - affichée dans sa langue d'origine
par [Expert]
(735 points)

I’ve updated the original post with the new wording to reflect what is in the current 8.0 help.

Ancienne publication - affichée dans sa langue d'origine

Updating 8.0 help is good, as far as it goes… (i.e., for those who have already transitioned to PT8). As a 7.5 user, I just happened to stumble upon this catching up on some old posts here (which I know most of my colleagues anon421222’t access). Has this been announced to 7.x users?

In 7.5 Help, searching for ‘migrate’ brings up a single entry: “How do I register for Paratext 8?” At the bottom of the entry, beside a green checkmark, is the following (emphasis added):

Once you have registered for Paratext 8, we recommend that you do both of the following:

  • Migrate existing projects to Paratext. When a main project is migrated, all the projects which depend on the main project (such as auxiliary and back translation projects) will also be migrated. In Paratext 8, see the following topics: How do I migrate a project to Paratext 8? Why migrate?
  • Register existing projects in Paratext 8. Most existing projects will be pre-registered by the translation organization before the user tries to use Paratext 8. For any existing projects that are not pre-registered, see: In Paratext 8, see the following topics: How do I register a project in Paratext 8? Why register?
Ancienne publication - affichée dans sa langue d'origine

As it turns out auxiliary projects including back translation projects do not migrate automatically when the base project is migrated. They must go through the migration process to be sure that the copy being migrated is the most up to date and authoritative copy. You will notice that when a back translation or other auxiliary project is migrated, that the step where you are asked to register the project is skipped since auxiliary projects “inherit” the registration of the base project. One consequence of this worth pointing out is that auxiliary projects do not appear in the Paratext registry.

Note: Back translations and other auxiliary projects must be associated to the base project by assigning the appropriate project type in order for them to not need to be registered. For more information on project types look in Help under :“What different types of projects can I have in Paratext?”

        In Paratext 7.3 (and later), the project type is no longer limited to Standard Translation.
        The General tab of the Project Properties and Settings dialog allows you to choose from the following types  of projects:
  • Standard Translation An ordinary Paratext project that is not derived from another project. If you choose this option, you cannot make a choice from the Based on list.

  • Back Translation A derived project based on a vernacular language translation. The back translation project is a translation of the vernacular to a language of wider communication so a consultant can check the vernacular translation.

  • Daughter Translation A derived project based on a “front” translation. A front translation is a translation in a language that is related to and structurally similar to the language of the derived project. A front translation can serve as the base for more than one derived project.

  • Transliteration (Manual) A derived project for the same language as the base translation, but using a different script.

  • Transliteration (using Encoding Converter) A derived project for the same language as the base translation, but using a different script.

  • Auxiliary A project derived from a base translation. You cannot add or remove users from an Auxiliary project, but you can change Book Permissions and Other Permissions.

Ancienne publication - affichée dans sa langue d'origine

Questions connexes

0 votes
7 réponses 2,1k vues
In Paratext 8.0 (and later): You cannot migrate resources from earlier versions of Paratext. Resources have a different ... See also: How do I install a Source Language Resource?
[Expert]
anon421222
735
posée févr. 23, 2017
0 votes
1 réponse 313 vues
I try to migrate from 7.5 to 8 in in Kuvi project. I try to follow the steps in proper way. I was able to register ... three times still it is showing same. How can I migrate to 8.
anon480013 162 posée juin 22, 2017
0 votes
4 réponses 492 vues
I've been helping a user with the registration\migration process. We were able to migrate the actual project as well as a ... Can you advise us on how to resolve it? Thank you.
MSEAIT_LT 478 posée janv. 23, 2018
0 votes
1 réponse 341 vues
I have a user who has a notes project for his consultant checking. He types one or more notes per verse into the ... | Papua New Guinea [Email Removed].pgmailto:[Email Removed].pg
SIL LSS PNG 411 posée oct. 5, 2017
0 votes
1 réponse 248 vues
Trying to migrate a back translation project to Paratext 8 and have run into a problem where we get as reason for the ... . The ticket reference is PTXS-17256 Thank you, MSEAIT/LT
MSEAIT_LT 478 posée juil. 31, 2018
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
And I tell you that you are Peter, and on this rock I will build my church, and the gates of Hades will not overcome it.
Matthew 16:18
3,046 questions
6,006 réponses
5,671 commentaires
2,026 utilisateurs