[sword-devel] Ezra Project 0.8.0 released

Tobias Klein contact at tklein.info
Mon Jun 3 23:10:13 MST 2019


Thanks, Troy! It took me a while in the beginning to figure out how 
Sword uses its system/user config/data directories. Looks like I hadn't 
fully understood it yet at that time.
I'm planning to improve this in the next version of Ezra Project.

Best regards,
Tobias

On 04.06.19 01:17, Troy A. Griffitts wrote:
>
> PS.  I noticed that you installed a ~/.sword/sword.conf in my home 
> directory which sets the [Install] DataPath to this location.  This is 
> not correct.  This overrides my systemwide /etc/sword.conf file.  The 
> modules installed into ~/.sword/ are always augmented to the 
> SWORD_PATH, so this isn't necessary for your ~/.sword/ modules to be 
> included.  I found this because I couldn't get the locales to work 
> when I was typing my last email to you.  SWORD is installed on my 
> system with /etc/sword.conf:
>
> [Install]
> DataPath=/usr/share/sword/
>
> and hence my locales files were installed to:
>
> /usr/share/sword/locales.d/
>
> Your ~/.sword/sword.conf which overrode this setting bypassed 
> everything in /usr/share/sword, including locales.d/ so no locales 
> were available.
>
> Hope this helps too, :)
>
> Troy
>
>
> On 6/3/19 3:29 PM, Troy A. Griffitts wrote:
>>
>> A few comments inline:
>>
>> On 6/3/19 12:01 PM, Tobias Klein wrote:
>>>
>>> Hi Troy,
>>>
>>> Yay! I'm excited to hear that Ezra Project works for you and thanks 
>>> for this report! :)
>>> I'm glad I found some tools that allow packing of Electron 
>>> applications into *.debs and *.rpms rather easily.
>>> I now have a script that can create packages for Ubuntu 18.04 & 
>>> 19.04, Fedora 29 and CentOS 7 in one go, so for future updates it's 
>>> gonna be easier with the packaging. I may still add some other 
>>> distributions based on demand. The packaging for each of these 
>>> distributions is done in individual Docker containers, which also 
>>> really helped to get this done efficiently.
>>>
>>>> The repos list doesn't seem to show all the repos available from 
>>>> our registry. 
>>>
>>> Oh, ok. Interesting. I though I'm just showing the content of the 
>>> "master repo list".
>>> Which repos are shown on your computer and which are missing?
>>>
>> Yes, one repo I was thinking about has only ancient Greek: Deutche 
>> Bibelgesellschaft
>>
>>
>>>
>>> Essentially I'm just calling 
>>> installMgr->/refreshRemoteSourceConfiguration/(), then 
>>> installMgr->/saveInstallConf()/ and then I'm iterating over 
>>> /installMgr->sources/ to get the repositories.
>>>
>>>> Selecting CrossWire and choosing Greek, English, and Hebrew, I 
>>>> don't see the WHNU Greek module.
>>>>
>> Yes, I think we use grc for ancient Greek.
>>
>> Yes, we include a language list in our locales installed with SWORD.  
>> It is a pseudo-locale called "locales" and has a pretty exhaustive 
>> list of locale codes with their native language name, along with 
>> their English names.
>>
>> So, for example, you can make calls like:
>>
>> std::cout << LocaleMgr::getSystemLocaleMgr()->translate("locales", "grc")
>>
>>   << " (" << LocaleMgr::getSystemLocaleMgr()->translate("locales", 
>> "grc.en") << ")";  // should output Ἑλληνική (Ancient Greek (to 1453))
>>
>> A good test tool is sword/tests/localetest:
>>
>> ./localetest locales grc
>>
>>
>>>> Noticed the eBible.org repo only shows that is has like 74 modules 
>>>> available, but I think Michael has like 2000 or something :)
>>>>
>>> Currently only modules with "recognized languages" are shown.
>>> When loading the languages I'm separating them into "known" ones and 
>>> "unknown" ones using the ISO-639-1 Javascript module.
>>> https://www.npmjs.com/package/iso-639-1#validatecode
>>> Only the "known" languages end up being shown in the installation 
>>> wizard. I should change that and also show the other ones below the 
>>> recognized languages in the installation wizard.
>>>
>>>> I like that I can have multiple tabs of different Bibles pointing 
>>>> to different locations.
>>>>
>>>> Noticed Hebrew (module: WLC) is left justified.  You should be able 
>>>> to key off the config entry: Direction=RtoL
>>>>
>>> Thanks for the hint! Could I do that automatically based on certain 
>>> information in that bible's *.conf file?
>>>
>> Yes, exactly: Direction=RtoL
>>
>>
>> Hope this is helpful,
>>
>> Troy
>>
>>
>>>
>>>> I like that I can highlight multiple verse and then click a tag to 
>>>> add them to that tag.  I am not sure if they are tagged 
>>>> individually, or as a group, but regardless, they all seem to be 
>>>> tagged.
>>>>
>>> They are tagged individually in the database.
>>>
>>>> I am not sure how to show all the verses associated with one of my 
>>>> tags.
>>>>
>>> Click on "Select tag" (next to "Select book") in the menu above the 
>>> text display area and choose one. You can also choose multiple ones. 
>>> Then click on "Select tag" again to hide that dropdown.
>>>
>>>> I notice you're not showing all the books associated with the 
>>>> current module.
>>>>
>>>
>>> Yes, that's correct. At the moment the books shown is a static list. 
>>> The only thing dynamic is that within that static list Ezra Project 
>>> checks which of these books are actually available and disables the 
>>> links if they're not.
>>>
>>>> Great start!  Thanks for your work!  I am sure building up personal 
>>>> tab libraries of Bible topics and sharing those with others can be 
>>>> a wonderful way to study God's Word. 
>>>
>>> Thanks for the encouragement :). Sharing a tag library could be a 
>>> feature for the future. At the moment a "Word export" is 
>>> implemented, but that obviously is not the same as sharing a 
>>> technical database. I could implement a simple JSON or XML 
>>> export/import to support such a feature.
>>>
>>>
>>> There's other features besides tagging that I have on my mind. 
>>> Generally I want to support the user in creating material based on 
>>> the bible that is not "separate" (like separate text documents), but 
>>> rather directly linked with the text.
>>>
>>> Best regards,
>>> Tobias
>>>
>>>
>>> _______________________________________________
>>> sword-devel mailing list:sword-devel at 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 at 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 at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20190604/c60ecb8e/attachment-0001.html>


More information about the sword-devel mailing list