Chris,
Another test I should like to add is a well-formed and/or a validity
test against the osis or thml schema. And to look for extraneous
markup such as { } and \. These creep in various modules.
BibleDesktop extensively tests the conf against what the wiki
documentation says the values in the conf must/can/should be,
reporting any errors to the console. So starting BD from the command
line and then opening the Book installer will survey all the conf's.
For the last several releases the Beta site has been part of the
installer.
The biggest problems are that the DistributionLicense values are
straying from the 4 prescribed values to give additional information.
The other problem I have encountered is that "po" is not the language
code for Polish.
Hope this helps.
In Him,
DM
On Aug 22, 2007, at 12:32 AM, Chris Little wrote:
>
> peter wrote:
>> There are a lot of modules in Beta which work perfectly well and
>> should
>> be moved.
>
> Unfortunately we don't know that they work well because most of the
> modules in Beta haven't been extensively tested.
>
> I will probably write some module testing utilities to identify
> missing
> or repeated verses, invalid/incorrect .conf entries, maybe a validity
> checker for generated RTF, and such.
>
>> The Turkish2.conf needs to be updated - see below - then it could get
>> moved over.
>
> I've updated the New Turkish Bible's .conf file and renamed it TurNTB,
> but I still want to test it more extensively.
>
> --Chris
>
> _______________________________________________
> sword-devel mailing list: [email protected]
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
_______________________________________________
sword-devel mailing list: [email protected]
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
