Difference between revisions of "Talk:OSIS 211 CR"

From CrossWire Bible Society
Jump to: navigation, search
(The element and poetry markup?: new section)
(The element and poetry markup?: :The <speaker> element was converted from the USFM tag '''\sp_text''' which is described as Speaker Identification (e.g. Job and Song of Songs). It's listed under)
Line 32: Line 32:
  
 
What's the recommended solution or hack? Is a change to OSIS required to facilitate this use? [[User:David Haslam|David Haslam]] 13:59, 2 January 2015 (MST)
 
What's the recommended solution or hack? Is a change to OSIS required to facilitate this use? [[User:David Haslam|David Haslam]] 13:59, 2 January 2015 (MST)
 +
 +
:The <speaker> element was converted from the USFM tag '''\sp_text''' which is described as Speaker Identification (e.g. Job and Song of Songs). It's listed under Titles, Headings and Labels in the USFM Reference. Surely this implies that when this tag is encountered, it should first terminate any existing poetry line group? After all, a title is not part of the poetry in any normal sense. [[User:David Haslam|David Haslam]] 01:58, 3 January 2015 (MST)

Revision as of 08:58, 3 January 2015

Introduction

Chris, please add an introductory description to the top of this page. David Haslam 17:56, 12 December 2010 (UTC)

Done - based on Troy's post in the Google group for Open Scriptures. David Haslam 08:11, 4 August 2011 (MDT)

New Features

Troy outlined a couple new features to handle OSIS fragments: https://groups.google.com/d/msg/openscriptures/kygOM0yPHL8/3232AYNQsSIJ Including:

  • Shadow/virtual elements
  • Remotely referenceable header

David Troidl also had a list of suggestions: https://groups.google.com/d/topic/openscriptures/1lyqiBSUCh8/discussion

--Westonruter 00:23, 10 August 2011 (MDT)

Next SBL meeting?

The SBL meeting mentioned in the opening paragraph is now past. When is the next meeting/opportunity to review OSIS improvements? David Haslam 05:30, 20 October 2012 (MDT)

Corrections to the OSIS Reference Manual

Maybe we should include a separate section to address Corrections to the OSIS Reference Manual? David Haslam 05:37, 20 October 2012 (MDT)

Don't get mixed up

As the OSIS element is called divineName and the USFM equivalent is called Name of Deity, this observation is recorded to serve as a caution against getting abbreviations mixed up when referring to either in emails, etc. (cf. the USFM tag par is \nd_...\nd* ) David Haslam 07:39, 22 February 2014 (MST)

The <speaker> element and poetry markup?

The line group element <lg> does not allow the <speaker> element unless it's within a line element <l>.
I've recently come across OSIS lines generated by usfm2osis.py where the <speaker> element occurred directly within <lg>.

What's the recommended solution or hack? Is a change to OSIS required to facilitate this use? David Haslam 13:59, 2 January 2015 (MST)

The <speaker> element was converted from the USFM tag \sp_text which is described as Speaker Identification (e.g. Job and Song of Songs). It's listed under Titles, Headings and Labels in the USFM Reference. Surely this implies that when this tag is encountered, it should first terminate any existing poetry line group? After all, a title is not part of the poetry in any normal sense. David Haslam 01:58, 3 January 2015 (MST)