There's an important distinction between not maintaining a revision controlled
source text and having copies of a source text to process at a particular point
in time.
There's also a difference between what gets officially stored on the CrossWire
server and what gets stored unofficially by any CrossWire volunteer on his/her
own computer.
When a volunteer like me converts USFM to OSIS on our own PC, they can decide
whether the OSIS thus produced is good enough to make a SWORD module.
There are projects where this is not the case, and where (e.g.) the CrossWire
script to fix references isn't up to the quality requirements.
In such cases, one might decide to process the OSIS locally by other means and
submit that for the purpose of module release.
A lot of text development activity goes on day by day before stuff ever
surfaces to the CrossWire modules team.
Some of this activity is collaborative, but it's up to the individual
volunteers rather than what CrossWire does as a Bible Society.
Best regards,
David
Sent from ProtonMail Mobile
On Thu, Jan 4, 2018 at 18:41, L'Africain <lafricai...@gmail.com> wrote:
> Le 04/01/2018 à 18:09, David Haslam a écrit :
>
>> Everyone - please understand that CrossWire does not maintain the source
>> text files for any SWORD modules apart from the flagship KJV and KJVA
>> modules.
>
> Ok it is clear, but what you do with texts send by people for the module
> creation (Example when I send you the usfm files for konnym)? Because if I
> understand well you want to do yourself the module with the osis no?
>
>> All other module updates depend on someone starting again from the most
>> recent source text files provided by third parties.
_______________________________________________
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
