Re: [sword-devel] Bibles in Beta

2008-06-17 Thread Daniel Blake
Another reason for storing the original text is to be able to compare and prove we haven't changed the actual text. Along with proving what source text was actually used. As I understand it, we don't even know what the original source was for some of the current modules. That can't be a good

Re: [sword-devel] Bibles in Beta

2008-06-17 Thread Greg Hellings
On Tue, Jun 17, 2008 at 1:20 AM, Manfred Bergmann <[EMAIL PROTECTED]> wrote: > > Am 16.06.2008 um 22:45 schrieb DM Smith: > >> Peter von Kaehne wrote: >>> The way we work with software is >>> >>> 1) multiple independent projects >>> 2) each project has one or several leads >>> 3) there are other co

Re: [sword-devel] Bibles in Beta

2008-06-16 Thread Manfred Bergmann
Am 16.06.2008 um 22:45 schrieb DM Smith: > Peter von Kaehne wrote: >> The way we work with software is >> >> 1) multiple independent projects >> 2) each project has one or several leads >> 3) there are other contributors with and without write access to the >> project repository >> 4) all project

Re: [sword-devel] Bibles in Beta

2008-06-16 Thread Manfred Bergmann
Am 16.06.2008 um 22:35 schrieb Sebastien Koechlin: > On Mon, Jun 16, 2008 at 08:43:38PM +0100, Peter von Kaehne wrote: >> a) having a raw text repository where the texts are kept in some >> import >> format (OSIS, ThML, whatever) under version control >> b) with named module owner(s) and contri

Re: [sword-devel] Bibles in Beta

2008-06-16 Thread Chris Little
Sebastien Koechlin wrote: > I think it's a very good idea. As a module maintainer (FreJND), I'm on the > list for more than a year. I submited a module on January 1st, and it's > still not in the beta repository. I asked friends to review it, but as it is > still not in beta, they can not install

Re: [sword-devel] Bibles in Beta

2008-06-16 Thread Sebastien Koechlin
On Mon, Jun 16, 2008 at 08:43:38PM +0100, Peter von Kaehne wrote: > a) having a raw text repository where the texts are kept in some import > format (OSIS, ThML, whatever) under version control > b) with named module owner(s) and contributor(s) - > c) with some form of automated build mechanism whi

Re: [sword-devel] Bibles in Beta

2008-06-16 Thread Peter von Kaehne
DM Smith wrote: >> Peter wrote: >> a) having a raw text repository where the texts are kept in some import >> format (OSIS, ThML, whatever) under version control >> > I think this needs to be the original text as we received it. Not the > import format. We should keep complete records of when,

Re: [sword-devel] Bibles in Beta

2008-06-16 Thread DM Smith
Peter von Kaehne wrote: > The way we work with software is > > 1) multiple independent projects > 2) each project has one or several leads > 3) there are other contributors with and without write access to the > project repository > 4) all projects are in some form of version control > 5) Many proj

Re: [sword-devel] Bibles in Beta

2008-06-16 Thread Greg Hellings
On Mon, Jun 16, 2008 at 3:09 PM, Peter von Kaehne <[EMAIL PROTECTED]> wrote: > Dm Smith wrote: > >> Chris, don't take it as criticism or a put down. I don't mean it >> that way. I appreciate all your hard work and your contributions! > > Seconded, wholeheartedly. Agreed! It seems on my hearings

Re: [sword-devel] Bibles in Beta

2008-06-16 Thread Peter von Kaehne
Dm Smith wrote: > Chris, don't take it as criticism or a put down. I don't mean it > that way. I appreciate all your hard work and your contributions! Seconded, wholeheartedly. ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crossw

Re: [sword-devel] Bibles in Beta

2008-06-16 Thread DM Smith
Peter von Kaehne wrote: > The TurNTB has often verses grouped together, but this is not encoded > ie.g. as v4-6 but instead v4 has all content and v5 and v6 are empty. > So the list you showed for it is endless in consequence. > The wiki says that this module is known bad, so I'll assume that i

Re: [sword-devel] Bibles in Beta

2008-06-16 Thread Peter von Kaehne
The way we work with software is 1) multiple independent projects 2) each project has one or several leads 3) there are other contributors with and without write access to the project repository 4) all projects are in some form of version control 5) Many projects have a development version and (in

Re: [sword-devel] Bibles in Beta

2008-06-16 Thread Peter von Kaehne
The TurNTB has often verses grouped together, but this is not encoded ie.g. as v4-6 but instead v4 has all content and v5 and v6 are empty. So the list you showed for it is endless in consequence. I would think this + alternative versification is the case in many other Bibles. Personally I would

[sword-devel] Bibles in Beta

2008-06-16 Thread DM Smith
For what it's worth, I've "scoped out" the Bibles in beta, comparing them to the KJV versification. (I skipped the GenBook Bibles) I wrote a little program using JSword to do the work. Hopefully, I didn't make a mistake in writing it. (I've spot checked it against GnomeSword.) Below are the res