0
507 次浏览

The Back Translation is setup correctly in PT7 and primary translation migrated fine.

Error Message: “Object Reference not set to in Instance of the object. If you are unable to resolve this problem, contact your support…”

I ran the project verify in PT7 and there were no errors found.

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

7 个回答

0
最佳答案

No, I think the problem can be worked around. I think there might be a couple issues here.

The first is that the project in question is not set as a back translation project. To have this work correctly in Paratext 8.0, I think it would be best if the project was first changed to be a back translation of the correct base project in Paratext 7.x. This can be done by changing the setting at Project > Project Properties and Settings > General tab > Type of project.

However, I don’t think that problem is causing the exception.

I was able to migrate your project just fine, so I think the exception is caused by a bad value in the C:\My Paratext 8 Projects\languageNameToCode.xml file. Could you try deleting this file to see if that fixes the migration problem?

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

Please use Help > Report a problem right after it happens to report this issue to us.
It’s unlikely to be a problem with your project.

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

I did report the problem

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

If this is likely a software issue, then I assume it may take a while and I should delete the PT7 primary project and have them continue in PT7 for now. Correct?
listentwice

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

It wasn’t originally a BT but I changed it to a BT and then did a S/R.

Today I went back and double checked the Project Settings says it is a BT.

较早的帖子 - 以原始语言显示
(1.2k 分) 发布
已重新显示
0

I will attempt to go back on Monday and delete that file and try again. I’m not sure how long they are in town.

Is it a problem that you are seeing it still as a Std Translation, but I see it as a Back Translation?

较早的帖子 - 以原始语言显示
(1.2k 分) 发布
已重新显示

No, I probably just pulled the wrong repository off the S/R server (I couldn’t tell who was the admin). :flushed:

EDIT: I just verified that that was the issue. I pulled the admin’s copy and it is a back translation. But that also means that I migrated the wrong copy, so I’m trying again.

EDIT 2: The migration still worked with the correct copy, so I still think it’s likely to be a problem with that file.

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

I deleted that file and migration was successful. Thanks!

Any idea what caused the bad value in that file?

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

Unfortunately, I don’t have any ideas. It probably would have been better if I had told you to rename it and send the bad file to us to look at. :sweat_smile:

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

相关问题

0
1 个回答 44 次浏览
有没有办法同时查看和编辑实际文本及其回译的圣经术语(Biblical Term)?我觉得这会非常有帮助,最好能在同一个窗口中完成!看起来似乎不可能,但有没有好的替代方案? 谢谢!
Roland 245 发布 提问于 二月 2
0
1 个回答 28 次浏览
我在尝试使用 圣经术语 (Biblical Terms)功能来使回译更加一致时,遇到了几个问题 例如,我的回译中有 sip (=sheep) ,但当我将其放入 圣经术语 中时,文本中只有 sip 被高亮显示(并用于一致性检查),因为括号内的部分被 ... 写法,因为斜杠被用于忽略词序 我尝试使用通配符来解决这个问题,但没有成功 有什么建议吗?提前感谢!
Roland 245 发布 提问于 一月 27
0
1 个回答 233 次浏览
我正在寻找一种简单的方法,帮助印尼语团队对其回译进行拼写检查,以便他们更容易进行搜索 @LivingField 在回复一个关于如何对英语/法语/西班牙语回译进行拼写检查的问题时提到,可以将一个名为 SpellingStatus.xml 的文件复制到 ... 使用拼写检查工具找到并更正拼写错误的单词,但要为其他所有单词点击对勾以标记为正确,将会花费很长时间
janetoruh 102 发布 提问于 一月 17, 2025
0
1 个回答 295 次浏览
时不时地,我会 将一章中的所有节标记为已完成 (通常是在我执行了查找替换以统一回译的一致性之后,然后我需要让受此更改影响的已完成章节显示为已完成) 任何做过这件事的人都会注意到, 将整本书中的所有节标记为已完成 ... 对话框也缺少针对 Status Check Boxes 的撤销选项 所以我的问题是,是否有简单的方法可以恢复到之前的勾选状态?
viverechristus 296 发布 提问于 十二月 31, 2024
0
1 个回答 385 次浏览
我试图提高书面回译的质量,这是一个独立的 Paratext 项目。Paratext 有一个拼写检查功能,原则上可以用来(填充)英语、法语、西班牙语等单词。有没有关于如何操作的“操作指南”?应该如何纠正书面回译? 提前感谢您的帮助。
goodgoan 347 发布 提问于 三月 6, 2024
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
There is neither Jew nor Gentile, neither slave nor free, nor is there male and female, for you are all one in Christ Jesus.
Galatians 3:28
3,049 个问题
6,007 个回答
5,672 条评论
2,029 位用户