Re: [sword-devel] ICU build fix

2006-10-06 Thread Deji Akingunola
Hi, On 10/6/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hello everyone, > > I believe I have a solution for the problems building sword-1.5.9 with ICU. Hmm, AFAIK, there is no problem building sword-1.5.9 with icu > Tests were failing to build properly. The attached patch solved the comp

[sword-devel] ICU build fix

2006-10-06 Thread munns
Hello everyone, I believe I have a solution for the problems building sword-1.5.9 with ICU. Tests were failing to build properly. The attached patch solved the compile errors in Unicode streams for me, maybe it will for everyone else hopefully including Fedora Core users. A good test to see your

Re: [sword-devel] The SWORD Project for Windows 1.5.9 installers testing

2006-10-06 Thread DM Smith
L.Allan-pbio wrote: > Some observations (none major ... good work): > Thanks. > * nit ... Crosswire license mentions copyright 1994-2005 ... should > this be 2006? (the Help About for sword.exe itself has 2006) > Good catch. > * SWORD_PATH environment variable over-written ... should per

Re: [sword-devel] The SWORD Project for Windows 1.5.9 installerstesting

2006-10-06 Thread L.Allan-pbio
I also don't understand why the InstallManager fields can't be pre-filled with default, valid info. Why would this convenience cause risks? I can understand if they proceed to get modules, but not why it is a risk just the convenience of prefilling a rather obscure part of The SWORD Project (if

Re: [sword-devel] The SWORD Project for Windows 1.5.9 installers testing

2006-10-06 Thread L.Allan-pbio
Some observations (none major ... good work): * nit ... Crosswire license mentions copyright 1994-2005 ... should this be 2006? (the Help About for sword.exe itself has 2006) * SWORD_PATH environment variable over-written ... should permission be asked to do this if one already exists (makes in