Mon, 22 May 2000 19:17:42 +0000
Sorry, but I found a bug.
I think everybody knows it's possible to have modules in a users $HOME/.sword directory.
But if a encrypted modules is stored there I can't save the key to the config file which is in
$HOME/.sword/mods.d/ (using BibleTime 0.3pre).
This is caused by the old SWORD architecture.
is everytime the same global path (e.g. /usr/local/sword/) but it's not possible to get the
path of the $HOME etc.
Or should I do this by hand?
May I submit my changes to CVS (changed provate: to protected: in swmgr.h,
otherwise BibleTime 0.3pre won't compile.). I wan't to place the latest version on the SWORD CD
(ok, Brook will do it ;-).
And there was a compiling problem with GCC 2.95.2, I'll submit the change this afternoon
(changed char* to const char* ;-).
The nasty encryption related problem is solved now !!
Thanks Troy and all the others!
The only problem is the localiziation bug I reported in my previous mail.
Very good work Troy!
>Ok everyone, I've merged all the past 2 months worth of work on 1.4.x
>into the 1.5.x tree. Please let me know if we fixed all your 1.5.x bugs
>or if we created any new ones.
>Try out the new range parse functionality with the updated
>tests/parsekey test program. Localization doesn't seem to work
>correctly for me when parsing. I'm hoping I'm just typing the wrong
>letters or that my de.conf file is outdated. Please let me know if it
>works/doesn't work for you. US locale seems to work ok.
>parsekey "gen 1:1-5,3-7;7:9,10;jas1-5"
>All the latest stuff is in CVS.
BibleTime - the bible study program for KDE