Re: [sword-devel] Xiphos 4.2.1

[Israel Dahl]

On 5/7/20 4:23 PM, Caleb Maclennan wrote:
> On Thu, May 7, 2020 at 11:12 PM Israel Dahl  wrote:
>> Do you maintain the AUR build scripts for Arch?
> I maintain the AUR builds for xiphos (and xiphos-git). 4.2.1 was
> released there already.
>
Excellent!  Thanks, I will try later on Manjaro!
>> And also do you think this will be able to get into Debian?
> I can't really speak to Debian. I think for Ubuntu the answer is no,
> but we're working on an official Xiphos PPA. I believe the packaging
> for that is basically the same as Debian. I believe there are some
> Debian folks here that can speak to that better though.
Yes, they use the same packaging system, unless you are talking about
newer formats Ubuntu uses like a 'snap' package (similar to flatpak if
you are familiar, and distantly related to the older AppImage)
> ___
> 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

Re: [sword-devel] Xiphos 4.2.1

[Caleb Maclennan]

On Thu, May 7, 2020 at 11:12 PM Israel Dahl  wrote:
> Do you maintain the AUR build scripts for Arch?

I maintain the AUR builds for xiphos (and xiphos-git). 4.2.1 was
released there already.

> And also do you think this will be able to get into Debian?

I can't really speak to Debian. I think for Ubuntu the answer is no,
but we're working on an official Xiphos PPA. I believe the packaging
for that is basically the same as Debian. I believe there are some
Debian folks here that can speak to that better though.

___
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] Xiphos 4.2.1

[Israel Dahl]

Do you maintain the AUR build scripts for Arch?
And also do you think this will be able to get into Debian?
Thanks for your work!

On 5/7/20 10:24 AM, Karl Kleinpaste wrote:
> https://github.com/crosswire/xiphos/releases/tag/4.2.1
>
> After a long dry spell, Xiphos is back with a new release. This is a
> release of many bug fixes and much re-structuring, especially for how
> the build system operates, an important factor for those in
> development. The older waf build system is gone, having been
> re-engineered from the ground up with cmake.
>
> User-visible changes regard crash-avoidance bugfixes and cosmetic
> matters: Corrected use of visuals in parallel window, corrected verse
> displays, status bar repair, corrected alternating fg/bg in parallel,
> improved/corrected spacing of Strong's and morphology with respect to
> mainline text, additions to the languages recognized in module
> displays, increased limits on book name length for exotic UTF-8
> languages (encodings too long), and some new and updated interface
> translations.
>
> I want most to thank the folks who have really stepped up in the last
> few months and especially the last couple weeks, making sure that the
> automatic build and release procedures are so robust.  Greg Hellings
> and Dom Corbex are the most obvious folks -- Dom gave us the
> re-engineered cmake-driven build system and Greg has done the bulk of
> the github-driven auto-build-and-release machinery.  There are many
> other contributors, and about 4 dozen issues have been closed.
>
> There are Windows installers and source tarballs for download.  Linux
> distributions should begin to gain updates soon.  There are Ubuntu PPA
> efforts underway due to Ubuntu no longer supporting our editor package
> (and the editor is under discussion for replacement, for many
> reasons).  See RELEASE-NOTES in /usr/share/doc/xiphos (for Windows,
> similarly under usual paths) for a list of issues addressed.
>
> --karl
>
> ___
> 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

Re: [sword-devel] Bishop 1.4.0 translation UPDATED2

[Caleb Maclennan]

On Thu, May 7, 2020 at 6:33 PM Troy A. Griffitts  wrote:
> I am learning more about gitlab as we go.  It appears that public
> projects on gitlab are browsable at the public/ link, e.g.,

No worries. Having maintained a couple Gitlab instances for a few
years I'm well aware of how much a bug-bear it can be to Administer. A
great system when it's working, but not the lightest thing to get off
the ground.

> https://git.crosswire.org/public

So I believe there is a mechanism where you can customize what shows
up on the login page, to which you should be able to add a "browse
public repos" link or something like that to the above URL.

I did receive your invitation, but I can't accept it. It's a catch 22
of some kind, when I click the link in the invite email I am told "To
accept this invitation, sign in." and shown a sign in form. If I could
sign in I wouldn't be needing the invitation.

___
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] Xiphos 4.2.1

[David Haslam]

Thanks Karl.

Well done everyone involved.

Is there any guidance for Windows users who had previously installed the x86 
edition of version 4.1.0 but would like to install the x64 edition as the 
update to version 4.2.1 ?

