Difference between revisions of "Modules in the beta repository"

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

See Talk:Modules_in_the_beta_repository#ABU for a discussion.

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.

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.

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)

...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)

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.)

Could you provide some examples.

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)

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)?

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)

Jub 38:6 is in /Jub/38

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

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