[sword-devel] Change to Synodal verse system

Chris Little chrislit at crosswire.org
Mon Aug 1 04:21:20 MST 2011

At the time 1.6.2 was released, there were still no major Sword apps 
that had been released with support for av11n to the extent necessary to 
support Synodal-v11n modules. We had also only released a couple of 
Synodal-v11n modules and only released them to the experimental 
repository. Accordingly, we updated the v11n definition in place in 
order to support the set of Synodal-v11n-like texts that include a Ps 114:9.

If an error were ever to be found in a released and reasonably 
widely-supported v11n, we wouldn't implement the strategy you suggest, 
of supporting two v11ns temporarily and removing the old v11n later. We 
might deprecate the flawed v11n, but we would probably keep it in the 
library forever.


On 8/1/11 12:48 AM, John Austen wrote:
> An error in the Synodal verse system (canon_synodal.h) was fixed in
> sword-1.6.2, which is great. Psalms 114:9 was missing from the verse
> system, but has now been included.
> My concern is that the fixed verse system has the same name as the old
> one. So the many existing Synodal Sword modules are no longer compatible
> with Sword, and new Synodal modules are not compatible with older Sword
> programs. Since Sword programs and Sword modules are upgraded
> independently from one another, this will cause the many current users
> of Synodal texts great problems and frustrations in the future.
> Does anyone have ideas on a solution to this problem?
> I'm wondering if in this very special case (a fix to a cannon) we might
> do the following: Give the new (fixed) "Synodal" cannon a new name. Then
> allow both the old "Synodal" and the new Synodal verse systems to remain
> in the codebase together for a reasonable time (maybe a year). Then,
> after most users will have upgraded both their programs and modules for
> other reasons, we can remove the old "Synodal" cannon from the code
> base, keeping only the new one. In this way, most users will never
> notice the transition, which is a very good thing since many Synodal
> users are not necessarily computer savvy enough to be able to diagnose
> and fix such an enigmatic incompatibility on their own.
> Thanks,
> John
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

More information about the sword-devel mailing list