Will running the install work smoothly in this situation or should I first 
manually uninstall the x86 edition?

Best regards,

David H

Sent from ProtonMail Mobile

On Thu, May 7, 2020 at 15:24, Karl Kleinpaste  wrote:

> https://github.com/crosswire/xiphos/releases/tag/4.2.1
>
> After a long dry spell, Xiphos is back with a new release. This is a release 
> of many bug fixes and much re-structuring, especially for how the build 
> system operates, an important factor for those in development. The older waf 
> build system is gone, having been re-engineered from the ground up with cmake.
>
> User-visible changes regard crash-avoidance bugfixes and cosmetic matters: 
> Corrected use of visuals in parallel window, corrected verse displays, status 
> bar repair, corrected alternating fg/bg in parallel, improved/corrected 
> spacing of Strong's and morphology with respect to mainline text, additions 
> to the languages recognized in module displays, increased limits on book name 
> length for exotic UTF-8 languages (encodings too long), and some new and 
> updated interface translations.
>
> I want most to thank the folks who have really stepped up in the last few 
> months and especially the last couple weeks, making sure that the automatic 
> build and release procedures are so robust.  Greg Hellings and Dom Corbex are 
> the most obvious folks -- Dom gave us the re-engineered cmake-driven build 
> system and Greg has done the bulk of the github-driven auto-build-and-release 
> machinery.  There are many other contributors, and about 4 dozen issues have 
> been closed.
>
> There are Windows installers and source tarballs for download.  Linux 
> distributions should begin to gain updates soon.  There are Ubuntu PPA 
> efforts underway due to Ubuntu no longer supporting our editor package (and 
> the editor is under discussion for replacement, for many reasons).  See 
> RELEASE-NOTES in /usr/share/doc/xiphos (for Windows, similarly under usual 
> paths) for a list of issues addressed.
>
> --karl___
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] Versification Mapping

[Troy A. Griffitts]

Dear Tobias,

I would recommend KJVA, so you can get the Apocrypha.  I believe this is
the common base Костя uses to convert between systems.  Костя has done a
great job at optimization.  I've updated the verseconvert.cpp example to
allow ranges.  Here is a timing for the entire book of Psalms:

[scribe@localhost classes]$ time ./verseconvert Ps Wycliffe
FreGeneve1669 > /dev/null

real    0m0.195s
user    0m0.162s
sys    0m0.033s

My guess is that most of that time is simply with SWORD engine
initialization, discovering and opening my library.

Converting all verses in both Old and New Testament:

[scribe@localhost classes]$ time ./verseconvert Gen-Rev Wycliffe
FreGeneve1669 > /dev/null

real    0m0.645s
user    0m0.601s
sys    0m0.042s

Hope this is helpful.  Looking forward to your work.  We've had
discussions over the many years of our project about sharing bookmarking
and similar data between apps, but we all had different ideas of what
we'd like.  BibleCS (our Windows classic app) concentrates on allowing
verse groups and trees of groups so users can create trees of topic. 
Other apps extend this to allow comments and notes at each reference,
including a specific module name with the reference.  We've all had
different data formats for our bookmarking materials.  Since your app
centers on tagging (which I would place in the same category as
bookmarking), I would love to hear what you come up with and if it
encompasses everything which all of our frontends desire to provide
their users.  Maybe we can make another go at a shared "bookmarking" or
"tagging" concept and push that concept back into the engine so all app
can share and take advantage of your functionality, if you'd be willing.

Troy


