Modules in the beta repository

From CrossWire Bible Society
Revision as of 13:26, 24 June 2011 by David Haslam (talk | contribs) (Other Bibles: '''Ready'''<ref>Rebuild module from OSIS file just submitted by Refdoc, in which all cross-reference issues have been fixed, and which includes the two new books.)

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.

Legends used in this page

Application Legends

For similar legends, see also Choosing a SWORD program.

  • BibleCS / SPW - The SWORD Project for Windows
  • MS - MacSword 1.x
  • MS2 - MacSword 2.0
  • GS - GnomeSword
  • Xi - Xiphos (formerly known as GnomeSword)
  • BD - Bible Desktop
  • BT - BibleTime[1]
  • SW - SwordWeb / BibleTool[2]
  • BP - BPBible
  • FB - FireBible
  • ABS - Alkitab Bible Study
  • SB - SwordBible
  • PS - PocketSword
  1. The BT developers have advised that BT testing is not necessary at this time.
  2. Only shows About of all modules and content of Bibles, Commentaries and Generic Books, can not show images at present.

Abbreviations Legends

  • WoC - Words-of-Christ, aka Red Letter Text
  • FN - Foot note
  • dt - due to
  • occ - occasionally
  • aka - also known as

Beta Modules

As of 2010-12-09, there are 109 modules in this repository.

When a new beta module is created, please add a row to the relevant table on this page.

When a beta module is either removed or released (moved to CrossWire main repo), please remember to edit the relevant table on this page.

Repository parameters

If the beta repository need to be declared, here are the parameters:

Site Name:              CrossWire beta
Site Machine Name:      www.crosswire.org
Repository Directory:   /pub/sword/betaraw

Bible Modules

Note: Unless stated otherwise, missing verses are based upon the KJV versification. A list of common versification systems and how they vary from the NRSVA versification can be found here.

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.
Byz 2009-11-01 hold for 1.6.1 (OSISVariants)
Vulgate_Clem 2008-07-24


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
Needs checking against a hardcopy
JST 2009-11-01
KJC 2008-06-28 NT only, conf reflects this Red letter is a complete mess!
KJV 2009-05-30 v2.4 uses milestoned chapter elements,
unlike released v2.3
Canonical Psalm titles do not display.
Psalm 119 acrostic headings misplaced.[1]
Change references from KJV2003 to KJV2006. Requires 1.6.x.
Please evaluate Psalms 3.
Hold[2][3]
Twenty 2009-01-23
  1. Observed using Xiphos 3.1.4
  2. Hold until root cause determined for module creation/encoding/display issues.
  3. Module was made using osis2mod Rev: 2421. Suggest first try rebuilding with osis2mod Rev: 2562.

French Bibles

Module Name Updated Does the module appear complete? Encoding problems? .conf problems? Display problems on any frontend? Ready / Fix / Hold
FreJND 2008-06-13 Whole Bible, appears complete

etienne>If I activate the headings, it adds the headings in the Psalms but it adds also the mention "Chapitre #" under each chapter. That's ok, but in the Epistle to the Hebrews, it displays "Psaume #" instead of "Chapitre #" ...

skc (maintainer)> Thanks etienne, I will correct this.

