Chris, Thanks for the comprehensive response. That's cleared up the last issue for me, I hope.
The publisher is not keen on removing books to produce a 66 book edition, so I cannot pursue that option. I'll use the italics sub-type that you suggested previously for deuterocanonical content. This will allow both the LXX individual verses as well as whole books to be identified (at least in the OSIS file for those who look there). (A project in progress is to produce a Protestant printed version of An BĂobla Naofa, but my discussion with the publisher revealed that this will only include something along the lines of just a different foreword regarding what is canonical/deuterocanonical and how Catholics and Protestants treat them differently.) When I've got this all done, and error-checked against the original files to ensure that no text has been deleted/added etc, I'll try it out on BibleCS, although that could be a week or so from now. John Duffy -----Original Message----- From: Chris Little [mailto:chris...@crosswire.org] Sent: 08 October 2009 03:12 To: johndu...@cgcf.net; SWORD Developers' Collaboration Forum Subject: Re: [sword-devel] Help wanted on non-canonical text I see some technical and practical problems with this suggestion. johndu...@cgcf.net wrote: > Chris, > > In Bibledit the deuterocanonical markers \dc_ ... \dc* outputs to OSIS such > as: > <reference type="added" edition="dc">Mar leanas a ghabh an litir: > </reference> Simply from the perspective of conformant OSIS, "added" isn't a possible value of reference's type attribute, so this wouldn't validate. More importantly, none of this OSIS markup is being used correctly. USFM's \dc_...\dc* tags do mark off a segment of deutero-canonical text for the purpose of exlusion from particular editions. OSIS's <reference> element is for marking references to parts of a text (the same text or another text). The most common use would be to use <reference> to surround a Bible reference, e.g. <reference osisRef="Gen.1.1">Genesis i, 1</reference>. I would recommend that, if you want to mark particular books/chapters as canonical according to various editions, you place some kind of tag within the editions attribute of each book (or chapter for those books that have chapters of differing canonicity). Using c as a token for Catholic canon and p as a token for Protestant canon, if a book is accepted as canonical by both Catholics and Protestants, you might have: <div type="book" osisRef="Gen" editions="c p"> for a Catholic-only book: <div type="book" osisRef="Gen" editions="c"> > It would seem good to use this so that frontends could potentially switch on > or off the deuterocanonical/LXX content as desired, if the program allowed > this. Neither any front ends nor Sword itself could support this. In order to allow them to support this, editions would have to be marked on every single verse and we'd have to move to a system in which the verse element is retained by osis2mod (which I believe Troy still opposes). This would itself leave a blank verse for every deuterocanonical verse, since every verse would still be a part of the text, it's contents would simply be masked. A better solution would probably be to simply issue two editions of the text if there are really communities that don't use and would be offended by the deuterocanonical text. One edition can use a versification such as NRSVA and another the NRSV v11n. > I don't think I can display a mod in KJVA v11n yet using a frontend, so I > can't check out if dc content will display as such. Do you know if the > latest osis2mod will handle this reference type? Admittedly I haven't tried yet, but the BibleCS that Troy posted should work fine with the KJVA. Assuming he compiled with the latest SVN of Sword, it would even support the Bibles using the Synodal v11n. --Chris _______________________________________________ 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