[sword-devel] Getting stuff done (Re: External links)
chrislit at crosswire.org
Wed Nov 26 23:35:23 MST 2008
Greg Hellings wrote:
> On Wed, Nov 26, 2008 at 4:27 PM, Chris Little <chrislit at crosswire.org> wrote:
>> Matthew Talbert wrote:
>>> I would just like to point out again that there is very little
>>> transparency in how bugs are updated and fixed in modules. Neither
>>> does it appear to happen quickly. For example, someone reported a bug
>>> (several bugs) in the ISBE module to the sword-support list 4 days
>>> ago, and no one has even replied. I do not know what to say, because I
>>> do not know how bugs like those reported could/should get fixed.
>> I don't really know how to respond either, since the bug that the user
>> thinks is there isn't. I'm planning to update the ISBE to TEI, which
>> would clear up the issue that the user thinks is there, but I need to
>> find a good source.
> Which is an excellent reason why CrossWire should at least, as was
> mentioned earlier, maintain the immediate form of the
> OSIS/TEI/ThML/RandomMarkupFormat that is fed into the import
> utilities. You might find a good source, after long searching, and go
> to report/fix a bug in theirs later and find them gone/moved/etc. If
> a copy of the directly imported form was kept on-hand, then at least a
> problem like that could be overcome.
I do keep copies of my own work, as well as copies of submissions that
come through me. It doesn't really pertain to this case as this is a
module from about 10 years ago. I might still have the original source
somewhere. Finding the hard drive it's on would be another matter
And in this case, it was considerably more efficient to simply export to
IMP, do a bunch of corrections by hand, and re-import the text.
New version is out, BTW. It's basically just the same ThML version with
some corrections--clean-up done prior to converting to TEI.
More information about the sword-devel