etienne> A little error at the end of Numbers 33. 51 (I report it here since I don't know were to report it else) : "Quand vous aurez passé le Jourdain [et que vous serez entrés] dans le paya de Canaan" this should be : "Quand vous aurez passé le Jourdain [et que vous serez entrés] dans le pays de Canaan".

features: FN and Xref work fine

skc (maintainer)> See FreJND about markup, it must probably be added in .conf, but where?

DMS: I'd suggest a textual comment in the About.

etienne>In FreJND there are three types of paragraph delimiter mentioned but I see only two used

skc> I added examples in the FreJND page

etienne> Ok, then I see the difference. It's ok for me, thanks (my comments can be removed then).

Headings in Psalms are all "canonical" and not subject to "heading" filter. If these are the only headings, should the conf still have Feature=OSISHeading?

skc> I don't know, will ask on the mailing list.

Displays fine in BD, in GS occ UTF8 problem - Mal 1:9 and Matt1:20 create odd characters (star in front of SEIGNEUR or DIEU), SW displays junk before DIEU in Mal 1:9 (looks like an engine problem handling <divineName>), MS doesn't display these verses at all, BibleCS ok.

skc> Stars are intentional, read FreJND. Other malfunctions are frontend utf-8 capitalization bugs.

etienne>Xi (previously GS) doesn't display the correct characters in front of Dieu or Seigneur. But it is ok for the stars in the Psalms. 2009-11 : I checked again an it displays correctly now with Xi 3.1.1 and BT 2.3.3 (on Ubuntu). For example see Hebrew 1.10, 10.30.


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.


Japanese Bibles

Note: these Bibles have a new feature OSIS Ruby. See [1]. Requires SWORD 1.5.12 (or later)!!!

See also http://bible.salterrae.net/en/
Module Name Updated Does the module appear complete? Encoding problems? .conf problems? Display problems on any frontend? Ready / Fix / Hold
JapBungo 2008-06-08 NT only (some missing verses) None hold for 1.6.2 testing
JapDenmo 2008-11-11 NT portions None Large amount of whitespace (new lines) around certain words like "Kingdom", "God" or "Father".[1]
JapKougo 2008-06-08 Whole Bible (some missing verses) None hold for 1.6.2 testing
JapMeiji 2008-06-08 Partial OT Note in-progress status of source. hold for 1.6.2 testing
JapRaguet 2008-06-08 NT only None hold for 1.6.2 testing
  1. See PocketSword bug report, which has been verified in MacSword as well, and includes a screen shot.

Iran Region Languages Bibles

Module Name Updated Does the module appear complete? Encoding problems? .conf problems? Display problems on any frontend? Ready / Fix / Hold
Azeri 2009-02-20 New Testament: emptyvss finds only [1] MS, Xi fine
Dari 2009-01-14 emptyvss finds [2] MS, Xi fine
FarHezarenoh 2009-02-20 New Testament: emptyvss finds [3] MS, Xi fine
FarOPV[4] 2009-01-14 emptyvss finds 19 missing verses[5] Incorrect statement about headings MS, Xi fine
FarTPV 2009-01-14 emptyvss finds [6] MS, Xi fine
  1. II Corinthians 13:14
  2. John 7:53, II Corinthians 13:14
  3. Matthew 18:11, Matthew 21:44, Matthew 23:14, Matthew 27:48-66, Mark 7:16, Mark 9:44, Mark 9:46, Mark 11:26, Mark 15:24-25,28, Mark 16:9, Acts 8:37, Acts 28:28-29, Romans 16:27, Philemon 1:1-25, Hebrews 13:7-25, II John 1:1-13, III John 1:1-14, Jude 1:1-25
  4. Supersedes FarsiOPV in the CrossWire repo., which omitted I Chronicles.
  5. Genesis 15:21, Genesis 21:34, I Samuel 8:22, II Samuel 24:25, Job 35:1, Job 40:1, Psalms 72:20, Psalms 94:23, Isaiah 45:25, Ezekiel 6:14, Ezekiel 25:5, Daniel 5:31, Matthew 2:23, Matthew 9:38, John 5:47, John 7:53, Romans 16:27, Philippians 1:30, I John 3:24
  6. Leviticus 4:30, I Chronicles 27:17-21, Isaiah 2:21-22, Jeremiah 19:2-15, Jeremiah 20:2-18, II Corinthians 13:14.

Other Bibles

Module Name Updated Does the module appear complete? Encoding problems? .conf problems? Display problems on any frontend? Ready / Fix / Hold
AraSVD 2008-07-21 Whole Bible none Displays nice in GS, BD, SW, MS, BibleCS
GreVamvas 2008-07-23
Latvian 2008-07-23 NT only, conf reflects this
None Cross refs cannot display in BibleCS.
PolUGdanska 2009-08-24 NT only, conf reflects this Matt 1:1 missing
Footnotes & cross-refs missing
Colophons?
Not valid xml, as it uses MS Word 'smart quotes' for attribute values.
None Displays OK in BD, BP, BibleCS Rebuild from MS Word source
TurNTB 2007-08-21 Whole Bible, many empty verses dt linkage Obadja missing plenty crossreferences in plain text e.g. Lev 1:1, verse ranges poorly encoded - empty verses, e.g Zeph 1:4-6 About contains several Unicode characters that are not properly encoded.[1] Displays fine in GS, BD, MS, BibleCS, SW Hold reimport after location of missing text and osismod update [2]
WelBeiblNet 2009-02-14 Colloquial Welsh New Testament
Arfon Jones' translation beibl.net[3]
There are major issues with cross-references. Ready[4]
  1. About=New Turkish Bible translation, jointly translated and published by K\u00305?tab\u00305? Mukaddes \u00350?irketler (www.kitabimukaddes.com) and Yeni Ya\u00351?am Yay\u00305?nlar\u00305? (www.yyyayinlari.com). We are grateful for the permission by Yeni Ya\u00351?am Yay\u00305?nlar\u00305? to distribute this translation.
  2. Better still, negotiate with the Translation Trust to distribute the complete Turkish Bible, and replace this NT only module.
  3. Psalms & Proverbs have since been translated.
  4. Rebuild module from OSIS file just submitted by Refdoc, in which all cross-reference issues have been fixed, and which includes the two new books. The new edition of the module should be moved to CrossWire Main.

WBTI & BL Bibles

  • WBTI denotes Wycliffe Bible Translators International
  • BL denotes Bible League

Global Problems:
These Bibles are likely to have the same set of problems. If you find an error that pertains to more than one, please briefly note it below and provide details with references here:
Wycliffe Bible Discussion

Note:

Most of these modules are for languages in the Americas, for which there is now much more up to date information indexed at http://www.scriptureearth.org/
Module Name Updated Does the module appear complete? Encoding problems? .conf problems? Display problems on any frontend? Ready / Fix / Hold
amu_BL_1999 2008-07-02 Global header note problem (see above). Dislays fine in SW. Not in BD.
cco_BL_2002 2008-07-02 Global header note problem (see above). Displays fine in SW
chd_BL_1991 2008-07-02 Displays fine in SW
chq_BL_1983 2008-07-02 Unicode 5.1 font needed? Displays fine in SW
chz_BL_2003 2008-07-02 Unicode 5.1 font needed? Displays fine in SW
ckw_WBTI_1996 2008-07-02 Displays fine in SW
cnl_BL_1994 2008-07-02 Global header note problem (see above). Displays fine in SW
cnt_BL_1994 2008-07-02 Global header note problem (see above). Needs Unicode 5.1 font? Displays fine in SW
cti_BL_1976 2008-07-02 Variation of global header note problem. The reference precedes Matt 5:20 verse number and the heading is indented after as if it were not a heading. Displays fine in SW
ctp_BL_1992 2008-07-02 Displays fine in SW
dug_WBTI_1999 2008-07-02 Global header note problem (see above). Displays fine in SW
huv_BL_1996 2008-07-02 Global header note problem (see above). Displays fine in SW
ixl_WBTI_2001 2008-07-02 Displays fine in SW
jac_WBTI_1997 2008-07-02 Global header note problem (see above). Displays fine in SW
jvn_BL_1999 2008-07-02 Displays fine in SW
kek_WBTI_2000 2008-07-02 Displays fine in SW
lac_BL_1978 2008-07-02 Global header note problem (see above). Displays fine in SW.
mir_BL_1988 2008-07-02 Incomplete? Using SW, a spot check of three arbitrary chapters shows empty verses. See Matt 5, v15,16,30,35,36 are missing. Jas 1, v8,11 missing. Rom 8, v4,8 missing.

Those are all linked verses. (Matt.5.14, Matt.5.15, Matt.5.16 are a single block, where the latter two link to the entry of the first.) Nonetheless, emptyvss is reporting numerous genuinely empty (and unlinked) verses that should have some linking, according to the OSIS source. There might be some sort of importer problem here. (But there is no missing text that I can see.)


There are 2 bugs in osis2mod: linking is not working and appended, interverse material is replacing a link.

hold for osis2mod fix Displays fine in SW
miz_BL_2003 2008-07-02 Global header note problem (see above). Displays fine in SW
mks_BL_1999 2008-07-02 Global header note problem (see above). Displays fine in SW
mvc_WBTI_2002 2008-07-02 Global header note problem (see above). Displays fine in SW.
mvj_WBTI_2000 2008-07-02 Global header note problem (see above). Displays fine in SW.
mxq_BL_2004 2008-07-02 Displays fine in SW
ncl_BL_1998 2008-07-02 Global header note problem (see above). Displays fine in SW
ngu_BL_1987 2008-07-02 Global header note problem (see above). Displays fine in SW
nhy_BL_2006 2008-07-02 Global header note problem (see above). Displays fine in SW
otq_BL_2003 2008-07-02 Global header note problem (see above). Displays fine in SW
qut_WBTI_1997 2008-07-02 Displays fine in SW
cso_BL_1986[1] 2008-07-02 Global header note problem (see above). Needs Unicode 5.1 font? Displays fine in SW
ttc_WBTI_2003 2008-07-02 Global header note problem (see above). Displays fine in SW
tzz_BL_1987 2008-07-02 Global header note problem (see above). Displays fine in SW
usp_WBTI_1999 2008-07-02 Displays fine in SW
mxt_BL_1983[2] 2008-07-02 Global header note problem (see above). Displays fine in SW
xtd_BL_2001 2008-07-02 Displays fine in SW
zab_BL_1995 2008-07-02 Empty note markers stand before verse numbers. (See Matt 5)
zaw_BL_2006 2008-07-02 Global header note problem (see above). Displays fine in SW
zpo_BL_2002 2008-07-02 Global header note problem (see above). Displays fine in SW
zpq_BL_1987 2008-07-02 Global header note problem (see above). In SW, Matt 5:32, the note is split oddly, as if part of it is attached to the prior verse.
zpu_BL_2000 2008-07-02 Global header note problem (see above). Displays fine in SW
zpv_BL_1990 2008-07-02 Global header note problem (see above). Displays fine in SW
zsr_BL_1992 2008-07-02 Displays fine in SW
ztq_BL_2000 2008-07-02 Global header note problem (see above). Displays fine in SW
zty_BL_2002 2008-07-02 Global header note problem (see above). Displays fine in SW
  1. Renamed; was sco_BL_1986
  2. Renamed; was xmt_BL_1983

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
ISBE 2009-09-07
Nave 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
FVDPVietAnh 2008-06-13
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.

needs fixing


Commentary Modules

Module Name Updated Does the module appear complete? Encoding problems? .conf problems? Display problems on any frontend? Ready / Fix / Hold
Barnes 2008-01-01 Gen 1.1 entry is not UTF-8 (quotes, nbsp), perhaps elsewhere

Isaiah 52:13,14,15 have a bad title.
Daniel 7:28, 9:25, Rev 9:21 is using <p> as a paragraph break. I.e. there is no matching </p>. Here and there, <hi type="b">, which is not valid OSIS.
Obviously, this was not validated against the OSIS schema.

In BD and GS the bad encoding makes the module look very bad. in SW some characters do not display (? quotation marks) e.g James 2:1 2nd paragraph needs fixing
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 needs fixing
Clarke 2007-10-06 Whole Bible, appears complete Displays well in GS, SW. In BD the bad encoding makes the module look very bad. needs fixing
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)?

needs fixing
OTPassages 2008-06-23 displays well in BD, GS. In SW only vers 1 is shown.


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 needs fixing
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.


Map Modules

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


Application Bugs Found During Testing

During testing pre-existing bugs may be found in an application. In general, you should use the appropriate bugtracker and report them there.

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 / SPW

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