0
596 次浏览

The instructions for 7.6β say:

You must ensure that the other members of the project team have upgraded
Paratext before you opt-in these features on the shared project.
Upgrade options are:
Upgrade team members to 7.5.100.46 or later.

    Team members will be unable to use Project Interlinearizer, Word

List, and Guess Translations, but can do other work. -or-Upgrade team members to the 7.6 Beta Test Version.

    Team members will need setup and training, will be more at risk 

of unexpected problems, and you will need to support them.

We have a lot of observers on our project, and none of them are in the same geographical location. I also have no way of knowing what version they currently have, apart from emailing them (and then, for some of them, emailing them again and again before I get an answer).

Or is it OK for users in an Observer role to have PT <7.5.100.46, since they can’t edit the text?

The feature where PT 7.6β2 flags out of date copies of PT in the summary it gives after an S/R is really nice … but it would be even nicer if it could tell you the PT version of all the users (the version they had the last time they S/R’ed). Then I could tell the relevant users to upgrade and do an S/R, and I’d know for sure that they really were on the latest version.

较早的帖子 - 以原始语言显示
Paratext (1.4k 分) 发布 | 596 次浏览

2 个回答

0
最佳答案

People who do not upgrade to 7.5.100.46 or later will be unable to open the project at all whether they are an observer or not. You can use the project without enabling the new 7.6 features and the project will continue to be able to be opened by previous versions of Paratext.

There is a way (more of a workaround :neutral_face:) to see the versions of all users on your projects in 7.6 by opening Project > Recent Changes and selecting a date that is far in the past.

较早的帖子 - 以原始语言显示
[Expert]
(16.7k 分) 发布

Looks like I was being too pessimistic: I thought that there was a danger that users of the old version would corrupt the project (I think there was a PT upgrade once that was dangerous like that). Thank you for giving more detail than the beta instructions did!

Nice hack. Though it’s not going to catch those observers, who never make changes to the project :unamused:.

The beta help also says:

After the team member computers are upgraded per either option above:
I. You opt-in on the project, and complete the Send/Receive that is initiated.
But don’t use the new features yet.
II. Then have all team members Send/Receive the project.
III. Then you may use the multi-parse and infix features.

We have 27 project members, of whom only 7 are currently in our office. I really don’t know how I’m going to determine when everyone has done an S/R. The instructions also don’t tell me what would happen if I use the new features when one user still has not done an S/R.

I’d love a feature in PT that says: “Inform Administrator when everyone has done an S/R”!

较早的帖子 - 以原始语言显示
0

I’m still looking for an answer to this. It’s hard for me to force our ten Observers to upgrade in a timely manner. Some of them are occasional users; some go on extended leave and don’t read the emails I send them; etc.

If, after I opt-in, an Observer with PT <7.5.100.46 tried to open the project, they will presumably not be prevented from doing so, since their old version of PT will be unaware of the new feature. Will they mess up the SFM files as a result? Or does the fact that they can’t edit the text protect the files from corruption. That’s the key question!

较早的帖子 - 以原始语言显示
(1.4k 分) 发布

If the user has a version before 7.5.100.46 (or maybe a little before this,
we did several changes related to accessing 7.6 versions in 7.4 and 7.5),
they will get a message saying that the project can’t be opened and it will
not be in the list of available projects that they can view.

The final out come was that 7.5 users will be able to open a 7.6 version
project (the version after opt-in is done), but will not be able to open
interlinear related forms since 7.5 doesn’t support the new format.

较早的帖子 - 以原始语言显示

相关问题

+1
3 个回答 499 次浏览
我们有一位用户希望在 Paratext 项目中以笔名工作 管理员也希望阻止该用户看到翻译团队的其他成员 目前,我们建议他们使用辅助项目(Auxiliary project),其中该笔名用户是唯一用户 我建议他们只处理其他成员已完成编辑的书卷,或 ... 可能具备跟踪父项目更改的功能(类似于回译状态复选框),但我不确定这是否是该场景下的最佳建议 谢谢,
[Moderator]
james_post
2.1k 发布
提问于 十一月 12, 2021
0
2 个回答 350 次浏览
I have a colleague who is being frustrated with the English interlinearizing of the Greet NT source text in Paratext ... copyright restrictions. But I thought it was worth asking.
anon703820 222 发布 提问于 一月 31, 2018
0
2 个回答 436 次浏览
A user accidentally put about 120 MB of pictures into his figures folder, and Paratext wants to Send/Receive ... Papua New Guinea [Email Removed].pgmailto:[Email Removed].pg
SIL LSS PNG 411 发布 提问于 二月 21, 2017
0
8 个回答 1.4k 次浏览
We have a user who has inserted a lot of \pn and some \nd inside of footnotes. We now know we need those to be ... the search to inside of a single footnote? Thank you, MSEAIT/LT
MSEAIT_LT 478 发布 提问于 八月 20, 2018
0
1 个回答 34 次浏览
我们在脚注交叉引用中使用了 /xt,设置为使用书籍的“短名”。但在词汇表中,我想使用书籍名称的缩写,是否有不同的 USFM 代码可以实现这一点?
Lenice 180 发布 提问于 十月 7, 2025
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
Every day they continued to meet together in the temple courts. They broke bread in their homes and ate together with glad and sincere hearts, praising God and enjoying the favor of all the people. And the Lord added to their number daily those who were being saved.
Acts 2:46-47
3,045 个问题
6,005 个回答
5,671 条评论
2,026 位用户