Talk:OSIS Bibles

From CrossWire Bible Society
Revision as of 22:23, 14 August 2009 by Osk (Talk | contribs) (Display outside <verse>)

Jump to: navigation, search

Display outside <verse>

Dowens just added the following comment: "Also, a quirk of the SWORD compilation process is that the only kind of content which reliably displays outside of <verse> elements are titles."

If this was the case, it may no longer be the case for osis2mod. I'm not familiar with a specific instance where this has been a problem, since I believe we maintain everything except <verse> elements themselves. That being said, if there is an issue, my guess would be that it is a frontend and/or filter issue--not an issue with the compilation process. Probably this needs some more investigation (and for bugs to be filed as appropriate). --Osk 00:50, 29 November 2008 (UTC)

Late response. Osis2mod takes all interverse material and either appends it to the prior verse or puts it into a x-preverse title. In doing this, it re-arranges the tags if needed. I am working on the implementation of a <div subType="x-preverse" sID="xxx"/>...<div subType="x-preverse" eID="xxx"/> to replace it. I hope to be done within the next week.--Dmsmith 11:33, 24 April 2009 (UTC)
If this was implemented, please update the main page to describe the syntax. David Haslam 19:33, 23 July 2009 (UTC)
Please document the correct method to tag the sentence after the "Amen." at the end of each Pauline epistle. This is post-verse content, describing where each epistle was written, etc. Not all Bible translations include these attributions, but the KJV does. For convenience, here is a list of such verses:
Romans 16:27
1 Corinthians 16:24
2 Corinthians 13:14
Galatians 6:18
Ephesians 6:24
Philippians 4:23
Colossians 4:18
1 Thessalonians 5:28
2 Thessalonians 3:18
1 Timothy 6:21
2 Timothy 4:22
Titus 3:15
Philemon 25
Hebrews 13:25
For use with BD, this list can be pasted into a text file and saved as
%Application Data%\JSword\bookmarks\Last verse of every Pauline epistle.lst 

David Haslam 20:00, 14 August 2009 (UTC)

For colophons, use <div type="colophon">....</div>. --Osk 22:22, 14 August 2009 (UTC)

Milestoned version of <chapter>

The section about milestones states, "There are a couple of instances where the milestoned version of <chapter> must be used. eg: when the paragraph is spanning over a chapter." IMHO, it would be helpful to cite both such instances, and give examples of Bible versions where this occurs. David Haslam 12:15, 22 April 2009 (UTC)

I gave the example of the Sermon on the Mount having a quote that spans several chapters. Osk removed it. One can naturally start the quote in chapter 5 and artificially end it at the end of 5, only to artificially start at the beginning of chapter 6 and also artificially end it at the end of the same chapter and thus to artificially start it at the beginning of chapter 7 and finally ending it at the natural place in chapter 7. This is unnecessary and current osis2mod does not require it. Just have the start quote in Matt 5 and the end in Matt 7, using milestoned chapters in between. Once milestoned chapters are used anywhere, OSIS "requires" that they are used everywhere. If quotes are not marked up, then this example, of course, does not pertain.--Dmsmith 01:18, 24 April 2009 (UTC)

I take that back. One can have a milestoned quote start in chapter 5 and a matching milestoned end in chapter 7. This was Osk's comment in removing it. Even chapter spanning paragraphs are not a necessary requirement for milestoned chapters. There is a milestoned version of the paragraph: <div type="paragraph" sID="xxx"/> ... <div type="paragraph" eID="xxx"/>. I was hesitant to mention this, but now SWORD supports this and osis2mod uses it instead of it's proprietary <lb> hack.--Dmsmith 11:15, 24 April 2009 (UTC)
Regarding milestoned paragraphs: Not quite.... There are a few instances of of unfortunate homonymy in OSIS. I think that the difference between <chapter> and <div type="chapter"> is fairly well understood. The former is meant for Bible chapters and the latter for any other type of chapter in any other type of book. Similarly <p> and <div type="paragraph"> have different meanings. A <p> is the normal sense of paragraph (a block of one or more sentences without any linebreaks, probably relating to a single topic). A <div type="paragraph"> is a text division equivalent to a section, sub-section, or chapter. It could very well contain one or more <p> elements. Or it might start with a <title> followed by <p>s or other <div>s for sub-paragraphs. It was specifically intended for documents that have "paragraphs" as a named division type. Law texts would be one example of a text using paragraphs in this sense. I believe the Catechism of the Catholic Church also uses paragraphs in this sense. So <p> really wasn't intended ever to be milestoned. --Osk 18:46, 24 April 2009 (UTC)
It is not at all clear to me in the OSIS manual that <chapter> and <div type="chapter"> have any semantic difference. In the manual it defines the div type of chapter:
chapter - Standard chapter as is found in a textbook.
To me, I always saw the chapters of a book of the Bible as equivalent to that of a textbook.
Likewise for paragraph:
paragraph - Should be used only where the paragraphs in question do not correspond to normal use of the p element of OSIS.
If the text is marked up with BCV, then the "normal use" of the p element does not work. So, I see it as an appropriate transformation inside a module or as a way of marking paragraphs that span chapters. The filters now support this mechanism in a fashion similar to paragraphs, using line breaks. I hope this is appropriate for the proper semantic usage you described, which allows for nested paragraphing.
Small comment on my removal of your <q> content from the article: I don't disagree that this is a good case for using milestoned chapters. That's quite possibly a better way to encode the Sermon on the Mount. But the text of the article, as worded, specifies instances where "milestoned version of <chapter> must be used" (emphasis mine), which this isn't. --Osk 18:29, 24 April 2009 (UTC)