[sword-devel] Getting stuff done (Re: External links)
bergmannmd at web.de
Thu Nov 27 00:02:39 MST 2008
Am 26.11.2008 um 23:31 schrieb Greg Hellings:
> 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
>>> (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
>> 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 second that. The direct sources that we create modules from should
be maintained by us.
The sources, any convertsion scripts and the resulting modules can and
should be version controlled by our Subversion.
More information about the sword-devel