Difference between revisions of "Talk:Osis2mod"

From CrossWire Bible Society
Jump to: navigation, search
m
(OSIS Dictionaries?: :::Aside: There's even a [http://www.tei-c.org/Guidelines/Customization/Lite/ TEI Lite]. ~~~~)
 
(6 intermediate revisions by 2 users not shown)
Line 25: Line 25:
 
Has there been a change in osis2mod that accompanied the release of SWORD 1.7.2 ? [[User:David Haslam|David Haslam]] 02:26, 21 January 2014 (MST)
 
Has there been a change in osis2mod that accompanied the release of SWORD 1.7.2 ? [[User:David Haslam|David Haslam]] 02:26, 21 January 2014 (MST)
 
: No. 1.7.2 was before this change. 1.7.x is a separately managed branch of trunk. It is a bug-fix release branch. As people make changes to trunk, they are evaluated for inclusion into the branch. --[[User:Dmsmith|Dmsmith]] 06:23, 21 January 2014 (MST)
 
: No. 1.7.2 was before this change. 1.7.x is a separately managed branch of trunk. It is a bug-fix release branch. As people make changes to trunk, they are evaluated for inclusion into the branch. --[[User:Dmsmith|Dmsmith]] 06:23, 21 January 2014 (MST)
 +
: This change breaks SWORD lib osishtmlhref and osisxhtml. See API-162 in Jira.--[[User:Dmsmith|Dmsmith]] 07:22, 21 January 2014 (MST)
 +
 +
== Default versification? ==
 +
 +
It appears that the default v11n was changed recently (in rev 3314) but without any official announcement. The syntax help still shows the default as KJV. Users beware! [[User:David Haslam|David Haslam]] 13:30, 5 September 2015 (MDT)
 +
:A discussion thread was started today by Michael H in the sword-devel mailing list. [[User:David Haslam|David Haslam]] 13:31, 5 September 2015 (MDT)
 +
 +
== OSIS Dictionaries? ==
 +
 +
I understand that the dictionary modules hosted in the '''IBT''' repository were made from OSIS XML source text rather than TEI XML source text. Would I be correct in assuming that '''osis2mod''' was used to build these modules? [[User:David Haslam|David Haslam]] ([[User talk:David Haslam|talk]]) 03:11, 10 March 2017 (MST)
 +
:They must have used their own utility, as osis2mod cannot produce anything other than VerseKey modules.
 +
:Aren't TEI and OSIS coming together on the issue of dictionary markup, though?
 +
:Is there a significant difference between TEI and OSIS for dictionaries?  [[User:David Haslam|David Haslam]] ([[User talk:David Haslam|talk]]) 15:13, 10 March 2017 (MST)
 +
::[https://github.com/JohnAustinDev/osis-converters osis-converters] uses OSIS converted to TEI using the xslt at [https://github.com/refdoc/Module-tools/blob/master/bin/osis2tei.xsl here]. TEI is really a sort of "do anything" specification whose key-entry markup is used to house SWORD's OSIS markup. So TEI offers the structure, but the Bible related markup is still OSIS. [[User:David Haslam|David Haslam]] ([[User talk:David Haslam|talk]]) 03:14, 11 March 2017 (MST)
 +
:::Aside: There's even a [http://www.tei-c.org/Guidelines/Customization/Lite/ TEI Lite]. [[User:David Haslam|David Haslam]] ([[User talk:David Haslam|talk]]) 03:17, 11 March 2017 (MST)

Latest revision as of 10:17, 11 March 2017

History of changes ?

Have there been any significant changes to osis2mod since 2009-06-06? If so, please update this section of the main page. David Haslam 19:56, 7 November 2010 (UTC)

Still waiting! David Haslam 06:21, 13 November 2011 (MST)
It hasn't changed since then until yesterday. I still have a few more reported problems to look at. After these, I'll update the page:
  • ZText modules don't write the last bits to the module.
  • OSIS header text appearing in the module.
  • cipher might not be working
  • large text causes the program to crash (e.g. when used to build a commentary)
--Dmsmith 19:02, 13 November 2011 (MST)

What changes have been made since the last one (2012-03-24 r2693) documented in the main page?

cf. I'm using the Windows x64 versions of r2778 compiled (2013-01-28) by Greg. David Haslam 12:26, 17 May 2013 (MDT)

Contained???

The following item on the main page seems to be incorrectly worded.

InterVerse Content refers to all content not contained by the verse element.

In the milestone form of OSIS, verse elements are not containers! So using the verb "contained by" is confusing! David Haslam 12:00, 17 May 2013 (MDT)

I was very aware that the milestoned version of a verse element is not a physical container. But it is a logical container. The same issue holds true regarding all talk of begin and end elements, when dividing interverse material. I don't want to see the page be very complicated in its wording. If you can make it clearer, please do.--Dmsmith 12:06, 17 May 2013 (MDT)

SWORD version 1.7.2

Has there been a change in osis2mod that accompanied the release of SWORD 1.7.2 ? David Haslam 02:26, 21 January 2014 (MST)

No. 1.7.2 was before this change. 1.7.x is a separately managed branch of trunk. It is a bug-fix release branch. As people make changes to trunk, they are evaluated for inclusion into the branch. --Dmsmith 06:23, 21 January 2014 (MST)
This change breaks SWORD lib osishtmlhref and osisxhtml. See API-162 in Jira.--Dmsmith 07:22, 21 January 2014 (MST)

Default versification?

It appears that the default v11n was changed recently (in rev 3314) but without any official announcement. The syntax help still shows the default as KJV. Users beware! David Haslam 13:30, 5 September 2015 (MDT)

A discussion thread was started today by Michael H in the sword-devel mailing list. David Haslam 13:31, 5 September 2015 (MDT)

OSIS Dictionaries?

I understand that the dictionary modules hosted in the IBT repository were made from OSIS XML source text rather than TEI XML source text. Would I be correct in assuming that osis2mod was used to build these modules? David Haslam (talk) 03:11, 10 March 2017 (MST)

They must have used their own utility, as osis2mod cannot produce anything other than VerseKey modules.
Aren't TEI and OSIS coming together on the issue of dictionary markup, though?
Is there a significant difference between TEI and OSIS for dictionaries? David Haslam (talk) 15:13, 10 March 2017 (MST)
osis-converters uses OSIS converted to TEI using the xslt at here. TEI is really a sort of "do anything" specification whose key-entry markup is used to house SWORD's OSIS markup. So TEI offers the structure, but the Bible related markup is still OSIS. David Haslam (talk) 03:14, 11 March 2017 (MST)
Aside: There's even a TEI Lite. David Haslam (talk) 03:17, 11 March 2017 (MST)