Modules in the beta repository

From CrossWire Bible Society
Revision as of 13:32, 8 January 2018 by Refdoc (talk | contribs) (→‎Other Bibles: These texts are uploaded a long time ago to Main)

Jump to: navigation, search

Report module errors for released modules via the bug tracker: http://www.crosswire.org/bugs/browse/MOD

Please use the guide on Testing of new modules to test below listed modules and note your findings down.

Beta Modules

Bible Modules

Original Language Bibles

This section should primarily contain Greek and Hebrew Bibles, but others that serve as source texts for various denominations may also be placed here (i.e. Latin, OCS, Syriac, & Coptic texts).

Module Name Updated Does the module appear complete? Encoding problems? .conf problems? Display problems on any frontend? Ready / Fix / Hold
Tisch 2008-11-28 John 8:53 has 375 <w> elements, the last of which stops in the middle of an attribute value (meaning it is is not valid xml). Hold until John 8:53 is fixed.


English Bibles

Module Name Updated Does the module appear complete? Encoding problems? .conf problems? Display problems on any frontend? Ready / Fix / Hold
ABU 2008-11-11 NT only, conf reflects this, appears complete features: WoC

There was a WoC display problem (which needs to be tested).

See Talk:Modules_in_the_beta_repository#ABU for a discussion.

Anderson 2009-01-19 NT only, conf reflects this Multiple OCR errors in the text source[1]
Needs checking against a hardcopy[2]
KJC 2008-06-28 NT only, conf reflects this Red letter is a complete mess!
Twenty 2009-01-23
  1. ↑ A better quality source text is online at [1].
  2. ↑ David Haslam owns a facsimile edition.

German Bibles

Note: Versification of German Bibles in the Old Testament is in stretches extremely different from the KJV. Both chapters and verses are of different length. As a result a lot of KJV verses, particularly at chapter ends are empty and other chapter ends are overloaded. Particular problems exist in the minor prophets: Joel has 4 chapters and Malachi only 3 in original versification. As a result, subsequent verses appear empty when KJV versification is imposed. The end of Malachi 3 can cause "Error reading ulBuffNum" in the outputs from Sword conversion and diagnostic utilities.

Module Name Updated Does the module appear complete? Encoding problems? .conf problems? Display problems on any frontend? Ready / Fix / Hold
GerElb1871r 2008-07-08 Various disconnected chapters of various books
 None Displays well in GS, BD, SW,
GerLut1545lh 2008-07-15 Needs verse linkage in a few cases. Hold for updated osis2mod. Hold pending update to osis2mod.
GerLut1912 2008-07-17 Whole Bible Displays fine in BibleCS,GS,BD, SW

Has an inability to display pre-verse titles, which are very common, resulting in display problems in most frontends. Might need to wait on osis2mod update before release.


Dictionary Modules

Module Name Updated Does the module appear complete? Encoding problems? .conf problems? Display problems on any frontend? Ready / Fix / Hold
Strong 2008-11-26

H8342 transliteration is: ώâώôn ώâώôn Is that really right? (in module: samekh->s, sin->ώ, shin->sh, tsade->ts; in printed text: same except samekh->c-cedilla, sin->s; conclusion: change s (except in ts/sh) to c-cedilla, and change ώ to s)

H5019 has the transliteration, pronunciation and original language mixed up. 

<entryFree n="H5019|נבוּכדנאצּר">
  <title>
    H5019
  </title>
  <orth>נבוּכדנאצּר</orth> 
  <orth rend="bold" type="trans">
    נבוּכדרא צּור    נבוּכדראצּר
  </orth> 
  <pron rend="italic">
    n<hi rend="super">e</hi>bûkadne'tstsar
    nebûkadre'tstsar  nebûkadre'tsôr
  </pron>
  <lb/>
  <def>
    <hi rend="italic">
      neb-oo-kad-nets-tsar'
      neb-oo-kad-rets-tsar'
      neb-oo-kad-tsore
    </hi> 
    <lb/>
    Of foreign derivation;
    <lb/> 
    <hi rend="italic">
      Nebukadnetstsar
    </hi>
    (or
    <hi rend="italic">
      retstsar
    </hi> 
    or
    <hi rend="italic">
      retstsor
    </hi>
    ) king of Babylon: -
    Nebuchadnezzar 
    Nebuchadrezzar.
  </def>
