[sword-devel] Headers in OSIS Bible & Included Additions

[gordion at o2active.cz]

Hello,




I thought all title types that I found in the osisCore.2.1.1.xsd can be used for "screen" rendering. Your note "... really makes sense in a printed book, or PDF file with pages, etc" enlighten it for me :-)




I try play with different types and subTypes of the title tag. At this moment I see no visual difference for different level of attribute values (1-4) in Xiphos :-(




Thank you




Best Regards




Ivo Dostal




-----Original
Message-----

From: David Haslam [mailto:dfhmch at googlemail.com] 

Sent: Wednesday, January 27, 2016 5:55 PM

To: sword-devel at crosswire.org

Subject: Re: [sword-devel] Headers in OSIS Bible & Included Additions
 
 
 
Dear Ivo,
 
 
 
You wrote,
 
 
 
"I have not found documentation for all these
osisTitles - acrostic, chapter, continued, ... "
 
 
 
The wiki does document how to mark
 
* major section headings (e.g. for the five books in
Psalms)
 
* chapter headings
 
* section headings
 
* acrostic headings (e.g. for Psalm 119) ...
 
 
 
There's nothing separate in OSIS for
"continued". In fact, your memo is the first mention of this.
 
 
 
btw. There's no sensible equivalent in OSIS to the USFM
running header tag \h A running header only really makes sense in a printed
book, or PDF file with pages, etc.
 
It makes less sense in the Bible software environment.
 
 
 
Also, useful to know, the JSword API supports the level
attribute in [section] titles.
 
It can display up to four different levels of title by
various means (font sizes and colors?).
 
This can be useful for marking sub-sections and
sub-sub-sections, etc.
 
 
 
As yet OSIS (and SWORD) has no special provision for the
following:
 
* chapter description
 
* chapter label
 
 
 
In OSIS, one would typically tackle the problem of
unavailable attributes by simply using a user defined one where the attribute
value has the prefix "x-"
 
 
 
CrossWire has recently started to maintain a bespoke
edited version of the OSIS schema, based on the potential change requests
documented in the wiki.
 
See
 
 
 
http://crosswire.org/wiki/OSIS_211_CR
 
 
 
We are already depending on part of this in order to
validate the source text for the KJV module.
 
 
 
Best regards,
 
 
 
David Haslam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20160129/77e30cfd/attachment.html>