I have a correction to make. Gnomesword 2.4 does display the introductions, but like BibleTime it doesn't support the outline as a list.

Daniel

Daniel Owens wrote:
Karl Kleinpaste wrote:
> Daniel Owens <[EMAIL PROTECTED]> writes:
>   
>> However, the book outlines in the
>> introduction are a thorny problem because neither lists nor regular
>> paragraphs appear correctly (the outlines become a single
>> paragraph--totally unreadable--though they are encoded in proper
>> OSIS).
>>     
>
> Can you provide an example?  Is there an existing module that shows the
> sort of problem you describe?
>
>   
Yes, I can. I can send the module compiled or just osis or both privately. Just 
let me know that you want it, and I will send it. The module is in the 
[EMAIL PROTECTED] inbox waiting for action, but there are a number of 
problems with it that I haven't been able to solve. Actually, aside from the 
book introductions, GS handles the module the best out of all the front-ends.
>> Third, the way Sword handles commentaries right now is fine if you're
>> looking at a single verse and the commentary is dealing with a single
>> verse, but often commentaries give comments on the structure or
>> theology of a section or comment on a range of verses in a single
>> paragraph or section. I am wondering if there is a way to have a more
>> dynamic and continuous way to view commentaries so if you open to
>> Genesis 1:1 you can just scroll down a bit to see Genesis 1:2
>>     
>
> Are you aware that you can specify verse ranges?
>
>   
Yes, I was aware of that. What I was getting at is a combination of content 
unconnected to a verse or range of verses (such as introductory matter in a 
commentary), content connected to a range of verses, and content connected to a 
single verse all in one work. This kind of content should be preserved as one 
work, in my opinion, but how do you encode something like that?
> The commentary/image module DoreWoodcutsCom (verse-keyed version of
> DoreWoodcuts, able to be used as a sort of graphical commentary) is
> import-encoded like this:
>
> $$$Gen 3:1-24
> Adam And Eve Are Driven Out Of Eden
> <br /><img src=""/>
> $$$Gen 4:1-7
> Cain And Abel Offer Their Sacrifices
> <br /><img src=""/>
> $$$Gen 4:8-26
> Cain Slays Abel
> <br /><img src=""/>
>
> The 1st covers the entirety of Gen 3.  The 2nd covers the beginning of
> Gen 4, the 3rd covers the rest of Gen 4.
>
> This is the idea behind what I mentioned as "fast" and "slow"
> commentaries: The fast side is per-verse commentary, relating directly
> to translation, text-critical observations, and related matters.  The
> slow side is prose discussion of larger sections.  As verses change,
> the slow commentary would not change until the verse boundary is passed
> when the next big section comes along.
>
>   
The idea of multiple types of content being preserved in multiple types of 
windows is a good step beyond where commentaries are today, but I guess I would 
just be interested to see how we can preserve the integrity of the original work 
while at the same time not making it a coding nightmare.

Daniel
> _______________________________________________
> 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
>
>   

-- 
PMBX license 1502 

  

_______________________________________________ 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

-- 
PMBX license 1502 
_______________________________________________
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

Reply via email to