</entryFree>

What should be the second part of the <orth> tag is put in the <orth type="trans">, the transliteration is put in the pron, and the pronunciation is left all alone outside.

StrongsGreek 2009-04-06
StrongsHebrew 2008-11-25
Easton 2008-11-29
Autenrieth 2007-09-22 None Known bad, do not test
BosworthToller 2010-07-08 None Known bad, do not test
CleasbyVigfusson 2007-09-05 None Known bad, do not test
LewisElem 2007-09-22 None Known bad, do not test
LewisShort 2007-09-21 None Known bad, do not test
LiddellScott 2008-12-06 Known bad, do not test
Zoega 2007-09-22 conf has 2 About= (should delete the first) Known bad, do not test
Webster1806 2008-06-20 none none displays well in GS, BD. Displays markup in MS Hold for 1.5.12 w/ improved TEI rendering? (may not be necessary for 1806)
Webster1913 2008-06-05 In E, for example, it says: 
See
<hi rend="italic">
  Guide to Pronunciation
</hi>,
§§ 74-97.
<lb/>

Where or what is this? front/end matter?

It probably doesn't exist in the text we have, which is derived from the MICRA database.--Osk 09:49, 16 March 2009 (UTC)

In article A:
...which was borrowed from the Greek 
<name rend="italic" type="biologicalSpecies">
<ref target="alpha">Alpha</ref></name>, 
of the same form;...

Why is this a biologicalSpecies???

The TEI is a faithful and accurate representation of the underlying text, which uses <spn> in this case to indicate species name.--Osk 09:49, 16 March 2009 (UTC) 

and this was made from the first letter (�)
of the Phœnician alphabet

The character in brackets is wrong. This occurs in C as well, and in D, F,.

The TEI is a faithful and accurate representation of the underlying text, which marks these as unknown character, hence the use of the same in Unicode.--Osk 09:49, 16 March 2009 (UTC)

In article E, lots of the text is in a footnote, which shouldn't.

The TEI is a faithful and accurate representation of the underlying text, which contains a couple of very large footnotes.--Osk 09:49, 16 March 2009 (UTC)

There seems to be an excessive amount of <hi rend="italic"> throughout.

The TEI is a faithful and accurate representation of the underlying text.--Osk 09:49, 16 March 2009 (UTC)

Senses collide with the number of the sense: 

<sense n="1">
  <num type="sense">
    1.
  </num>

Will output 11.

The TEI is a faithful and accurate representation of the underlying text. If you want the rendering to be different, modify the filter and submit a patch. The markup is correct, and this is not a module error or issue.--Osk 09:49, 16 March 2009 (UTC)

I want to clarify my position on all of these types of errors: The Webster's 1913 text is fairly well error-riddled. We can do minor text corrections, but in some sense it's pointless unless we go to the effort of searching for errors in a more systematic fashion. But I have to think that's not the best use of time considering there are other projects, such as the GCIDE, to improve (but also modernize) this text. Some of these issues, like the Phoenician letters could be corrected, but wouldn't be apparent since no one is likely to have fonts that display Phoenician. And incorrectly tagged words (as in the case of the species name "Alpha") could be corrected, but wouldn't likely have any display difference in any Sword front end. --Osk 05:11, 18 March 2009 (UTC)

