0
464 次浏览

While doing Send-Receive for a specific project, all users get a notice that says,

> Paratext was unable to load the lth language file for the ThurM. Paratext will use the English language file instead. On clicking ok, Send-Receive completes just fine.

We had issues with this language before during registration. The ethnologue (lth) code was missing in the Paratext registry as it was a new language. But now on checking the registry, it appears fine and the LTH code in the registration is assigned to the Thur language.

What could be the problem?

较早的帖子 - 以原始语言显示
Paratext (135 分) 发布
已重新显示 | 464 次浏览

4 个回答

0
最佳答案

Unfortunately, even though the language was available in the Registry, it is still not available inside Paratext. I’m guessing that this is causing the issues you are seeing.

A fix for this has already been completed and should go out to everyone in the next week or so after internal testing is finished. Sorry about the problems this mismatch is causing.

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

已重新显示

anon670954,

It looks like John D created the lth language file in the project a few days ago. If you send/receive now do you get that file? (The file name is lth.ldml in the ThurM folder).

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

Thanks, anon291708.

kent_schroeder
Domain Team Leader - Language Technology

SIL Anglo-Lusophone Africa

Waxhaw NC 28173

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

Thank you all!

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

The update to Paratext containing the new language codes has gone out to everyone (version 8.0.100.62). Let us know if that does not fix the problem.

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

Thank you, the update worked and the language code was fixed. However, the back translation doesn’t seem to pick the language code from the parent/standard translation. It still shows eng. What can I do?

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

anon670954,

Normally the back translation uses a different language from the standard translation (usually the language would be English, or the language of wider communication). Please note that for earlier versions of Paratext if was important to always use a unique language so as to not change the settings for everyone else in the world using a language like “English” or “French”. However, Paratext 8.0 protects the language settings for each project.

The project administrator should be able to change the language by going to Project > Project Properties and Settings and either creating a new language or selecting one from the list of existing languages.

There is a new option in 8.0.100.63 that allows the administrator to register a back translation. If it has been registered, then I would presume that the language would need to be changed in the registry.

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

Thank you, anon848905!

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

相关问题

0
3 个回答 442 次浏览
image.png1366×768 109 KB Admin Edit: Fixed topic category.
anon388057 124 发布 提问于 十一月 2, 2017
Paratext
0
0 个回答 118 次浏览
When Paratext creates a problem report file, it encodes it using uuencode. In order to read the report file, you must ... creates a normal zip file on the desktop of your computer.
[Expert]
anon421222
735 发布
提问于 二月 23, 2017
0
2 个回答 281 次浏览
I learned today that you can define in a custom versification file verses that you don't want to be included in ... custom.vrs file from the NLT07 folder into your project folder.
[Expert]
sewhite
3.3k 发布
提问于 三月 1, 2016
0
1 个回答 75 次浏览
当我打开 Paratext 时,出现一条消息: 无法打开您计算机上的 DUOT 项目 该项目与此版本的 Paratext 不兼容 请使用此项目,请将 Paratext 升级到 9.5 或更高版本 我作为顾问参与 DUOT 项目 我担心如果我升级到 ... 的计算机上打开该项目 他们的一些计算机需要安装更多内存才能升级到 9.5,因此这不是一个简单的任务
anon407273 106 发布 提问于 五月 30, 2025
Paratext
0
2 个回答 554 次浏览
我们已完成新约翻译,目前正在从事旧约翻译工作。其中一位译者询问,目前是否有可能制作一份新约的逐词对照(interlinear),且其中的释义(glosses)使用目标语言。我假设这意味着需要翻译逐词对照中使用的所有释义,这将是一项艰巨的任务。但使用内置的逐词对照功能是否可行?是否有办法在其中提供自定义释义?或者是否有其他方法可以实现这一目标?
JohnBrownie 385 发布 提问于 六月 28, 2023
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
Accept the one whose faith is weak, without quarreling over disputable matters.
Romans 14:1
3,048 个问题
6,007 个回答
5,672 条评论
2,028 位用户