Thanks to everyone for responding earnestly to this.
Daniel
On 03/04/2012 08:07 PM, Troy A. Griffitts wrote:
> OK Guys,
>> I spent a little time on this tonight.
>> I've reworked OSISHeadings to be sane. It was an old filter and
> parsed everything manually; it had never been updated to extend and
> take advantage of SWBasicFilter. It is much shorter and fairly well
> commented now. I'm not promising it works, but it should be readable
> by anyone who wants to tweak it.
>> In fact, I may have broken everything :) So please test. Or it may
> just work for both old style and new style preverse chunks-- that was
> my goal.
>> Karl, I tried it on the new KJV and got stuff out from RenderText.
>> Daniel, it outputs stuff from your OSIS Reference module. I'm not
> sure it's the right stuff :)
>> I started an OSIS test in our testsuite. It starts by creating a
> module from our new OSIS Reference document and then proceeds to run a
> single test to check if RenderText will output something from the
> preverse div in Ps.3.1.
>> Hope this is a good start.
>> Troy
>>>>>> On 03/05/2012 02:33 AM, DM Smith wrote:
>> Some really weird stuff going on here in the nightly build of BD. I
>> found Gen 1 in Matt 1, Mark 1 in Genesis chapter 36. Looked through
>> the entire module and didn't find Psalms.
>>>> Looks like JSword nightly flipped the two testaments.
>>>> I have something to look forward to this week.
>>>> -- DM
>>>> On Mar 4, 2012, at 6:15 PM, Daniel Owens wrote:
>>>>> That is wonderful news. I have not been updating to the nightly
>>> build for awhile, so I downloaded the latest, but the test module
>>> does not display at all. I am not sure what to make of that, but it
>>> is a rather unorthodox module in that it only has a little bit of
>>> content.
>>>>>> Daniel
>>>>>> On 03/04/2012 04:32 PM, DM Smith wrote:
>>>> The next release of Bible Desktop supports/displays book and
>>>> chapter introductions. It is available now as a nightly build. How
>>>> well the nightly build works on any given day is possibly broken.
>>>>>>>> AndBible will probably support it once JSword is released.
>>>>>>>> -- DM
>>>>>>>> On Mar 4, 2012, at 4:08 PM, Daniel Owens wrote:
>>>>>>>>> I did some testing of several of the major front-ends (sorry, I do
>>>>> not have a Mac or iPhone). I posted the results at
>>>>>http://www.crosswire.org/wiki/OSIS_Bibles/BSPExample#Level_of_Support_by_Front-ends.>>>>>>>>>> Overall feature support is strongest in BPBible, followed by
>>>>> BibleTime and Xiphos tied for second. Then comes BibleCS,
>>>>> BibleDesktop, and AndBible.
>>>>>>>>>> That can partly be explained by the fact that BibleDesktop and
>>>>> AndBible do not display book introductions (that is a reasonable
>>>>> choice for AndBible). However, both support parallel titles (for
>>>>> synoptic passages in the Gospels) and canonical psalm titles (as
>>>>> does BPBible). But BibleTime, Xiphos, and BibleCS simply do not
>>>>> display the text of Canonical psalm titles. That is a severe bug.
>>>>>>>>>> As a novice module creator several years ago, this diversity
>>>>> almost drove me crazy. I guess now at least module creators can
>>>>> know what features are likely to work well, but it would be nice
>>>>> if front-ends worked on supporting some of these features, even if
>>>>> the text is passed through as plain text, such as canonical psalm
>>>>> titles. Nothing like that should be omitted, even if the display
>>>>> is not anything special.
>>>>>>>>>> One last note, variants do not work correctly in any front-end,
>>>>> which tells me the markup is not right. If anyone can provide a
>>>>> correction to the markup, please let me know.
>>>>>>>>>> Daniel
>>>>>>>>>> On 03/04/2012 01:18 PM, Patrick Zimmermann wrote:
>>>>>> Hey,
>>>>>>>>>>>> this is great news. Thank you.
>>>>>>>>>>>> If the rendering produced by xiphos or bibletime is at least some
>>>>>> sort of
>>>>>> acceptable I'll change the module I'm developing at the moment to
>>>>>> use the
>>>>>> syntax. Mostly additions, removals and alternatives are affected.
>>>>>>>>>>>> Thanks again,
>>>>>> Patrick
>>>>>>>>>>>> On Sunday, 4. March 2012 01:59:15 Daniel Owens wrote:
>>>>>>> Based on varied sources, including Patrick's helpful example
>>>>>>> OSIS Bible,
>>>>>>> I put together an example OSIS "Bible" that validates and is
>>>>>>> consistent
>>>>>>> with the wiki page on OSIS Bibles (
>>>>>>>http://www.crosswire.org/wiki/OSIS_Bibles). The text itself is
>>>>>>> mostly
>>>>>>> KJV text, with a little Hebrew to illustrate more than what the
>>>>>>> KJV can
>>>>>>> by itself. I chose to use the BSP structure because the KJV
>>>>>>> illustrates
>>>>>>> the BCV structure well already, and I have no idea idea how to
>>>>>>> deal with
>>>>>>> paragraphs and poetry in the BCV structure.
>>>>>>>>>>>>>> You can find the example file and the following list of features at
>>>>>>>http://www.crosswire.org/wiki/OSIS_Bibles/BSPExample:>>>>>>>>>>>>>> - BookGroup and section titles, including parallel passages:<title>
>>>>>>> - Book introduction
>>>>>>> - List:<list>,<item>
>>>>>>> - Table:<table>,<row>,<cell>
>>>>>>> - Bold and italic text:<hi>
>>>>>>> - Strong's numbers, lemma, and morphology:<w>, @lemma, @morph
>>>>>>> - Notes, including study notes and
>>>>>>> cross-references:<note>,<reference>
>>>>>>> - Marked additions:<transChange>
>>>>>>> - Canonical title (Psalms):<title type="psalm" canonical="true">
>>>>>>> - Poetry markup:<lg>,<l>
>>>>>>> - Divine Name:<seg>,<divineName>
>>>>>>> - Variants:<seg type="x-variant" subType="x-1">
>>>>>>> - Abbreviations:<abbr>
>>>>>>>>>>>>>> I compiled and tested the module, and I will send a separate
>>>>>>> email when
>>>>>>> I have a chance to record the results systematically. Suffice it
>>>>>>> to say,
>>>>>>> no one front-end supports all of the markup well, and some features
>>>>>>> (such as variants and tables) are conspicuously poorly
>>>>>>> supported. Since
>>>>>>> it is not a complete text of the KJV, some odd display issues
>>>>>>> should be
>>>>>>> ignored, but most front-ends displayed the "New Testament" title
>>>>>>> at the
>>>>>>> bottom of Psalm 3. It would be lovely if front-end developers
>>>>>>> would see
>>>>>>> how their front-end handles it (or doesn't). I can send a compiled
>>>>>>> module to those who are interested.
>>>>>>>>>>>>>> Feedback is welcome. If I have missed something or used
>>>>>>> less-than-ideal
>>>>>>> markup, please let me know, and we can change it.
>>>>>>>>>>>>>> Daniel
>>>>>>>>>>>>>> _______________________________________________
>>>>>>> sword-devel mailing list:sword-devel at 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 at 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 at crosswire.org<mailto:sword-devel at 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 at 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 at 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 at 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 at crosswire.org>http://www.crosswire.org/mailman/listinfo/sword-devel> Instructions to unsubscribe/change your settings at above page
>