Hey, this is great to hear, thank you!
if you want to have a look at what I put together: https://gitorious.org/offene-bibel-converter/osis-showcase-module It contains a bible and a commentary. A module is created with make.sh. When compiled to a sword module several issues show up though, as I have already said. @Troy: Your mail Daniel replied to did not make it to my inbox. Where did you send that mail to? Patrick On Thursday, 1. March 2012 21:38:51 Daniel Owens wrote: > Hmmm, that sounds like a tantalizing assignment, that is, if developers > pay attention. :) > > Such a document would need to have excerpts from various parts of the > Bible, including especially the Psalms and the Gospels since between > them several of the odd markup issues show up. If someone were to > generate that, module developers would rise up and call us blessed only > if the markup was rendered as expected. > > I may take a stab at it. > > Daniel > > On 03/01/2012 02:18 PM, Troy A. Griffitts wrote: > > Patrick, > > > > Well, the KJV2003 project would have been my idea fore best practices > > markup for OSIS, but it now lives at the KJV2006 and I would guess now > > represents DM's idea of best practices for OSIS markup :) > > > > The tutorials also were meant to iterate the most used features of > > OSIS to give an example of best practice markup for that feature. We > > should include a link to a concise, representative, validating OSIS > > document which includes all of these features. > > > > Anyone up for the task? > > > > Troy > > > > On 02/29/2012 07:23 PM, Patrick Zimmermann wrote: > >> On Wednesday, 29. February 2012 15:29:31 Troy A. Griffitts wrote: > >>> On 02/29/2012 01:21 PM, Peter von Kaehne wrote: > >>>> Ok, > >>>> > >>>> Just my 2p to the matter: > >>>> > >>>> There are several versions of osis2mod about which produce different > >>>> results. > >>>> > >>>> I learned the hard way that other than by adding x-preverse to most > >>>> titles etc things do NOT work. > >>> > >>> Dear Peter, > >>> > >>> If you ever find that you need to manually add x-preverse to your OSIS > >>> text before importing then a bug should be raised either here or in > >>> jira > >>> about what standard OSIS markup doesn't get imported correctly via > >>> osis2mod. > >>> > >>> I realize often you just need to get something to work quickly, but > >>> this > >>> doesn't help us solve the core problem moving forward. > >>> > >>> The clear specification is OSIS. You should never need to add any > >>> custom tags to your document. Again, that's the goal in a perfect > >>> world. I believe we have somewhere a 'best practices' document for > >>> OSIS > >>> markup which is know to work with osis2mod. > >> > >> Hello Troy, > >> > >> Do you know where that 'best practices' document is? I have been eagerly > >> searching for one in vain some time ago. I thus started my own > >> showcase OSIS > >> module which produces terrible output for much of the syntax it tries > >> to show. > >> If there is such a document already, I can gladly throw my miserable > >> approach > >> away. > >> > >> Patrick > >> > >>> We have about 5 OSIS > >>> tutorials floating around and I'm not sure what state they are all in, > >>> but they should probably be clean up to give you what you ask for > >>> below, > >>> 'a clear specification to work to'. > >>> > >>> http://crosswire.org/osis/tutor.jsp > >>> http://crosswire.org/wiki/OSIS_Tutorial > >>> http://crosswire.org/wiki/OSIS_Bibles > >>> http://crosswire.org/wiki/OSIS_Commentaries > >>> http://crosswire.org/wiki/OSIS_Genbooks > >>> > >>> > >>> Troy > >>> > >>>> But recently things have become more broken and it has become a > >>>> mess to > >>>> figure out. > >>>> > >>>> It is not all engine as modules produced in different times have > >>>> different level of "properness". > >>>> > >>>> It would be great if we as module makers had a clear specification to > >>>> work to - whatever that is - and then could dump the module into > >>>> osis2mod and get a working module. > >>>> > >>>> At the moment we do not. > >>>> > >>>> Peter > >>>> > >>>> -------- Original-Nachricht -------- > >>>> > >>>>> Datum: Wed, 29 Feb 2012 12:39:19 +0100 > >>>>> Von: "Troy A. Griffitts"<scr...@crosswire.org> > >>>>> An: SWORD Developers\' Collaboration Forum<sword-devel@crosswire.org> > >>>>> Betreff: Re: [sword-devel] preverse divs > >>>>> > >>>>> I don't know what's wrong except what I noted in the previous > >>>>> post: that > >>>>> there is something wrong. > >>>>> > >>>>> I want to clear up one thing that seems to be a general > >>>>> misunderstanding: > >>>>> > >>>>> Module makers should never care or know about x-preverse. > >>>>> They should make their module how they think best conforms to the > >>>>> OSIS > >>>>> specification. > >>>>> osis2mod will add the x-preverse div to the section it things > >>>>> should be > >>>>> associated with a verse but display before the verse marker. > >>>>> > >>>>> .... in a perfect world anyway. That's the goal, at least, and > >>>>> depending on who's reverted whom's revert, it might work that way > >>>>> now. > >>>>> > >>>>> On 02/29/2012 11:09 AM, David Haslam wrote: > >>>>>> Hi Troy, > >>>>>> > >>>>>> I just tried wrapping the first "section title" for Matt.1.1 as > >>>>>> follows: > >>>>>> > >>>>>> <div type="section"> > >>>>>> <div type="x-milestone" subType="x-preverse" sID="pv1"/> > >>>>>> <title>Lignez Jezuz</title> > >>>>>> <div type="x-milestone" subType="x-preverse" eID="pv1"/> > >>>>>> <verse sID="Matt.1.1" osisID="Matt.1.1"/> > >>>>>> Levr lignez Jezuz-Krist, Mab David, Mab Abraham. > >>>>>> <verse eID="Matt.1.1"/> > >>>>>> > >>>>>> After rebuilding the module, the title "Lignez Jezuz" had > >>>>>> disappeared > >>>>> > >>>>> when > >>>>> > >>>>>> viewed with *Xiphos 3.1.5* (in Windows). In its place there > >>>>>> seemed to > >>>>> > >>>>> be an > >>>>> > >>>>>> extra space. > >>>>>> > >>>>>> It was there before, albeit displayed after the verse tag. > >>>>>> > >>>>>> So what's wrong? > >>>>>> > >>>>>> cf. In *BibleDesktop 1.6*, the same title is still displayed, and > >>>>>> still > >>>>>> after the verse tag and a line break. > >>>>>> > >>>>>> The phrase "not yet supported" seems to be a considerable > >>>>> > >>>>> understatement. > >>>>> > >>>>>> Regards, > >>>>>> > >>>>>> David > >>>>> > >>>>>> View this message in context: > >>>>> http://sword-dev.350566.n4.nabble.com/preverse-divs-tp4429131p4431114 > >>>>> .ht > >>>>> > >>>>> ml > >>>>> > >>>>>> 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 > > _______________________________________________ > 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
