-
For Bible modules, SWORD supports a growing number of [[Alternate Versification|Versification
...ith the sole exception texts based on CCEL documents that are marked up in ThML.
14 KB (2,376 words) - 20:31, 4 June 2020
-
'''IMPORTANT:''' CrossWire now accepts only GenBook modules and LexDict modules in IMP format. Bibles must be in either VPL or OSIS format.
...ly markup accepted are scripture reference links in OSIS or ThML All other modules need to be in valid OSIS or TEI XML files before submission is accepted.
3 KB (576 words) - 16:29, 11 March 2018
-
The ThML of this module can currently be found at CCEL ([http://www.ccel.org/ccel/sc
...y split into to 2. Would this complicate things if we distribute this as 2 modules, or should it be compressed into 1?
536 bytes (82 words) - 10:21, 4 December 2009
-
.... It includes scripts that module authors may use in their preparation of modules. These are mainly undocumented and not intended for any public release. D
...S, as losslessly as possible. The OSIS can then be used for creating SWORD modules. See the README in the relevant directory for more information.
4 KB (585 words) - 18:22, 10 January 2018
-
...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
-
'''xml2gbs''' 1.0 is the OSIS/ThML/TEI General Book module creation tool for the SWORD Project.
...ml here]. The purpose was to solve the computational problem of why custom modules and the tutorial had not loaded successfully to a SWORD app.
5 KB (591 words) - 21:13, 9 June 2023
-
Here is a place to request modules you would like to be made. If the copyright holder has been contacted, the
New modules are made largely on the basis of content availability and distributability.
66 KB (9,977 words) - 20:04, 17 January 2019
-
== SWORD modules ==
...the following markup for module creation: OSIS, [https://tei-c.org/ TEI], ThML and plain text.
8 KB (1,308 words) - 12:11, 20 February 2021
-
:The sourceforge repository for various modules is still available at [http://sourceforge.net/projects/zefania-sharp/]. The
::Haoila is what's used to create all the SWORD Bible modules now hosted at eBible.org [[User:David Haslam|David Haslam]] ([[User talk:Da
12 KB (1,955 words) - 13:18, 8 January 2018
-
Further, we do not support GBF anymore other than in legacy modules. We also have seen for years (ie.e since I am part of the project) any sugg
...e.jolon.org/developer/welcome.html Go Bible Creator] can take either USFM, ThML or OSIS as the source text format, but they usually have to be made special
3 KB (567 words) - 12:30, 28 April 2018
-
...odule type is used to contain modules keyed to non-hierarchical keys. Such modules include: dictionaries (indexed by words or numbers), glossaries (simple one
...uments. Since TEI is modular, it is possible to ignore the majority of its modules and use only a smaller set of tags necessary to our needs.
14 KB (2,213 words) - 11:27, 5 February 2021
-
...edia.org/wiki/ThML ThML] is another XML schema which can be used to create modules for CrossWire software.
''ThML support is no longer actively pursued by CrossWire developers. New content
2 KB (292 words) - 12:38, 8 January 2018
-
...query for a verse (or verse list/range), a search, a request for a list of modules, etc.
| for modules with GlobalOptionFilter=UTF8GreekAccents<ref>Refer to [[DevTools:conf Files
10 KB (1,547 words) - 17:14, 13 April 2018
-
Valid output_format values are: GBF, ThML, RTF, HTML, HTMLHREF, XHTML, OSIS,
...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
-
...edition red letter] markup errors had been reported or observed in the KJV ThML source file, originally downloaded from CCEL, and as used for making the [h
::: Interesting! Our modules should follow the 1769 text, as described in the conf files. And DM's polic
25 KB (3,753 words) - 21:20, 22 January 2016
-
...eryone seems to give about their frontend. Archiving is GS tem for keeping modules out of sight but available. It does what it says on the tin. BT has (I thin
..., and will probably be an integral part of future plans to allow uploading modules. Also, you can archive a module, then remove it (which would also affect ot
72 KB (11,844 words) - 16:32, 1 May 2020
-
...ce named "n3", typically used for footnotes; can use either ! (OSIS) or # (ThML).
...(or there is no module specified), the app will firstly bring up a list of modules of the type specified & then when the user selects a module, the verse is v
4 KB (612 words) - 17:50, 26 July 2012
-
...Bible application to act as something like a front-end for CrossWire Bible modules on the Java ME platform. The author of the Go Bible application and the de
...o be done towards automating the software tools to convert CrossWire Bible modules to one of the formats suitable for use with [[Projects:Go Bible/Go Bible Cr
11 KB (1,754 words) - 11:41, 8 January 2018
-
...ou want to get such a repository on the CrossWire server please email to ''modules'' AT ''crosswire'' DOT ''org''.
...setup for its internal development and for the automatic (re)deployment of modules.
4 KB (573 words) - 12:57, 18 December 2015
