Search results

Jump to: navigation, search

Page title matches

Page text matches

  • ...to revert to the original source text, but to apply a replace list on the OSIS file to correct the orthography. This is probably quicker to implement than BlockType=BOOK
    2 KB (337 words) - 10:04, 4 August 2009
  • ...online at [http://lugandaministry.org/Bible.html]. It is laid out Book by Book and Chapter by Chapter, except for some corrections to be made in the text ...ry adjustments. Then we put out a new version on our website and the Bible book may be a new audit letter. Because it is advisable to wait here until the t
    36 KB (5,651 words) - 18:29, 12 January 2018
  • osis2mod transforms an OSIS encoded [[OSIS Bibles|Bible]] or [[OSIS_Commentaries|commentary]] into a SWORD module. * Added reporting of unhandled entities. (An OSIS document should not have entities other than the canonical 4 entities.)
    34 KB (5,473 words) - 16:45, 9 March 2020
  • ...ctories under lexdict. A glossary is between two languages.</ref>, general book) and<BR>(b) the data driver (ModDrv parameter) are: '''OSIS''' ([http://www.bibletechnologies.net Open Scriptural Information Standard]
    40 KB (6,129 words) - 06:22, 20 February 2024
  • | '''Shows book introductions''' | [[Alternate Versification]]<ref>Modules with a different book order may have navigation problems in some front-ends.</ref>
    95 KB (15,480 words) - 18:57, 26 June 2023
  • ...cross-references to John 3:16. (JSword will normalize the reference to an OSIS ID.) ...ule, this may change. If we discuss it and then document the behavior in [[OSIS Bibles]] that would be fine.--[[User:Dmsmith|Dmsmith]] 19:58, 8 March 2009
    72 KB (11,844 words) - 16:32, 1 May 2020
  • This page contains an example OSIS document that is structured by Book-Section-Paragraph. *Book introduction
    10 KB (1,373 words) - 11:25, 5 March 2012
  • ...ed in Ethiopia: the Protestant 66 book canon and the Ethiopian Orthodox 81 book canon (called the narrow canon). The so-called broad canon has never been Should there be a "book" abbreviation for the following introductions?
    8 KB (1,224 words) - 09:39, 23 June 2020
  • ...chor reference named "n3", typically used for footnotes; can use either ! (OSIS) or # (ThML). * '''sword://Josephus//The+Antiquities+of+the+Jews/Book+1/Chapter+1/Section+4''' -- non-bible module. The 2nd double "//" is becaus
    4 KB (612 words) - 17:50, 26 July 2012
  • For "milestoned" form of OSIS XML files, there is an XSLT script available to convert these to the "conta ...m/p/osis-converters/ osis-converters] includes a Perl script that converts OSIS files to make Go Bible applications.
    11 KB (1,754 words) - 11:41, 8 January 2018
  • [[OSIS_Tutorial|OSIS Primer - A Tutorial]] [[OSIS_Bibles|Guide to Writing OSIS Bibles]]
    473 bytes (64 words) - 21:25, 11 January 2019
  • ...recording potential change requests to the [http://bibletechnologies.net/ OSIS] 2.1.1 XML schema, and for defining our own updated schema. The '''BTG''' that sponsored the OSIS committee and hosted the OSIS schema no longer exists.
    41 KB (6,082 words) - 13:32, 14 June 2023
  • ...of the word '''osisRef''', evidence that it was originally derived from an OSIS XML file. Its revision history has "2002-06-10 Converted from GBF text." [[ ...hen our independent work was essentially done. His is not derived from the OSIS. Ours is not derived from the ThML. We compared the texts for differences a
    12 KB (1,818 words) - 21:23, 22 January 2016
  • * '''OSIS''' &ndash; a single XML file using OSIS format # For use with Go Bible Creator, an [[OSIS Tutorial|OSIS]] file must be of the ''container'' type, not the ''milestone'' type.
    28 KB (4,515 words) - 19:06, 14 July 2015
  • The Biblical text display now includes simple book and chapter headings, such that during continued scrolling, there is a bett UI-Action-Next-Book: Next Book
    24 KB (3,372 words) - 07:08, 4 January 2017
  • ''Peter has had some success in converting ABW files to OSIS using scripting tools''. ...''extensible''. OXES is ''restrictive''. All options are explicitly named. OSIS focuses on the ''finished'' translation. OXES includes ''process informatio
    8 KB (1,272 words) - 10:06, 11 January 2018
  • ...e is intended to be a one-stop reference which lists all the extensions to OSIS either recognized by the SWORD API or (at least) also found in various SWOR The OSIS reference standard permits custom extensions to XML elements in the form of
    18 KB (2,917 words) - 20:30, 4 June 2020
  • ...rules. As further pre-processing tools are being developed (such as USX to OSIS), having a one stop reference should be valuable to help developers ensure == Non-CrossWire OSIS eXtensions ==
    11 KB (1,599 words) - 17:45, 10 January 2018
  • ...ies are translation strings for anything you might want. REQUIRED are the book names of the Bible, including deuterocanonical books if used. Other things # <snipped rest of book names>
    6 KB (946 words) - 20:59, 19 August 2019
  • * Keep the notes in book and chapter titles, suggested by [[User:Yvand|Yvand]] :Currently notes in book titles ([http://koocotte.org/darby/html/Song.html Song], [http://koocotte.o
    10 KB (1,677 words) - 20:30, 15 May 2017

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