On 5/7/20 9:07 AM, Tobias Klein wrote:
> Thanks Troy!
>
> Besides comparing verses in different translations my primary use case
> is the following:
> Establish „unique verse reference“ objects that I can use to assign
> tags independent of the specific translation.
>
> Currently I’m doing this by determining the „absolute verse number“
> for the respective verse I’m tagging.
> Then at the point when the „verse reference object“ (a database entry)
> is created, the absolute verse number both for English and Hebrew
> versification are determined based on my mapping tables.
>
> Then, when looking up tags for the currently selected verses I can map
> the correct „verse reference object“ to each verse in the currently
> selected translation (based on the respective absolute verse number).
>
> If I migrate to the Sword VerseKey approach I would change my concept
> in the following way:
>
> 1) Use KJV verse references (chapter + verse) as unique identifiers
> for all „abstract verse reference“ objects. (Does KJV make sense as a
> „ reference versification“)
> 2) When opening a translation that does not follow the KJV theme - map
> all verse references to the KJV variants and use the KJV verse
> references (chapter + verse) as a key to find the correct „verse
> reference“ objects in my database.
>
> What’s the performance of the SWORD VerseKey based mapping function
> you described below?
>
> How would this work if I need to perform a mapping operation on all
> verses of a large book like Psalms? (2461 verses).
> Would this operation come back in less than a second?
>
> If not I would have to think about some caching mechanism in my verse
> reference objects. Currently I’m caching the absolute verse numbers
> for English and Hebrew for all tagged verse references.
> With the new concept I could cache the actual chapter/verse references
> for all known versification systems.
>
> Thanks for your help on this!
>
> Best regards,
> Tobias
>
>> Am 06.05.2020 um 18:47 schrieb Troy A. Griffitts
>> mailto:scr...@crosswire.org>>:
>>
>> Yes, as Peter has pointed out, SWORD includes a facility for mapping,
>> graciously contributed by Костя Маслюк  and
>> should "just work" when setting a key from one module to another,
>> e.g, kjv->setKey(wycliffe->getKey()).  It's not quite that simple,
>> because there isn't always a 1:1 mapping, so if you want full
>> support, you'll have to see if a bound is set on the receiving
>> module's key.
>>
>> The mapping data, as with everything, is not exhaustive, but we'd
>> certainly like to extend it to meet cases which you run into which
>> aren't yet supported.
>> You can see it taken advantage of in example
>> sword/examples/tasks/parallelbibles.cpp, but I've just added a
>> concise example which shows how to use it:
>>
>> http://crosswire.org/svn/sword/trunk/examples/classes/verseconvert.cpp
>>
>> Which outputs, e.g. 
>> ./verseconvert Ps.43.22 Wycliffe FreGeneve1669
>>
>> Psalms 43:22 (Wycliffe) => Psalms 44:21-Psalms 44:22 (FreGeneve1669)
>>
>> Hope this helps,
>> Troy
>>
>>
>>
>>
>>
>> On 5/6/20 7:07 AM, ref...@gmx.net wrote:
>>> I think transparent mapping has been for a while now included in the
>>> library. I am not sure how to make it work, but I do think it is
>>> there and 

Re: [sword-devel] Versification Mapping

[Tobias Klein]

Thanks Troy!

Besides comparing verses in different translations my primary use case is the 
following:
Establish „unique verse reference“ objects that I can use to assign tags 
independent of the specific translation.

Currently I’m doing this by determining the „absolute verse number“ for the 
respective verse I’m tagging.
Then at the point when the „verse reference object“ (a database entry) is 
created, the absolute verse number both for English and Hebrew versification 
are determined based on my mapping tables.

Then, when looking up tags for the currently selected verses I can map the 
correct „verse reference object“ to each verse in the currently selected 
translation (based on the respective absolute verse number).

If I migrate to the Sword VerseKey approach I would change my concept in the 
following way:

1) Use KJV verse references (chapter + verse) as unique identifiers for all 
„abstract verse reference“ objects. (Does KJV make sense as a „ reference 
versification“)
2) When opening a translation that does not follow the KJV theme - map all 
verse references to the KJV variants and use the KJV verse references (chapter 
+ verse) as a key to find the correct „verse reference“ objects in my database.

What’s the performance of the SWORD VerseKey based mapping function you 
described below?

How would this work if I need to perform a mapping operation on all verses of a 
large book like Psalms? (2461 verses).
Would this operation come back in less than a second?

If not I would have to think about some caching mechanism in my verse reference 
objects. Currently I’m caching the absolute verse numbers for English and 
Hebrew for all tagged verse references.
With the new concept I could cache the actual chapter/verse references for all 
known versification systems.

Thanks for your help on this!

Best regards,
Tobias

