Search results

Jump to: navigation, search

Page title matches

  • The 'Site Name' field is just a convenient name for managing/selecting repositories. Users may edit these without any loss of functionality, as long as they en ...des some but not all of CrossWire repositories and some of the Affiliated repositories.
    8 KB (1,191 words) - 11:36, 29 March 2024
  • # If so, can it be accessed by the module manager from other JSword or SWORD front-ends? ...ore Bibles" in "Help" of the Download version, you have access to two STEP repositories - '''Public''' and '''Licensed'''. Modules from the '''Public''' repository
    2 KB (367 words) - 15:29, 8 January 2018

Page text matches

  • * Module Tools (MODTOOLS) ...nd/or markup issues here: (only for modules in the main or av11n CrossWire repositories)
    2 KB (315 words) - 19:51, 26 July 2023
  • ==SWORD module sources== ...Updating|SWORD Module Remote Installation Source Repository Discovery and Module Updating]]
    6 KB (820 words) - 17:39, 11 August 2023
  • = Module Development Overview= If you want to learn how to create a SWORD module, this is the place to start. Here is a brief overview of the process:
    14 KB (2,376 words) - 20:31, 4 June 2020
  • The 'Site Name' field is just a convenient name for managing/selecting repositories. Users may edit these without any loss of functionality, as long as they en ...des some but not all of CrossWire repositories and some of the Affiliated repositories.
    8 KB (1,191 words) - 11:36, 29 March 2024
  • # Each Bible module will carry a .conf entry identifying its versification from an supported li # On system start, the engine will load, for each open KJV-divergent module, the relevant data presented in the relevant <tt>canon_{Versification].h</t
    11 KB (1,634 words) - 18:02, 29 June 2020
  • ....crosswire.org/sword/modules/ModInfo.jsp?modName=ESV downloadable from our repositories]. ...the modules that have been licensed to CrossWire for distribution. The KJV module is the only one for which we maintain the source, which you can obtain [htt
    13 KB (2,149 words) - 13:13, 8 January 2018
  • ...terested in creating a module from that material. If you want to see a new module, your quickest results will come from encoding it in OSIS yourself and subm ...ble.org''' repository. Many more languages are there than on the CrossWire repositories.
    66 KB (9,963 words) - 06:09, 23 July 2024
  • ...page documents in concise form fonts which are useful to specify within a module conf page and/or install on your computer if your chosen language has other ...nvisible). Bear this in mind when selecting the font directive for a Sword module in the conf file. </ref>
    20 KB (3,127 words) - 06:26, 4 July 2023
  • '''Report module errors for released modules via the bug tracker: https://tracker.crosswire. !width="7%"|Module Name
    14 KB (2,005 words) - 16:41, 9 March 2020
  • ==Module Development== Please first visit this page [[Module Development Collaboration]] &ndash; it may save you a lot of time.
    24 KB (3,995 words) - 14:02, 5 June 2023
  • ...the end of the last chapter. Fortunately, the WoC start and finish in this module is on chapter boundaries. If it had started in chapter 5 and finished in ch * Change osis2mod to accept a wider range of valid OSIS inputs, creating a module that the SWORD Engine can handle, specifically allowing how this is encoded
    27 KB (4,527 words) - 17:30, 11 February 2021
  • * Determine a module name based on the language, owner, & year of publication: (lowercase langua Many modules have a problem with notes tied to headers. This may not be a module problem, but an osis2mod problem or a SWORD engine problem. For example, us
    9 KB (1,468 words) - 15:11, 16 June 2012
  • ...ou can look at the MONGOLIAN, HALH (MONGOLIAN) [MN-MONG] entry of the UDHR module. Windows 7, FWIW, appears to ship with a font that has Mongolian coverage. ...tly try to re-establish contact with him regarding permissions for a SWORD module. [[User:David Haslam|David Haslam]] 15:04, 15 December 2009 (UTC)
    36 KB (5,651 words) - 18:29, 12 January 2018
  • This page describes important information about module configuration (.conf) files. All SWORD modules require one. == Key elements of a SWORD module.conf ==
    40 KB (6,129 words) - 06:22, 20 February 2024
  • # If so, can it be accessed by the module manager from other JSword or SWORD front-ends? ...ore Bibles" in "Help" of the Download version, you have access to two STEP repositories - '''Public''' and '''Licensed'''. Modules from the '''Public''' repository
    2 KB (367 words) - 15:29, 8 January 2018
  • ...wikipedia.org/wiki/File_Transfer_Protocol FTP] server to any working SWORD module installation (i.e. if via your FTP server and your module repository is done).
    2 KB (323 words) - 15:35, 10 January 2018
  • ...ped archive of a module in the file and directory layout used in the local module directory. To create a zipped module of an uncompressed GenBook do this:
    1 KB (209 words) - 15:36, 10 January 2018
  • === Module related === ==== Module Support ====
    95 KB (15,480 words) - 18:57, 26 June 2023
  • * If a module is in the ug language, when there are several script choices, which is it U ::Xiphos also uses language names as nodes in a tree in its module manager. [[User:David Haslam|David Haslam]] 17:35, 21 December 2009 (UTC)
    10 KB (1,591 words) - 10:55, 13 January 2016
  • ==== Correct the osisRef syntax for a non-verse-keyed OSIS module ==== Module:Div1/Div2/Div3
    41 KB (6,082 words) - 13:32, 14 June 2023

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)