0
471 次瀏覽
  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 點) 提出
已重新顯示 | 471 次瀏覽

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 提出 已提問 2月 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 提出 已提問 1月 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 提出 已提問 9月 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 提出 已提問 2月 1, 2019
0
1 個回答 38 次瀏覽
我正在與一位同事合作,據我所知,他已經正確地在 Paratext 中關聯了他的 FLEx 專案。但當他在 FLEx 中前往「選擇文本」(Select texts)時,沒有看到「聖經」(Bible)類型。這裡可能出了什麼問題? 謝謝, Aaron Wade
aaron_wade 124 提出 已提問 12月 1, 2025
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
And over all these virtues put on love, which binds them all together in perfect unity.
Colossians 3:14
3,051 個問題
6,010 個回答
5,676 則評論
2,030 位使用者