Re: [sword-devel] Namespace Proposal re eBible - collissions, duplication, clean-up etc
See below: On 09/04/2015 01:43 AM, Karl Kleinpaste wrote: On 09/03/2015 07:09 PM, Kahunapule Michael Johnson wrote: Please make sure you get a fresh copy from the repository. I always refresh immediately before such tests; such was the case 90 seconds before I wrote. the morphology tags have been stripped from this module for now. Those may come back, later, if I have time to deal with all of that. ?!? Why did you do that? As I wrote when first looking over grcTisch (Wed 09:02pm), all you needed to fix the problem was to add GlobalOptionFilter=OSISMorph in order to trigger the apps' ability to switch it on and off in the engine, and (in Xiphos' case) to provide for the needed separate subtext layer to hold it, apart from Strong's, when switching it on. There's nothing "to deal with," you just have to configure it properly. Literally a one-line .conf fix. I had already manually added it to my local copy and seen that it would then be fine. Thank you for that information. There are two things to deal with right now, for me, other than what looks like a one-line .conf fix. One is a steep learning curve of how morphology tags work with the markup variations and the different applications and front ends. Your assurance that everything was fine except for the .conf line is helpful. I was concerned that there might be other, deeper issues and an unending quagmire of tweaks. The other thing is that I don't do one-line .conf fixes directly. I fix the process, not the .conf file, and let the process generate the correct .conf file. This is slower for one module. It is orders of magnitude faster for hundreds of modules. This is not a really hard thing, but I'm currently only fixing repository show-stopper items for launching the eBible.org repository. The rest will have to wait until the repository is officially on line. -- Aloha, Kahunapule Michael Johnson 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
Re: [sword-devel] Namespace Proposal re eBible - collissions, duplication, clean-up etc
Welcome back, Troy. Enjoy the vacation from your vacation. ; The "eb" namespace trailer has now been added to all of the Bible modules in the eBible.org repository. The last update cycle is complete, and the repository is at rest. eBible.org main repository: ftp://ftp.eBible.org/sword or http://eBible.org/sword eBible.org beta repository: ftp://ftp.eBible.org/swordbeta or http://eBible.org/swordbeta The previously-advertised ftp://ftp.eBible.org/pub/sword still works, and probably will continue to work, but the shorter URL seems preferable to make primary, right now. On 09/04/2015 03:46 AM, Troy A. Griffitts wrote: On 09/03/2015 10:50 PM, Peter von Kaehne wrote: Where is Troy and what does he think? I have just arrived back from being tour-guide for my sister on vacation and now I need a vacation :) I've been following these threads, catching up when I have time, and I think the conversations happening need to happen and everyone ultimately is coming to sane and logical conclusions. I am enjoying being a spectator. I like Peter's suggestion to namespace with a trailing publisher code for all the reasons everyone has said, and especially since it will get the eBible repo online publicly without any engine changes right now. Great work and I'm excited about all the movement and new resources for the Gospel mission! Troy Peter On Thu, 2015-09-03 at 10:21 -1000, Kahunapule Michael Johnson wrote: Based on Peter's good advice and sound reasoning, I'm appending an "eb" to every Bible module name in the eBible.org repository. I didn't want to lengthen the module names excessively with something like "eBible_org" or even "ebib" on the end-- just enough to avoid collisions among less than a dozen repositories. These module names get crammed into really small spaces at times, for better or for worse, at least for display. One letter appended didn't seem quite enough for clarity, but two letters provides 676 possible combinations and a reasonable chance of assigning sequences that make sense, like cw, ib, xi, etc. I'm not putting in an obsoletes line in the conf files for these changes, leaving a manual cleanup challenge behind. Such obsoletes lines would have undesired side-effects in the case of existing collisions, especially the worst kind, where names differ only by case. I'm assuming that the other modules probably won't change their module names for existing modules, being already fully public and in general use already, but might adopt a similar convention for all new modules. I regret any inconvenience this naming convention change may cause for those awesome people who have been testing the eBible.org repositories. It seems that this little thing will solve more problems (including solving problems in advance) for more people than the inconvenience it may cause. In the case of the non-Bible modules on the eBible.org repository, I'm not renaming them at this time, because they are bit-for-bit copies of the same modules from Crosswire main. Therefore, duplication should not be a problem. Those are there merely as a convenience. They could be removed if they actually do cause a problem. Module abbreviations are mostly unchanged. Collisions could happen. I think the consensus is that those will be dealt with by the front ends when they happen for particular users. In other news, I have (1) disabled morphology tags that don't use the same system as DM's KJV, and (2) corrected a bug in the code where it was possible for Haiola to miss generating a GlobalOptionFilter=OSISMorph line in the conf file. The new grcTisheb module should at least display correctly, even though it is missing some features. I'll deal with that later. Maybe. Ideally, I will restore the missing features when I learn some things I don't yet know and have time to implement that. Thank you, front end developers, for making adjustments to handle another very large repository. Thank you, all who have tested the new repository and pointed out opportunities for improvement, some of which have been essential. With the addition of the new eBible.org repository: More people will be able to use Sword project software for Bible study on their favorite devices and in their own language. Adding new Bibles and Bible portions to the Crosswire Sword module collection just got orders of magnitude easier and faster. Frequent revisions and additions for translations that are in progress are truly practical, now. New books can be added or updated as they are completed or revised. We have a way of easily tapping into Paratext projects for rapid updates, which is actually happening now with about a dozen projects. We have a way to quickly publish any Bible we get permission for from the Every Tribe Every
Re: [sword-devel] Namespace Proposal re eBible - collissions, duplication, clean-up etc
On 09/03/2015 10:50 PM, Peter von Kaehne wrote: > > Where is Troy and what does he think? I have just arrived back from being tour-guide for my sister on vacation and now I need a vacation :) I've been following these threads, catching up when I have time, and I think the conversations happening need to happen and everyone ultimately is coming to sane and logical conclusions. I am enjoying being a spectator. I like Peter's suggestion to namespace with a trailing publisher code for all the reasons everyone has said, and especially since it will get the eBible repo online publicly without any engine changes right now. Great work and I'm excited about all the movement and new resources for the Gospel mission! Troy > > Peter > > > > On Thu, 2015-09-03 at 10:21 -1000, Kahunapule Michael Johnson wrote: >> Based on Peter's good advice and sound reasoning, I'm appending an >> "eb" to every Bible module name in the eBible.org repository. I >> didn't want to lengthen the module names excessively with something >> like "eBible_org" or even "ebib" on the end-- just enough to avoid >> collisions among less than a dozen repositories. These module names >> get crammed into really small spaces at times, for better or for >> worse, at least for display. One letter appended didn't seem quite >> enough for clarity, but two letters provides 676 possible >> combinations and a reasonable chance of assigning sequences that make >> sense, like cw, ib, xi, etc. I'm not putting in an obsoletes line in >> the conf files for these changes, leaving a manual cleanup challenge >> behind. Such obsoletes lines would have undesired side-effects in the >> case of existing collisions, especially the worst kind, where names >> differ only by case. I'm assuming that the other modules probably >> won't change their module names for existing modules, being already >> fully public and in general use already, but might adopt a similar >> convention for all new modules. >> >> I regret any inconvenience this naming convention change may cause >> for those awesome people who have been testing the eBible.org >> repositories. It seems that this little thing will solve more >> problems (including solving problems in advance) for more people than >> the inconvenience it may cause. >> >> In the case of the non-Bible modules on the eBible.org repository, >> I'm not renaming them at this time, because they are bit-for-bit >> copies of the same modules from Crosswire main. Therefore, >> duplication should not be a problem. Those are there merely as a >> convenience. They could be removed if they actually do cause a >> problem. >> >> Module abbreviations are mostly unchanged. Collisions could happen. I >> think the consensus is that those will be dealt with by the front >> ends when they happen for particular users. >> >> In other news, I have (1) disabled morphology tags that don't use the >> same system as DM's KJV, and (2) corrected a bug in the code where it >> was possible for Haiola to miss generating a >> GlobalOptionFilter=OSISMorph line in the conf file. The new grcTisheb >> module should at least display correctly, even though it is missing >> some features. I'll deal with that later. Maybe. Ideally, I will >> restore the missing features when I learn some things I don't yet >> know and have time to implement that. >> >> Thank you, front end developers, for making adjustments to handle >> another very large repository. >> >> Thank you, all who have tested the new repository and pointed out >> opportunities for improvement, some of which have been essential. >> >> With the addition of the new eBible.org repository: >> More people will be able to use Sword project software for Bible >> study on their favorite devices and in their own language. >> Adding new Bibles and Bible portions to the Crosswire Sword module >> collection just got orders of magnitude easier and faster. >> Frequent revisions and additions for translations that are in >> progress are truly practical, now. New books can be added or updated >> as they are completed or revised. >> We have a way of easily tapping into Paratext projects for rapid >> updates, which is actually happening now with about a dozen projects. >> We have a way to quickly publish any Bible we get permission for from >> the Every Tribe Every Nation Digital Bible Library. >> This is a level of automation and service that I think is a great >> advance for the Crosswire Bible Society. Pat yourselves on the back, >> because I can't reach you from my computer. OK, now back to work. ;-) >> >> >> Yesterday's conf clean-up is done, and moved to >> http://eBible.org/sword. The renaming process is in progress, module >> by module, at http://eBible.org/swordbeta. >> >> On 09/03/2015 04:05 AM, Peter von Kaehne wrote: >>> On Thu, 2015-09-03 at 09:29 -0400, Karl Kleinpaste wrote: Adding complexity to configuration will not solve the problems being fo
Re: [sword-devel] Namespace Proposal re eBible - collissions, duplication, clean-up etc
On 09/03/2015 07:09 PM, Kahunapule Michael Johnson wrote: > Please make sure you get a fresh copy from the repository. I always refresh immediately before such tests; such was the case 90 seconds before I wrote. > the morphology tags have been stripped from this module for now. Those > may come back, later, if I have time to deal with all of that. ?!? Why did you do that? As I wrote when first looking over grcTisch (Wed 09:02pm), all you needed to fix the problem was to add GlobalOptionFilter=OSISMorph in order to trigger the apps' ability to switch it on and off in the engine, and (in Xiphos' case) to provide for the needed separate subtext layer to hold it, apart from Strong's, when switching it on. There's nothing "to deal with," you just have to configure it properly. Literally a one-line .conf fix. I had already manually added it to my local copy and seen that it would then be fine. ___ 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
