0
469 次浏览
  1. Does PT8 apply appropriate restrictions to each resource based on the licences that apply to that resource? The WEB/WEBUK resources are Public Domain, i.e. they have no restrictions on their use whatsoever – but the following commands or operations are disabled:
  • Print Draft… ;
  • Print… ;
  • Save as RTF… ;
  • Export to Pathway… ;
  • disabling View ➢ By Chapter;
  • copying more than 800 characters of the text.
  1. Am I correct in thinking that that all the above restrictions have been implemented because they are considered appropriate for resources that are “© All rights reserved”? I believe that many printed editions will allow you to photocopy multiple chapters for personal use, as long as they do not constitute a complete book, so the PT restrictions are much more stringent, and effectively prevent you from printing even a single chapter – which you might want to do for a number of reasons, e.g. in order to annotate the text with coloured pens as part of an exegetical or textual study exercise.
较早的帖子 - 以原始语言显示
Paratext (1.4k 分) 发布
已重新显示 | 469 次浏览

3 个回答

0
最佳答案

I can’t comment on your general question, but as for the particulars of WEB…

A while back I needed a PT project to play with without any concerns of breaking it, and thought a Public Domain option would be great. Someone recommended WEB and I found the files within about 5 minutes online and needed little or no conversion to get it set up. Meaning they must have been in USFM format or something very close. So, at least in this case, you could easily create your own project of it.

[Note that in the past posts have been deleted for showing how to bypass the PT copyright restrictions, but I do not believe this is doing that. This isn’t decrypting the PT WEB resource, it’s finding a free version of it elsewhere and importing it into PT just like we do with many other projects. However, the admins can delete this if they disagree with me.]

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

Telling everyone how to get a Bible that is already publicly-available in the USFM format is definitely not against the rules. :grin:

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

This USFM has Strongs Number information, which makes it hard to read. Best is Preview view, but still every word in the canonical books is displayed with an asterisk in front of it. I could use a regex to strip out the Strongs, but is there a better way to get a readable WEB Bible (that I can print out freely)?

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

I’m not sure what you are asking. You have pointed out that the public domain resource that you have is restricted. Paratext is not making any distinction based on type of resource. If a resource is downloaded from the DBL then it will be restricted.

As was pointed out - there are other ways to get some resources that might be unrestricted.

If you feel that resources should be restricted based on their copyright you could submit a feature request to Paratext (this site is not the place to make feature requests).

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

I believe anon848905 is correct that Paratext 8 does not apply any resource-specific logic when restricting copy/paste etc. Rather, it simply applies those restrictions to all resources.

If that is a significant inconvenience to you, you can use Help > Make a Suggestion to request a more granular approach. Are you only asking about Public Domain resources, or also about resources whose licenses seem more “permissive” than most?

I’m not sure how easy it is to confidently identify such resources programmatically, but we could see what information exactly DBL supplies to Paratext.

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

I strongly recommend a bit more granularity on copy/paste/export restrictions. There are many resources in the DBL that are Public Domain or under a Creative Commons license that should not have any such restrictions on them. It should be possible to mark those as free to copy, just as I have done with the entries that don’t have a gray background at https://eBible.org/find/. Yes, people can look there for USFM Bibles, but why make them import another project into paratext just to get the export working?

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

(I know this is getting off topic, and if the conversation continues, I’ll make sure it continues elsewhere.)

@anon854042, it would be nice if there was an explanation on that page of what the grey background means.

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

相关问题

0
1 个回答 261 次浏览
关于书卷缩写(TOC3),“选择书卷名称缩写的最佳实践”帮助页面强调了项目内部一致性的重要性。因此,只要某个项目内部保持一致,在排版/出版方面对书卷缩写是否有任何限制?例如,书卷缩写是否必须由特定数量的字符组成(例如三个)?是否允许使用空格?是否允许使用首字母缩略词和首字母组合词?我之所以这样问,是因为从功能上看,Paratext 似乎对这些问题都没有问题。
drwww 448 发布 提问于 二月 16, 2021
0
1 个回答 222 次浏览
Is there a list of restrictions to a project if it is not registered in Paratext 8? This would be helpful to know ... | Papua New Guinea [Email Removed].pgmailto:[Email Removed].pg
SIL LSS PNG 411 发布 提问于 一月 30, 2018
0
2 个回答 320 次浏览
See this this posting and ff in thread: Recovered unsaved text for resource? [I am] the person responsible for all the Paratext Resources on the webpage [paratext.org .]
wdavidhj 1.4k 发布 提问于 九月 17, 2015
0
1 个回答 420 次浏览
If a resource is available to me to download via Download/Install Resources, what can I assume about licensing/ ... when someone makes a resource as available to all translators.
jbabt 115 发布 提问于 二月 1, 2019
0
1 个回答 38 次浏览
我正在与一位同事合作,据我所知,他已在 Paratext 中正确关联了他的 FLEx 项目。但当他进入 FLEx 的“选择文本”(Select texts)时,却没有“圣经”(Bible)这一类型。这里可能出了什么问题? 谢谢, Aaron Wade
aaron_wade 124 发布 提问于 十二月 1, 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,051 个问题
6,010 个回答
5,676 条评论
2,030 位用户