> Am 06.05.2020 um 18:47 schrieb Troy A. Griffitts :
> 
> Yes, as Peter has pointed out, SWORD includes a facility for mapping, 
> graciously contributed by Костя Маслюк  
>  and should "just work" when setting a key 
> from one module to another, e.g, kjv->setKey(wycliffe->getKey()).  It's not 
> quite that simple, because there isn't always a 1:1 mapping, so if you want 
> full support, you'll have to see if a bound is set on the receiving module's 
> key.
> 
> The mapping data, as with everything, is not exhaustive, but we'd certainly 
> like to extend it to meet cases which you run into which aren't yet supported.
> You can see it taken advantage of in example 
> sword/examples/tasks/parallelbibles.cpp, but I've just added a concise 
> example which shows how to use it:
> 
> http://crosswire.org/svn/sword/trunk/examples/classes/verseconvert.cpp 
> 
> 
> Which outputs, e.g. 
> ./verseconvert Ps.43.22 Wycliffe FreGeneve1669
> 
> Psalms 43:22 (Wycliffe) => Psalms 44:21-Psalms 44:22 (FreGeneve1669)
> 
> Hope this helps,
> Troy
> 
> 
> 
> 
> 
> On 5/6/20 7:07 AM, ref...@gmx.net  wrote:
>> I think transparent mapping has been for a while now included in the 
>> library. I am not sure how to make it work, but I do think it is there and 
>> functioning. 
>> 
>> Peter
>> 
>> Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
>> 
>> 
>>  Original Message 
>> Subject: Re: [sword-devel] Versification Mapping
>> From: Jamie 
>> To: 'SWORD Developers' Collaboration Forum' 
>> CC: 
>> 
>> 
>> Hi Tobias,
>>  
>> Not sure that this exactly answers your question, but just in case it’s 
>> relevant, Tyndale House have various public domain information available, 
>> including material on alternative versification schemes.  The 
>> reversification material gives details of how to map LXX, MT and Vulgate 
>> schemes on to NRSVA (and also addresses some other schemes which are perhaps 
>> less frequently encountered).  It also caters for common variants which 
>> basically follow one of these schemes, but which have certain verses split 
>> up into subverses.  You can find the data at :-
>>  
>> https://github.com/tyndale/STEPBible-Data/blob/master/TVTMS%20-%20Tyndale%20Versification%20Traditions%20with%20Methodology%20for%20Standardisation%20for%20Eng%2BHeb%2BLat%2BGrk%2BOthers%20-%20TyndaleHouse.com%20STEPBible.org%20CC%20BY-NC.txt
>>  
>> 
>>  
>> If you do want to make use of it, I’d be very happy to try to answer any 
>> questions.
>>  
>> Regards,
>>  
>> ARA “Jamie” Jamieson
>>  
>>  
>>  
>> From: Tobias Klein [mailto:cont...@tklein.info ] 
>> Sent: 05 May 2020 21:19
>> To: SWORD Developers' Collaboration Forum  
>> 
>> 

Re: [sword-devel] Bishop 1.4.0 translation UPDATED2

[Troy A. Griffitts]

Dear Caleb,

I am learning more about gitlab as we go.  It appears that public
projects on gitlab are browsable at the public/ link, e.g.,

https://git.crosswire.org/public

Invitation sent.

Troy


