0
537 次浏览

Under Resolving Conflicts in P8 Helps I read:

“Changes Paratext Rejected” or “Merge all changes” in step 5 above only work in Paratext 8.0 if the users whose changes create the conflict have Paratext 7. 5.100.16 (or later).

It is awkward to have a P8 feature that only works if you have a version 7 installed on the computer. I have noticed the feature working in 7.6, but did not notice it in 7.5.100.87. In my experience, it only works if 7.6 is installed, not the latest 7.5. I like the feature, so my question is: Will this be included in P8 or do I need to ask all the translators to install 7.6 just to get his working after all translators have migrated to P8?

Yesterday we had conflicts caused by a malfunction in Paratext Live. The conflicts “created” by those with 7.5.100.87 did not have the feature. The conflicts “created” by the only computer with 7.6 did have the feature.

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

4 个回答

0
最佳答案

We are 5 computers all with Paratext 8. One of them has P7.6, the others 7.5.
I always found the older/newer information confusing because it was not clear to me whether it was the time the edit was made on the computer or whether it was the time of the S/R. We did some testing today and realized that it was the time of the S/R, not the time the edit was done. P8 apparently accepts the latest it has received and rejects earlier ones. We did one round where the computer with 7.6 was the latest to do S/R, so this was the computer that “created” the conflict. (It is not helpful to talk about who created the conflict, because all five computers had a share in that creation, but it is helpful to tell the user which computer should resolve the conflict.) Only the computer with 7.6 had the option of keeping the latest or the earlier change. (It was also confusing that the computer thought the older was the later and vice versa.) You could also merge the two, but it was not possible to reject both. (We needed that for our test, but that is a special situation, so I am not saying that an option to reject both is needed.) On all the other computers, the conflict note looked very different. None of them had the option to change what P8 had accepted.
We then did a different experiment where the computer with 7.6 did S/R first and another computer later. This note was then named after the latest S/R as the one who had “created” it. Here there was no option on that computer to select anything. It only informed us that the earlier change was rejected. That change was not even shown, so the red/green information was confusing. There was no red/green difference. He could only resolve the note and go to the text to correct. The computer with 7.6 did not get the option of choosing either.
So, the reason I mentioned about 7.6 is that P8 behaves differently whether 7.6 is installed or not. It is quite complicated and needs more programming work after testing.

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

The option for choosing which change to accept/reject is only available to the administrator on the project or to the person the note is assigned to. I’m guessing this just happened to be the user who had 7.6.

You can think this, but trust me when I say that it’s impossible for 7.6 to affect 8.0 in this way. PT7 and PT8 have completely separate data sets so they can not affect each other.

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

Some clarification:
The new functionality for conflicts required additional information to be stored in the conflict note. Previously, only the change that was rejected was put into the conflict note, but this new functionality required the change that was accepted as well. The code to add this new information was added to 7.5.100.16 so that any computer that creates a conflict note with that version or later would create the conflict note with the needed information.
However, the code actually needed to do the resolution (i.e. to allow the user to choose which version wins in the UI) was added in 7.6. The reason the information needed for this new UI was added in 7.5 was because of the fact that many projects have people using different versions of Paratext and we didn’t want this new functionality in 7.6 to be useful only if the conflicts happened to be created with the users 7.6.

You do not need to have Paratext 7 installed to use this feature in 8.0 - I’m not sure what made you think that.

EDIT: It looks like the help topic is a little confusing with its current wording. We’re probably just going to remove that blurb about Paratext 7.5 from the 8.0 help since it was really information intended for 7.6. :disappointed_relieved:

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

已重新显示
0

Thanks. So it is the administrator only. The Help says:

We recommend that only the following users resolve a conflict note:

          An administrator who feels capable of making a decision regarding the conflict, or
          A translator to whom the administrator has assigned the conflict note.

How does the administrator assign the conflict note to somebody?
What is meant by “the person the note is assigned to”?

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

Ok, I saw now where the administrator can assign the not to somebody. Thanks.

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

