-
* CrossWire's [[Copyright|copyright]] policy
* How to create [[DevTools:Modules|SWORD Modules]] & [[DevTools:conf Files|Module Configuration Files]]
6 KB (820 words) - 17:39, 11 August 2023
-
#Obtain the source text and permission from the copyright holder if you wish to distribute a copyrighted module.
For Bible modules, SWORD supports a growing number of [[Alternate Versification|Versification
14 KB (2,376 words) - 20:31, 4 June 2020
-
...y the SWORD engine to process modules, by installers to help users install modules and by front-ends to render the module appropriately.
: DataPath=./modules/texts/ztext/kjv/
9 KB (1,381 words) - 06:47, 14 February 2020
-
...ee Software. We have several software products. We also have numerous text modules (Bible translations, commentaries, lexicons, ...) which can be used with ou
...ogramming_interface Application Programming Interface] (API) for CrossWire modules. When referring to SWORD it is customary to use all uppercase. It is someti
13 KB (2,149 words) - 13:13, 8 January 2018
-
Here is a place to request modules you would like to be made. If the copyright holder has been contacted, the permissions granted or not can be put here.
New modules are made largely on the basis of content availability and distributability.
66 KB (9,977 words) - 20:04, 17 January 2019
-
...ds.urbanpug.com/show.php?id=1346 renewed in 1950], which makes it still in-copyright today. NOTE: [http://renewalrecords.urbanpug.com/ urbanpug], google, Guten
...[http://www.sobicain.org Sociedad Bíblica Católica Internacional] is the copyright holder. My request is forwarded, but another in spanish is pending.
4 KB (590 words) - 21:07, 28 June 2018
-
...a program's module Install Manager, or from http://www.crosswire.org/sword/modules. They are also available on the [[SWORD CD]].
...ion modules can not be used because they are [http://en.wikipedia.org/wiki/Copyright copyrighted] and we cannot distribute them without permission.
8 KB (1,466 words) - 08:24, 10 September 2018
-
...interim option for Bible translators needing to test their privately built modules on any platform in which this font can be installed.
...udes Oblique, Bold & Bold-Oblique styles. Through such Bitstream fonts are copyright, they are freely distributable. See [http://dejavu-fonts.org/wiki/License].
20 KB (3,127 words) - 06:26, 4 July 2023
-
...conversion of material that is under copyright without permission from the copyright holders is not supported by The SWORD Project.
== SWORD modules ==
8 KB (1,308 words) - 12:11, 20 February 2021
-
* Installs modules to the USB drive.
* Able to use modules installed to the USB drive.
12 KB (1,861 words) - 15:17, 10 January 2018
-
...module team or the director who needs to receive the permissions from the copyright owner.
...r , thanks to local legislation is not a problem for them. As long as such modules are not discussed (explicitely or implicitly) or offered on the list for te
5 KB (861 words) - 16:46, 14 December 2020
-
I thought I'd move discussion about the implementation of modules here. It was cluttering the other page and when we'd get a new version or a
...the responsibility of osis2mod to placate the SWORD Engine by transforming modules to what it wants to hear. I think the best long term solution is for osis2m
27 KB (4,527 words) - 17:30, 11 February 2021
-
...m'''] was active (2007-2012) in developing [http://go-bible.org/ Go Bible] modules for [http://en.wikipedia.org/wiki/Java_Platform%2C_Micro_Edition Java ME] e
=== Copyright lobbying ===
3 KB (437 words) - 14:28, 11 January 2018
-
I am trying to establish contact with the copyright holders of the Wolof NT. [[User:David Haslam|David Haslam]] 15:16, 23 Octob
...ot placed this in the main article, as I have yet to make contact with the copyright holders. It's still in my tasks list. [[User:David Haslam|David Haslam]] 1
36 KB (5,651 words) - 18:29, 12 January 2018
-
Copyright 1999-2014 by the CrossWire Bible Society
...ems to be no command line option to toggle '''morpheme segmentation''' for modules in which the .conf file includes:
3 KB (502 words) - 20:40, 24 December 2017
-
...important information about module configuration (.conf) files. All SWORD modules require one.
...le library, the following conventions are recommended and must be used for modules wishing to be included in a CrossWire repository:
40 KB (6,129 words) - 06:22, 20 February 2024
-
# Does STEP have its own modules repository?
...llow us to put their works in the '''Public''' one. There are not yet many modules in either.
2 KB (367 words) - 15:29, 8 January 2018
-
...frontends should be able then to access this repository and download your modules.
To optimize a repository with a larger number of modules, an archive file of the mods.d directory should be created. The repository
2 KB (323 words) - 15:35, 10 January 2018
-
[[Software testers | Software]] or [[Modules in the beta repository| module testers]], [[Translating|translators]] and d
...in which volunteers can help is in the area of seeking permissions from [[copyright]] holders.
2 KB (362 words) - 22:42, 10 January 2018
-
== Avoiding duplication in copyright lobbying ==
...mbarrassment of having other volunteers duplicate the approach to the same copyright owners. [[User:David Haslam|David Haslam]] 17:04, 8 December 2008 (UTC)
7 KB (1,064 words) - 21:38, 11 October 2017