On 5/7/20 12:27 AM, Caleb Maclennan wrote:
> As Greg mentioned, the root of the Gitlab instance redirects to the
> login. There are actually several projects that are publicly
> browseable but you can only start doing so with a deep link to one of
> them.
>
> I would appreciate an invite as well, if nothing else to participate
> in issues on Bishop!
>
> On Thu, Apr 2, 2020 at 7:18 PM Greg Hellings  wrote:
>>
>>
>> On Wed, Apr 1, 2020 at 10:04 PM Troy A. Griffitts  
>> wrote:
>>> Our Gitlab instance is available for any official CrossWire projects who 
>>> wish to use it.  We don't have the resources to manage open subscriptions 
>>> but any CrossWire project wishing to make our gitlab their home is welcome 
>>> to an account and to send invites to their contributors.
>>>
>>> We backup all repos regularly and multiple backups of a sprawling public 
>>> gitlab instance would quickly fill our disk capacity.  Github.com is great 
>>> for public sandboxing, personal projects, and even importing and working on 
>>> project with upstream from out gitlab instance.  You can directly import on 
>>> Github by selecting  [+], Import repository, and then specify one of our 
>>> gitlab project clone URLs.  Of course, if you are a regular contributor to 
>>> a project, you are welcome to an account on our gitlab instance for that 
>>> purpose.
>>>
>>> Hope this makes sense,
>> It makes sense, and it's exactly what I would expect for a privately hosted 
>> instance. However, I think the instance is more locked down than you intend. 
>> Any URL leading into git.crosswire.org, including the "/" path, redirects me 
>> to login. So without an account I can't even see what code is up there.
>>
>> --Greg
>>> Troy
>>>
>>>
>>> On 4/1/20 10:14 AM, Greg Hellings wrote:
>>>
>>> How does one sign up for access to our gitlab instance?
>>>
>>> --Greg
>>>
>>> On Wed, Apr 1, 2020 at 11:21 AM Troy A. Griffitts  
>>> wrote:
 I hope everyone isn't going too crazy sitting at home.

 I'm about to push this release of Bishop out.  If anyone has anything else 
 they'd like to get into the release, please send me a merge request on our 
 repo:

 https://git.crosswire.org/main/bishop

 or send me an email with your update.

 Thank you for all the feedback, translations, testing, and encouragement!

 May God use this to draw many to Himself,

 Troy



 On 3/21/20 4:22 AM, Troy A. Griffitts wrote:

 Updated list of new strings (comment lines start with # and don't need to 
 be translated):

 Show Gospel Parallels=Show Gospel Parallels
 # This option is used as a choice for Study Bible to use for Verse Study, 
 Word Study, etc.
 # First Active means that the first Bible selected in the 3 display 
 dropdowns which has language data will be used.
 # This choice says, "I don't wish to choose a specific Bible, just use the 
 first one I am currently diplaying which has the ability."
 First Active=First Active
 Nothing to display.=Nothing to display.
 No Modules Installed=No Modules Installed
 No Modules Available.  Try pressing the [↻] button.=No Modules Available.  
 Try pressing the [↻] button.
 You have received an application update since your last run.=You have 
 received an application update since your last run.
 Would you like to check for updates to your Bibles and other study 
 resources?=Would you like to check for updates to your Bibles and other 
 study resources?
 Update Resources=Update Resources
 Installation Sources=Installation Sources
 Updates Available=Updates Available
 No installed resources have updates available. New study resources can be 
 added by first selecting an installation source at the top.=No installed 
 resources have updates available. New study resources can be added by 
 first selecting an installation source at the top.
 Below is a list of installed resources which have updates available. Click 
 on any row to update the resource.=Below is a list of installed resources 
 which have updates available. Click on any row to update the resource.
 You have asked to show Gospel parallels. For this feature, we need to 
 download a small set of data.  Is this OK?=You have asked to show Gospel 
 parallels. For this feature, we need to download a small set of data.  Is 
 this OK?
 Install Module=Install Module
 Font: Reading=Font: Reading
 Font: App=Font: App

 On 3/21/20 3:42 AM, Cyrille wrote:

 Please add Fonts: Reading and Fonts: App to the list. I'm waiting for them 
 before a new merge request.

 Le 21/03/2020 à 11:38, Troy A. Griffitts a écrit :

 Updated list of 

[sword-devel] Xiphos 4.2.1

[Karl Kleinpaste]

https://github.com/crosswire/xiphos/releases/tag/4.2.1

After a long dry spell, Xiphos is back with a new release. This is a
release of many bug fixes and much re-structuring, especially for how
the build system operates, an important factor for those in development.
The older waf build system is gone, having been re-engineered from the
ground up with cmake.

User-visible changes regard crash-avoidance bugfixes and cosmetic
matters: Corrected use of visuals in parallel window, corrected verse
displays, status bar repair, corrected alternating fg/bg in parallel,
improved/corrected spacing of Strong's and morphology with respect to
mainline text, additions to the languages recognized in module displays,
increased limits on book name length for exotic UTF-8 languages
(encodings too long), and some new and updated interface translations.

I want most to thank the folks who have really stepped up in the last
few months and especially the last couple weeks, making sure that the
automatic build and release procedures are so robust.  Greg Hellings and
Dom Corbex are the most obvious folks -- Dom gave us the re-engineered
cmake-driven build system and Greg has done the bulk of the
github-driven auto-build-and-release machinery.  There are many other
contributors, and about 4 dozen issues have been closed.

There are Windows installers and source tarballs for download.  Linux
distributions should begin to gain updates soon.  There are Ubuntu PPA
efforts underway due to Ubuntu no longer supporting our editor package
(and the editor is under discussion for replacement, for many reasons). 
See RELEASE-NOTES in /usr/share/doc/xiphos (for Windows, similarly under
usual paths) for a list of issues addressed.

--karl
___
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] Bishop 1.4.0 translation UPDATED2

[Caleb Maclennan]

As Greg mentioned, the root of the Gitlab instance redirects to the
login. There are actually several projects that are publicly
browseable but you can only start doing so with a deep link to one of
them.

I would appreciate an invite as well, if nothing else to participate
in issues on Bishop!

