<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Christopher,
<br>
<br>
This is not a problem with BibleCS or BibleDesktop. It is the
fundamental nature of how a module is constructed. For each module
there is an index of the start and length of each verse. The index does
not contain any reference to the verse. The program maintains a lookup
table that given a verse, it constructs a lookup integer for the
module's index. In the module the verses may be in any order (as long
as the verses belonging to a "block" are in the block). The index sorts
them out.
<br>
<br>
BibleDesktop gets the verses one at a time and assembles them in the
"right" order.
<br>
<br>
You might figure that you can adjust the index to reflect the order
that you desire, but it won't work as the module does <b
class="moz-txt-star"><span class="moz-txt-tag">*</span>not<span
class="moz-txt-tag">*</span></b> (for the vast majority of the cases,
I think that WLC is the only exception so far) have the verse reference
with the verse. If you store index Mat 17.3 in the Mat 17.6 slot, then
a lookup for Mat 17.6 in BibleDesktop will get the text for Mat 17.3
and label it Mat 17.6. If all of Matt 17 is shown in BibleDesktop, the
verses will display in the order you want, but the verse numbers will
be wrong (unless they are stored as part of the verse in the module.
<br>
<br>
I took a look at your example and I don't know if it matters, but it
has been posted here that using milestones for verses is a bad thing.
As far as the sword module is concerned, each verse is a container. If
you need milestones, I suggest that you pick verses as a container and
use milestones for the other elements. Better yet, avoid them if you
can. It will be a long while before a verse based system can handle
them well. (When getting and rendering a single verse that contains a
milestone, there is not much that can be done, if both the start and
end milestone are not in the same verse.) And even if we had both the
start and the end, it adds huge complexity to xslt to handle state
changes (i.e. modes are a pain!)
<br>
<br>
Hope this helps,
<br>
DM
<br>
<br>
Krzysztof Bialas wrote:
<blockquote cite="mid001201c541f2$6bfc8710$7201a8c0@ctm.gdynia.pl"
type="cite"> Hi!
<br>
I've already investigated the problem on the osis-user group. The
problem is
<br>
with the Biblie text in which there are places where the verses are not
in
<br>
sequential order. The text looks like this:
<br>
Matt.17.1
<br>
Matt.17.2
<br>
Matt.17.4
<br>
Matt.17.6
<br>
Matt.17.5
<br>
Matt.17.3
<br>
Matt.17.7
<br>
/this is of course the example, Matt is ok :-)/
<br>
After osis2mod conversion the verses order is preserved. In BibleCS and
<br>
BibleDesktop front-ends the verses are displayed back in the 'wrong'
<br>
sequential order. Is there a way to encode module in OSIS for sword so
the
<br>
not-sequential verses order would be preserved?
<br>
<br>
Christopher
<br>
P.S. I've updated the sample file
<a class="moz-txt-link-freetext" href="http://panda.bg.univ.gda.pl/~krzbia/test.osis.xml">http://panda.bg.univ.gda.pl/~krzbia/test.osis.xml</a> to show this problem
(Matt.17)
<br>
<br>
_______________________________________________
<br>
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
<br>
Instructions to unsubscribe/change your settings at above page
<br>
<br>
</blockquote>
</body>
</html>