Re: embedded milestones. Each entry has its own text that isn't repeated, but also isn't in the biblical stream... These entries are displayed many times via iframes from within the biblical text. That is, at the commentary level: (comment1, comment2, ..., comment7399)
Genesis 1:0 pulls an iframe for the book, testament, and work intros (<gen1:0> <iframe source=comment1> <iframe source=comment35> <iframe source=comment201> Genesis 1:1 pulls an iframe for each commentary that references it. (<gen1:1> <iframe source=comment 5> <iframe source=comment7> <iframe source=comment17>) It's been years since I looked at osis this deep, but I'm pretty sure the commentary had a plan to allow for both non-biblical and biblical entries like this where you could have both a topical and biblical index within the same work. Maybe I'm hanging out beyond saturn, and this was enhancements I never submitted. For sword, this is the most preferred and useful setup for commentaries with a deep layered structure. Parallel displays of whole chapters get cumbersome. but on reference for any point shows you the complete set. and the most common use of a deep commentary isn't as a second parallel passage, but as a verse specific research point. A sparse commentary might be appropriate for a parallel column, but these deep commentaries aren't. On Thu, Nov 15, 2018 at 4:06 PM Dudeck, John <[email protected]> wrote: > Troy, > > The problem is not parsing references. I have that figured out long ago, > and converting from Logos to Sword, etc. > > The problem is that when you have a commentary with, for example a > milestone for Gen 1:1-31 with some introductory material, followed by a > sub-heading with a milestone for Gen 1:1-13, then followed by verse > commentaries for Gen 1:1-5, then Gen 1:6-8, then Gen 1:9-13. When compiling > with osis2mod, it doesn't quite know what to do with the nested ranges, and > stuff does not display properly. > > John > > > > > Hi John, > > Do you have an example? Our parser handles some pretty crazy verse > references. You can > > give it a try here: > > > > http://crosswire.org/study/examples/parsevs.jsp > > > > > > > > On 11/15/18 10:35 AM, Dudeck, John wrote: > > The main problem with commentaries is getting the annotateRef attribute > right without > > manual intervention. Logos supports nested levels of reference, eg. > book-level, > > chapter-level, verse-level, and verse ranges (that can span mutiple > chapters). As far as I > > can tell, osis2mod gets terribly confused with nested ranges. > > > > Generally speaking, black box converters are pretty much a lost cause. I > have used a .conf > > file approach where variable stuff can be configured, for example how to > map class and > > style attributes to the limited rendering capabilities of Sword. And I > have separate scripts > > for genbooks, bibles, commentaries, and dictionaries/lexicons. > > > > John > > > > > Any time your list of exceptional conditions contains more text than > the > > > conversion itself, you have to start questioning whether 'automation' > is > > > even possible. > > > > > > I spent time developing similar scripts (something like wordxml -> > > > USFM) for single use cases. Doing the conversion was usually about > > > 10 steps, but then dealing with the exceptions (both before and after > > > the conversion) took 100+ steps. Without automation, the 10 steps > > > was good enough. but not keeping a human involved, all the human > > > decisions had to be mapped. > > > > > > > > > > > > > > > On Thu, Nov 15, 2018 at 10:39 AM Greg Hellings < > [email protected]> wrote: > > > > > > > > > On Thu, Nov 15, 2018 at 10:35 AM Dudeck, John <[email protected]> > wrote: > > > I am developing a set of Perl scripts that convert Logos XML to OSIS > for > > > commentaries. It has proven to be a non-trivial exercise. > > > > > > I undertook a similar exercise over a decade ago as part of an > internship. It was a beast > > of > > > a task and one that was never fully completed. > > > > > > --Greg > > John Dudeck > Programmer at Editions Cle Lyon, France > [email protected] [email protected] > -- > "If we knew what it was we were doing, it would not be called > research, would it?" -- Albert Einstein > > _______________________________________________ > sword-devel mailing list: [email protected] > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page
_______________________________________________ sword-devel mailing list: [email protected] http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