On Thu, Apr 2, 2020 at 7:18 PM Greg Hellings  wrote:
>
>
>
> On Wed, Apr 1, 2020 at 10:04 PM Troy A. Griffitts  
> wrote:
>>
>> Our Gitlab instance is available for any official CrossWire projects who 
>> wish to use it.  We don't have the resources to manage open subscriptions 
>> but any CrossWire project wishing to make our gitlab their home is welcome 
>> to an account and to send invites to their contributors.
>>
>> We backup all repos regularly and multiple backups of a sprawling public 
>> gitlab instance would quickly fill our disk capacity.  Github.com is great 
>> for public sandboxing, personal projects, and even importing and working on 
>> project with upstream from out gitlab instance.  You can directly import on 
>> Github by selecting  [+], Import repository, and then specify one of our 
>> gitlab project clone URLs.  Of course, if you are a regular contributor to a 
>> project, you are welcome to an account on our gitlab instance for that 
>> purpose.
>>
>> Hope this makes sense,
>
> It makes sense, and it's exactly what I would expect for a privately hosted 
> instance. However, I think the instance is more locked down than you intend. 
> Any URL leading into git.crosswire.org, including the "/" path, redirects me 
> to login. So without an account I can't even see what code is up there.
>
> --Greg
>>
>> Troy
>>
>>
>> On 4/1/20 10:14 AM, Greg Hellings wrote:
>>
>> How does one sign up for access to our gitlab instance?
>>
>> --Greg
>>
>> On Wed, Apr 1, 2020 at 11:21 AM Troy A. Griffitts  
>> wrote:
>>>
>>> I hope everyone isn't going too crazy sitting at home.
>>>
>>> I'm about to push this release of Bishop out.  If anyone has anything else 
>>> they'd like to get into the release, please send me a merge request on our 
>>> repo:
>>>
>>> https://git.crosswire.org/main/bishop
>>>
>>> or send me an email with your update.
>>>
>>> Thank you for all the feedback, translations, testing, and encouragement!
>>>
>>> May God use this to draw many to Himself,
>>>
>>> Troy
>>>
>>>
>>>
>>> On 3/21/20 4:22 AM, Troy A. Griffitts wrote:
>>>
>>> Updated list of new strings (comment lines start with # and don't need to 
>>> be translated):
>>>
>>> Show Gospel Parallels=Show Gospel Parallels
>>> # This option is used as a choice for Study Bible to use for Verse Study, 
>>> Word Study, etc.
>>> # First Active means that the first Bible selected in the 3 display 
>>> dropdowns which has language data will be used.
>>> # This choice says, "I don't wish to choose a specific Bible, just use the 
>>> first one I am currently diplaying which has the ability."
>>> First Active=First Active
>>> Nothing to display.=Nothing to display.
>>> No Modules Installed=No Modules Installed
>>> No Modules Available.  Try pressing the [↻] button.=No Modules Available.  
>>> Try pressing the [↻] button.
>>> You have received an application update since your last run.=You have 
>>> received an application update since your last run.
>>> Would you like to check for updates to your Bibles and other study 
>>> resources?=Would you like to check for updates to your Bibles and other 
>>> study resources?
>>> Update Resources=Update Resources
>>> Installation Sources=Installation Sources
>>> Updates Available=Updates Available
>>> No installed resources have updates available. New study resources can be 
>>> added by first selecting an installation source at the top.=No installed 
>>> resources have updates available. New study resources can be added by first 
>>> selecting an installation source at the top.
>>> Below is a list of installed resources which have updates available. Click 
>>> on any row to update the resource.=Below is a list of installed resources 
>>> which have updates available. Click on any row to update the resource.
>>> You have asked to show Gospel parallels. For this feature, we need to 
>>> download a small set of data.  Is this OK?=You have asked to show Gospel 
>>> parallels. For this feature, we need to download a small set of data.  Is 
>>> this OK?
>>> Install Module=Install Module
>>> Font: Reading=Font: Reading
>>> Font: App=Font: App
>>>
>>> On 3/21/20 3:42 AM, Cyrille wrote:
>>>
>>> Please add Fonts: Reading and Fonts: App to the list. I'm waiting for them 
>>> before a new merge request.
>>>
>>> Le 21/03/2020 à 11:38, Troy A. Griffitts a écrit :
>>>
>>> Updated list of new strings (comment lines start with # and don't need to 
>>> be translated):
>>>
>>> Show Gospel Parallels=Show Gospel Parallels
>>> # This option is used as a choice for Study Bible to use for Verse Study, 
>>> Word Study, etc.
>>> # First Active means that the first Bible selected in the 3 display 
>>> dropdowns which has language data