Needless osis filler ....? I assume it's gone this way because modules needed conf-like influence but the (osis) standard moves too slowly? (I think I read in this list someone wondering if people were still working on it - with the recommendation Sword developers should just adopt Sword specific OSISisms).
If so, I understand the practicality, but its too bad all of the .conf stuff couldn't be contained in the module so we could do away with having to generate .conf files apart from the modules' osis (or if its a resource issue, make it so the .confs could be generated from the module itself). The fact there are .conf suggests a defect in the standard. ~A On Sun, Sep 16, 2012 at 3:28 PM, Greg Hellings <greg.helli...@gmail.com> wrote: > I'm pretty sure osis2mod simply discards all content in the header. Such > info needs to be specified in the equivalent options in the module's conf > file, if such options exist. > > On Sep 16, 2012 2:06 PM, "Andrew Thule" <thules...@gmail.com> wrote: >> >> On the issue of which language shows up in the client, English or the >> module language, it may be true that different clients have different >> default behaviours, and it''s not clear (to me) of the module can >> influence this - that said, the module's osis has at least two ways >> language is specified: >> >> <osisText osisIDWork="INK" osisRefWork="defaultReferenceScheme" >> xml:lang="iu"> >> (which I assume is for xml's sake) >> >> and in the header: >> <work osisWork="INK"> >> <title>Inuktitut Version</title> >> <identifier type="OSIS">Bible.INK</identifier> >> <date>2012-06-1</date> >> <description>Inuktitut Bible in Eastern Arctic >> Inuktitut</description> >> <language type="IETF">iu</language> >> <rights>Copyrighted. Not for distribution >> (yet)</rights> >> <refSystem>Bible.KJV</refSystem> >> </work> >> >> As far as I can tell, setting <language type="IETF">iu</language> >> doesn't influence sword clients ... but then again I haven't looked >> how osis2mod deals with the language tag either. If I gambled (and I >> don't) I'd bet few developers building non-English modules bother to >> declare the modules language by specifying <language></language>. >> >> All this to say I believe the only obligation the sword client >> developers has to worry about correctly presenting book names in >> foreign language modules is to honour the OSIS intent (according to >> tags), which means the module developers who bother specifying >> <language></language> in osis should rightly expect to influence >> client behaviour with respect to module specific presentations (module >> locales trump client locales for module presentation). Those that >> don't bother at all, are at the mercy of the default behaviour of the >> client, namely English or client locales specifications. >> >> ~A >> >> On Fri, Sep 14, 2012 at 8:13 AM, Peter von Kaehne <ref...@gmx.net> wrote: >> > Just CrossWire Main. Attic might have plenty more, but these are >> > irrelevant for the future. >> > >> > And Beta and Av11n hopefully contain none. Chris has said ages ago, he >> > will only accept OSIS bibles. And generally the standard of texts has gone >> > up over the years. >> > >> > Peter >> > -------- Original-Nachricht -------- >> >> Datum: Fri, 14 Sep 2012 04:30:35 -0700 (PDT) >> >> Von: David Haslam <dfh...@googlemail.com> >> >> An: sword-devel@crosswire.org >> >> Betreff: Re: [sword-devel] Locale differences >> > >> >> Peter, >> >> >> >> Did your survey of our modules cover all the repositories? >> >> Or just those in CrossWire Main? >> >> >> >> David >> >> >> >> >> >> >> >> -- >> >> View this message in context: >> >> >> >> http://sword-dev.350566.n4.nabble.com/Locale-differences-tp4650966p4650992.html >> >> Sent from the SWORD Dev mailing list archive at Nabble.com. >> >> >> >> _______________________________________________ >> >> sword-devel mailing list: sword-devel@crosswire.org >> >> http://www.crosswire.org/mailman/listinfo/sword-devel >> >> Instructions to unsubscribe/change your settings at above page >> > >> > _______________________________________________ >> > sword-devel mailing list: sword-devel@crosswire.org >> > http://www.crosswire.org/mailman/listinfo/sword-devel >> > Instructions to unsubscribe/change your settings at above page >> >> _______________________________________________ >> sword-devel mailing list: sword-devel@crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page > > > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