With the <num type="sense"> question, I think (though I don't know about TEI, so I may be wrong) that the <num type="sense"> should be removed. I can do a patch, but I'm not sure what the correct behaviour is. Benpmorgan 06:08, 27 March 2009 (UTC)

none displays well in GS, BD. Displays markup in MS Hold for 1.5.12 w/ improved TEI rendering


Daily Devotional Modules

Module Name Updated Does the module appear complete? Encoding problems? .conf problems? Display problems on any frontend? Ready / Fix / Hold
Daily 2008-04-19 Appears structurally sound (scrolling between dates works)

Numerous scripture reference parsing errors in the source. (Fix by running through vs2osisref.)

Dates after Christmas mysteriously empty.... (They're present in the doc supplied to imp2ld though.)

Displays well in GS, BD, SW, Links do not work in MS, some links appear with markup in BibleCS

Could you provide some examples.

fix


Commentary Modules

Module Name Updated Does the module appear complete? Encoding problems? .conf problems? Display problems on any frontend? Ready / Fix / Hold
CalvinCommentaries 2008-01-01 Many, not all books from OT and NT, Conf reflects this, features - no FN found Gen 1:1 contains an XML document preamble <xml encoding="UTF-8" version="1.0"> <osis xmlns=".....
Maybe it was built with imp2mod and not osis2mod? 		Displays fine in GS, BD, MS, SW, cross reference links in BibleCS often displayed as HTML text. e.g. Mark 1:1 second last paragraph fix
Clarke 2007-10-06 Whole Bible, appears complete Displays well in GS, SW. In BD the bad encoding makes the module look very bad. fix
hold testing, update planned
TSK 2008-06-23 Seems to be missing Deut 34:12 which shows up in released TSK. This is end of book content.

Deut 34.12 has no content in TSK. Some versions repeat the text of the verse (probably from the KJV). We do not. --Osk 23:02, 7 September 2009 (UTC)

In the currently released TSK, there is this content in Deut 34:12: 

12 CONCLUDING REMARKS ON DEUTERONOMY AND THE PENTATEUCH. 
Thus ends the book of Deuteronomy, and with it the Pentateuch, 
commonly called the Law of Moses; 
a work every way worthy of God its author, and only less than 
the New Testament, the Law and Gospel of our Lord and Saviour Jesus Christ. 
Its antiquity places it at the head of all the writings in the world...

This content is not in the beta.

Philemon 1:1 has some Greek Strong's Numbers but they are linked incorrectly (directly to the STRONG module, aka: sword://STRONG/G5371 instead of a ref with action=showStrongs in it). v1.4 in the non-beta repo links these correctly. --Niccarter 03:51, 10 February 2011 (UTC)

displays well in GS. In SW only vers 1 is shown and links do not work.

Hebrew letters are not done properly (comparing with e-sword) e.g. Judg 12:6, where ת appears as ϊ and ו as ε. Another example is Nehemiah 7:61, where again it seems to have greek letters, not hebrew.

Also, it is missing the diagram (and introductory text to it) for Numbers 35:4. Is this type of schematic possible in OSIS (or just include an image)?

fix


GenBook Modules

Module Name Updated Does the module appear complete? Encoding problems? .conf problems? Display problems on any frontend? Ready / Fix / Hold
GerLutherpredigten 2008-06-07 Appears structurally sound Conf offers headings, none found Displays fine in GS, BD, BibleCS, MS, SW ready
SummaTheologica 2003-02-13 Remove?
AquinasSummaTheologica 2008-06-16 links like Bible:VUL:Gen.1.1 do not work in BD. This is a BD bug. At the same time though I think that it is inappropriate to prescribe which Bible (Vulgata) is linked to, given that this genBook is in English Refdoc
If an author cites a particular work, as Aquinas is likely to have done, this is appropriate. More significantly, since Aquinas is working from Bibles with a different reference system from Bible.NRSVA, it's important to identify that somehow so that we have the potential to do reference system translation.Osk 21:47, 28 June 2008 (MDT)

Aquinas will have quoted the Vulgata as it was the authorative translation (i.e. not as a preference, but dt lack of alternative). It is a new situation to have an abundance of translations. I do agree though with the versification being a problem. Only - it will not work right now either as even the Vulgate will be KJV versified. My long term suggestion would be to introduce (once GenBokk bibles are reality) a conf property regarding versification GenBooks could then refer to VersScheme:Book:Chapter:Verse instead of ModName:Book:Chapter:Verse - which would allow users to use a variety of applicable Bible translations with any given gen book.Refdoc 02:01, 1 July 2008 (MDT)

Add Obsoletes: SummaTheologica ? Displays fine in MS, GS SW, BibleCS. Links in BD do not work fix
EnochCharles 2009-01-23
EnochGeez 2009-01-23
EnumaElish 2009-01-23
Jasher 2009-03-24
Jub 2005-05-21 Jub 35:3 is in /Jub/35, not /Jub/35/3

Jub 38:6 is in /Jub/38

Jub 47, 48 links to exodus aren't osisref'ed

Didache 2008-11-10 Even when a proper font is selected, some text seems problematic. See /Didache/1/6, which contains:"??? σου". If this is unknown text or if there are textual variants, then a footnote should be added to let the reader know that this is not an encoding problem. Basic contents display properly in BT, GS, BibleCS, and BD after an appropriate font is selected.

Content is not valid OSIS. It has some <w> elements that are not closed. And it uses <p> as a marker, I.e. no matching </p> tag nor is the tag a <p/>.

Navigation can be a bit awkward. Didache/1 should present the reader with a title heading such as "Chapter 1" (but in Greek which I can't read). Still better, front ends should have a way to present all verses of the chapter without individual verse-navigation, which is very awkward. BT does this well, BD and BibleCS make this module painful to navigate. Navigation in GS is so-so.


Application Bugs Found During Testing

During testing pre-existing bugs may be found in an application. You should use the appropriate bugtracker and report them there, NOT HERE.

This section does not yet list all front-end applications. Add more sub-sections as and when required.

SWORD front-ends

MS

http://www.crosswire.org/bugs/browse/MACSW

  • In GenBooks: click on a leaf, then click on (About). (About) does not show. Sometimes nothing happens, other times another entry's content shows.
  • In About w/ UTF-8 characters, e.g. GerLutherpredigten, garbage is shown because it tries to interpret it as "Latin-1".
  • Does not handle WoC when milestoned quotes are used: Words of Christ

GS/Xi

http://sourceforge.net/tracker/?group_id=5528

  • Does not handle WoC when milestoned quotes are used: Words of Christ
  • Parallel references in section headings in the Gospels display as *x but do not point to the parallel text. They appear as a cross-reference to the first verse in that chapter. For an example, see Mark 1 or Luke 4 in VietNVB.
  • <lg> elements can cause an extra space to be added between the verse number and text.

BT

http://sourceforge.net/tracker/?group_id=954&atid=100954

  • <div type="section"> and <lg> elements can cause an extra space to be added between the verse number and text.

SW

http://www.crosswire.org/bugs/browse/SWEB

  • Does not handle UTF-8 in Description when listing names of modules.
  • In About w/ UTF-8 characters, e.g. GerLutherpredigten, garbage is shown because it tries to interpret it as "Latin-1".
  • In About w/ \uxxxxx? RTF codes, e.g. TurNTB, ? is shown.
    • Well, that's the expected behavior if the font lacks the encoded character (and so, not a software or a module bug but a font deficiency if anything).-Osk
  • Does not handle WoC when milestoned quotes are used and transChange is in the WoC:
    Words <transChange type="added">of</transChange> Christ
    The words following <transChange> are not highlighted.
  • Links to Bible references in Daily devotions do not work
  • Shows in commentaries only Vers 1 rather than whole chapter when asked to show a chapter - e.g. Genesis 1 - only Gen 1:1 will show up

BibleCS

http://www.crosswire.org/bugs/browse/BCS

BP

Please add bug tracker details.

JSword front-ends

BD

http://www.crosswire.org/bugs/browse/BD

  • Does not handle foot-notes in anything but Bibles.
  • Does not handle WoC when milestoned quotes are used: Words of Christ
  • links leading to a specific Bible module do not work
  • Inconsistently displays <l> elements.
  • Inconsistently displays pre-verse titles.
  • in ThML Genbooks, BD fails to display any div which includes <verse> tags
  • BD cannot generate a search index for some Bible modules. Examples: JPS, Rotherham

See also

Retrieved from "https://wiki.crosswire.org/index.php?title=Modules_in_the_beta_repository&oldid=15978"