We appreciate all the work that has gone into P8 and the strain created by the pressure to get it out. It looks like there is quite a bit of work still to be done on the Help interface and contents. Maybe many people learn P8 at a workshop, but I don’t. I have watched a few old videos, but have not had time yet to watch the new ones, and I am on a metered modem connection right now.
Our merge conflicts mainly resulted from the use of Paratext Live. I have decided that Paratext Live is not a good option for our project with 6-7 computers working together in a small city. It seems that it always (well, the 2 times we have tried it) loses the connection with conflicts as a result, even if everybody does S/R morning and evening and before a live session. We can manage without it.
I am happy that it is possible to choose other options than the red/green difference, since I am red/green colour blind. blue/yellow would not be a problem
I was initially confused by this statement: “Changes Paratext Rejected” or “Merge all changes” in step 5 above only work in Paratext 8.0 if the users whose changes create the conflict have Paratext 7. 5.100.16 (or later)."
This must be a carry-over from 7.6, since it has no place in P8. When we use P8, everybody does so, and it is irrelevant to talk about users using P7.5.100.16 (or a later version of P7) and should be deleted. What is relevant is that it only works for the administrator.
I have not found the place where it clearly says that the Administrator sees a completely different conflict note than the translators. The one which is shown to the administrator is very clear with two windows, the others see a note that is so obscure that it is better not to have them. My recommendation is that all should see the same clear note with two windows, the only exception being that only the administrator has authority to make choices. He/she should also be the only one to be able to resolve the note. At the moment anyone can apparently resolve these note. It is ok to get input from the translators about choosing options if he/she is not sure, and it is ok to be able to delegate the authority to somebody although it is cumbersome and time consuming with several S/Rs.
Thanks for listening.

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

The best way to give us information like this is to use Help > Report a Problem or Help > Make a Suggestion inside Paratext. This will ensure the information gets into our issue tracking system so that it is not lost.

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

Thank you. I shall do that.

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

相关问题

0
0 个回答 154 次浏览
当我们的项目处理圣经模块时,我们在 XXC 书中频繁遇到合并冲突 但这些 冲突 实际上是与原始位置的编辑相关的问题 有时这与原始引用位置的冲突相对应,但其他时候,它似乎仅仅是由于特定用户何时打开其 XXC 书并因此刷新 ... ]] 我正在考虑撰写一份错误报告/功能请求,但我也在 wondering 是否有关于系统的某些方面是我 simply 没有理解的
mnjames 1.9k 发布 提问于 二月 5, 2022
0
3 个回答 281 次浏览
我们翻译团队正在使用 Paratext,并通过 Paratext Live 连接了 4 台电脑 有几个地方,两名团队成员在非共同工作时间对同一节经文进行了编辑,因此这些位置出现了红色的小冲突三角形,以提示存在冲突 然而,当我们通过 ... 按钮 这是正常的工作方式吗?我以为如果我解决了,其他人就不需要再操作了? 感谢提供任何建议 anon110449
anon110449 114 发布 提问于 六月 17, 2021
0
2 个回答 275 次浏览
由于未知原因,我们在几个章节的空节上出现了冲突。 除了逐个处理之外,有没有什么方法可以清除它们?
listentwice 1.2k 发布 提问于 五月 14, 2021
0
5 个回答 321 次浏览
我有一个测试项目,其中有多人拥有写入权限(有点混乱),在两个人并行创建了一些新书之后,我遇到了数千个冲突。有没有办法批量解决它们?
jeffh 1.4k 发布 提问于 十二月 2, 2020
0
1 个回答 261 次浏览
我在 Paratext 9 中执行了发送/接收(Send/Receive)操作 已发送和接收的更改 (Changes Sent and Received)菜单显示,我有 102 个来自 2020-08-05 的冲突,以及今天(2020-08-31)的 1 个冲突 对 ... 报告 我真的希望我没有丢失任何数据 有其他人遇到过这个问题吗? 感谢您的帮助
anon070573 110 发布 提问于 八月 31, 2020
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
Live in harmony with one another. Do not be proud, but be willing to associate with people of low position. Do not be conceited.
Romans 12:16
3,047 个问题
6,007 个回答
5,672 条评论
2,027 位用户