Thanks Michael, Troy,
Despite a very loud appeal for complaints on a large number of mailing lists and even more direct emails to various developers I have not received any show stopping responses.
The responses we all saw re capitalisation etc, are in my view examples of ongoing quality assurance work which will continue to be required, but should not stop us from going live.
Troy, I think you should put the repo on the master repo list
Peter
Gesendet: Freitag, 14. August 2015 um 17:10 Uhr
Von: "Kahunapule Michael Johnson" <kahunap...@ebible.org>
An: sword-devel@crosswire.org
Betreff: Re: [sword-devel] eBible.org repository refresh done
Von: "Kahunapule Michael Johnson" <kahunap...@ebible.org>
An: sword-devel@crosswire.org
Betreff: Re: [sword-devel] eBible.org repository refresh done
Thank you, Troy for the light on the subject.
The eBible.org repository refresh is done, again, with no case squashing anywhere, and consistent capitalization. I hope. (Tell me if I missed something, of course.)
I'm not worried about case collisions in the repository, as all module names are unique without regard to case, but just more readable with mixed case. (I would discover any exceptions when I copy them to a case insensitive file system for testing with Windows or Mac if I goofed.) Since the zip files don't follow the same case-squashing convention (a kind of confusing exception), I think it is probably less error-prone to just always do the same thing with case. I'm not worried about 8.3 file systems or PalmOS for these, as they are mostly minority language Bibles in countries where I haven't seen a PalmOS device in use for years. My own last PalmOS device disintegrated years ago. The most common platforms actually used will be Android, followed by iOS, Windows, Mac OS, and Linux, in that order. (Anyone running Solaris, HPUX, BSD Unix, etc., is probably geeky enough to compile their own.)
Anything else?
On 08/13/2015 01:19 PM, Troy A. Griffitts wrote:
The eBible.org repository refresh is done, again, with no case squashing anywhere, and consistent capitalization. I hope. (Tell me if I missed something, of course.)
I'm not worried about case collisions in the repository, as all module names are unique without regard to case, but just more readable with mixed case. (I would discover any exceptions when I copy them to a case insensitive file system for testing with Windows or Mac if I goofed.) Since the zip files don't follow the same case-squashing convention (a kind of confusing exception), I think it is probably less error-prone to just always do the same thing with case. I'm not worried about 8.3 file systems or PalmOS for these, as they are mostly minority language Bibles in countries where I haven't seen a PalmOS device in use for years. My own last PalmOS device disintegrated years ago. The most common platforms actually used will be Android, followed by iOS, Windows, Mac OS, and Linux, in that order. (Anyone running Solaris, HPUX, BSD Unix, etc., is probably geeky enough to compile their own.)
Anything else?
On 08/13/2015 01:19 PM, Troy A. Griffitts wrote:
Not commenting on the merits, but only on the necessities and history: Module names can (often should be for readability) upper and lower caseDataPath needs to match exactly the data path on the file system. The case needs to match because some operating systems are case sensitive. Historically, we've always lowercased the all file and folder names for better consistency between OS/FSs that ignored case and others that don't. i.e., if we only use one case, then we shouldn't run into any problems. This has just been historical convention and maybe to avoid issues on 8.3 FSs from long ago or wince or palmos or something, but the important thing today is that the configuration file DataPath entry needs to match the actual data path or else OS/FSs that do honor case will not find the files. It is such a blessing the work you and everyone have done to make these resources available! Troy On 08/13/2015 09:58 PM, Kahunapule Michael Johnson wrote:It seems to me that squashing to lower case for file system references is what caused problems in the first place, because I didn't also squash the module name to lower case. Wouldn't it be better to keep the module name the same as the file & directory names? Of course, I could squash both to lower case, but that raises readability issues where I use case to show a transition from language code to translation abbreviation, like thaKJV2003. Right now, a process is running to make the casing match on everything, but it is not squashing everything to lower case. What do you think? On 08/13/2015 08:20 AM, Karl Kleinpaste wrote:On 08/13/2015 02:15 PM, Kahunapule Michael Johnson wrote:Is there anything else that needs to be fixed?I've just been periodically trying to load up the entire content and reporting what I find doesn't work. As for fixing this sort of thing, generally speaking I believe we have always recommended that all filesystem references (DataPath in .conf; directories' names that contain content; module-internal references like <img src="" be squashed to lowercase. _______________________________________________
--
| Your partner in electronic Bible publishing, |
| MICHAEL JOHNSON PO BOX 881143 PUKALANI HI 96788-1143 USA |
eBible.org MLJohnson.org Mobile: +1 808-333-6921 Skype: kahunapule |
_______________________________________________ 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
_______________________________________________ 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
