<!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">
Sorry for the late delay in my response--we had some medical challenges
in our family necessitating an evacuation, so I am now away from my
desktop and using my wife's laptop, which only has Windows installed. <br>
<br>
I like the idea that OSIS tagging, if it is legal, should work. I will
go back and do my best to check the tagging against the OSIS 2.1.1
schema first to make sure I have done things right. After that I will
create a module and check to make sure that it is still creating the
problem and then file bug reports and send the module if there are
still problems.<br>
<br>
I have a suggestion for improving the wiki for module creation. The
documentation on module creation is detailed for the *.conf files, but
there isn't much available in the way of OSIS example xml documents.
The Bible Technologies Group website has some OSIS 2.0 examples, and
that is what I used as a model for my tagging since the CEV example has
almost all the features that I needed for the translation I am working
with (including notes, section headings, ect.). I work better from
concrete examples than the lengthy user manual for OSIS 2.1.1, which I
am now scouring for answers to my questions. When I created the module
and ran into problems I wasn't sure whether the problem was the various
Sword front-ends (Gnome Sword did fine while most others had problems)
or my tagging. If someone could create some short example xml files to
put on the module creation wiki, that would help average module
creators like me compare our tagging with something that is KNOWN to
work in the Sword library. Short examples of prose and poetry Bible
text with common features, a commentary, a general book, and a
dictionary would be really useful. They need not be complete--partial
documents with enough to demonstrate the features supported by Sword
would go a long way in helping average module creators imagine what
their xml document needs to look like.<br>
<br>
Daniel<br>
<br>
Eeli Kaikkonen wrote:
<blockquote cite="midPine.GSO.4.58.0708282200470.16744@paju.oulu.fi"
type="cite">
<pre wrap="">On Sat, 25 Aug 2007, Daniel Owens wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I'm working on tagging a bible in OSIS, and when I use osis2mod the
module shows up in Bibletime, but there are a few quirks I'd appreciate
help with. I followed the examples from the OSIS website.
</pre>
</blockquote>
<pre wrap=""><!---->...
</pre>
<blockquote type="cite">
<pre wrap="">Can anyone advise me on how to fix my tagging?
</pre>
</blockquote>
<pre wrap=""><!---->
My opinion is that if your tagging is "legal" osis you should not need
to change it but the library/frontends should be fixed. It may very well
be that the problem is in "filters" which translate the osis text into
html or something else. BibleTime has it's own filters but a bug can
be in both Sword's and BibleTime's filter.
Just now I'm too hungry and busy to look at it but I suggest that if you
don't find anything wrong with you tagging you could file this as
BibleTime bug. We just need access to your module.
Yours,
Eeli Kaikkonen (Mr.), Oulu, Finland
e-mail: <a class="moz-txt-link-abbreviated" href="mailto:eekaikko@mailx.studentx.oulux.fix">eekaikko@mailx.studentx.oulux.fix</a> (with no x)
_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page
</pre>
</blockquote>
</body>
</html>