0
158 次瀏覽

I encountered a weird error migrating a project. The migration went fine, Paratext reported the project had migrated, but then it showed this error when opening the project.

It turned out there were some extra characters in the scripture reference settings (viewed in Paratext 7.5) that was causing this.


When I cleared out the extra characters in Range of verses in 7.5, then deleted the project from 8 and remigrated it, I had no problems.
舊文章 - 以原文顯示
Paratext [Expert]
(3.3k 點) 提出
| 158 次瀏覽

登入註冊 以回答此問題。

相關問題

0
3 個回答 1.3k 次瀏覽
During migration from Pt7.5 to Pt8, or in Convert Project, is there any way that I can change the Based on: ... care of these things, but ran into the problems described above.
anon492507 123 提出 已提問 8月 17, 2017
0
2 個回答 877 次瀏覽
Editing permissions are copied from Paratext 7 to Paratext 8 during migration. This can potentially cause problems ... Permissions can interact and use the appropriate caution.
[Expert]
Jeff_Shrum
2.9k 提出
已提問 5月 9, 2017
0
3 個回答 231 次瀏覽
Hi, I have a project that was submitted to DBL several years ago under PT7.5. I now want to migrate that project to ... the current DBL version of the project to be in Paratext 8.
anon251522 150 提出 已提問 2月 18, 2019
0
2 個回答 296 次瀏覽
I was migrating our project into Paratext 8 from Paratext 7.5 and in the migration all the word selections and ... doing an interlinear on a fresh project. Is this intentional?
Generic.User 238 提出 已提問 7月 9, 2018
0
0 個回答 131 次瀏覽
This is probably due to a forced language identifier change during project migration to Paratext 8. This has happened ... lexical term itself only shows as three question marks.
[Moderator]
dhigby
1.3k 提出
已提問 12月 7, 2017
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
All the believers were one in heart and mind. No one claimed that any of their possessions was their own, but they shared everything they had.
Acts 4:32
3,048 個問題
6,007 個回答
5,672 則評論
2,028 位使用者