Re: [sword-devel] NASB, NBLA, LBLA

[Tobias Klein]

These are great news, Troy! I've been a happy NASB reader when studying 
the Bible in English!


Thanks for your efforts on this long road and thanks to Lockman! I 
remember writing them an email ten years ago asking about the copyright 
of the NASB. To see now that this translation becomes available as a 
free SWORD module is really awesome! This will enhance my own bible 
study and the study of many people I know.


Tobias

On 3/12/20 5:42 AM, Troy A. Griffitts wrote:

It's been a long long road, but after much negotiation and many
volunteers contributing to the conversion efforts, we have finally been
granted permission to distribute Lockman's:

New American Standard Bible (NASB)
Nueva Biblia de las Américas (NBLA)
La Biblia de las Américas (LBLA)

Additionally, a gracious gift from Lockman, they have granted permission
for CrossWire to distribute all 3 of these modules unlocked, for free.

The modules are immediately available on swordweb:

http://www.crosswire.org/study/parallelstudy.jsp?del=all=NASB=LBLA=NBLA=Jn.3.16

And have been updated in the "Lockman Foundation" repository.  Please
refresh your repository in your favorite frontend to be sure you have
the latest module configurations.

If you have previously installed any of these modules using the test
unlock keys, you may need to clear out the key for them to work property
in your frontend.

May God use these resources to draw people to Himself.

Praise Him for always providing cool things,

Troy


___
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] PocketSword status

[David Haslam]

AFAIK there’s no module conf key that works as the opposite to Obsoletes=

David

Sent from ProtonMail Mobile

On Fri, Mar 13, 2020 at 20:30, Michael H  wrote:

> Is it possible that the modules and .conf can sunset ... pointing across 
> repositories to the new replacement?  I know there is some facility to name a 
> successor module in the conf/updating process, but can it name one on another 
> site?
>
> If that is possible, Some of the out of date editions of the WEB should be 
> removed from Crosswire (WMB, etc.) It might help the remaining editions get 
> updated with more frequency.
>
> On the other side of that, ebible has added several works from Crosswire onto 
> it's Web directory and I see at least some of these on the ebible sword repo. 
>  However, As far as I can tell, these modules are not actually changing 
> visible content every time they update. It's more that defects introduced by 
> the transfer to ebible have been eliminated, so that they now represent a 
> truer copy of the original at Crosswire. These shouldn't be removed from 
> either, but maybe the ebible repo could be clearer that it's presenting 
> content from Crosswire, and not changing it.
>
> Is it possible the ebible repository could be divided into sub repos, like 
> the crosswire site has ?  It would be nice to select ebible-english, or 
> ebible-americas and have a list of only 20 or 100 languages to scroll 
> through, vs. selecting ebible creates 1000 entries to search in Bibletime, 
> which seems to have difficulty with that number... so the screen updates get 
> 10 second to a couple minutes behind the keystrokes and mouse clicks when 
> I've selected ebible for downloading?
>
> On Fri, Mar 13, 2020 at 3:11 AM Cyrille  wrote:
>
>> Dear all,
>> Actually my worry was about a question between the module team. We have
>> duplicated modules, in Crosswire and in ebible.org. Often the ebible.org
>> are updated and not in Crosswire. And we are very slow to update the new
>> module in Crosswire. Then I proposed to remove in the Crosswire repo,
>> all the old modules with issue reported on the bug tracker. But the
>> question was: What to do if the users don't know how to change the repo,
>> as it happened in the other post on this list, some of us didn't know
>> how to change for IBT in Xiphos.
>> I Bibletime, Andbible and Bishop, the repositories are updated all
>> together, but not in Xiphos. I opened an issue about this on the xiphos git.
>> For this reason I proposed this for Swordpocket, even if it seems to be
>> more or less easier than for Xiphos.
>>
>> Br Cyrille
>>
>> Le 13/03/2020 à 04:14, Nic Carter a écrit :
>>> On the downloads screen, tap on the folder icon in the top right corner, 
>>> then refresh the source list.
>>> That will show all servers in the Master Server List.
>>>
>>> Sent from my phone, hence this email may be short...
>>>
 On 13/03/2020, at 09:24, Cyrille  wrote:

 Hi Michael,
 Maybe add the updating of all the repositories at once, as with Andbible
 and Bishop. This will help users who don't know they are other
 repository as ebible.org...
 My 2 cents :)

 Br Cyrille

> Le 12/03/2020 à 20:30, Michael Johnson a écrit :
> Hello, my brothers and sisters in Christ.
>
> I just thought I should post a status on PocketSword work. I have started 
> on updating it, but haven't yet gotten to a stable point for testing 
> using Test Flight. Right now, it is, unfortunately, on hold, as I have 
> another task in the foreground. I finished the main editing of the World 
> English Bible, with the exception of still correcting the occasional rare 
> typo. (I found one this morning in Ezekiel.) My foreground task at the 
> moment is integrating SILE into Haiola for better PDF generation, 
> especially
> with mixed complex scripts. After that is done, I hope to focus on 
> PocketSword. In its new incarnation, it will generate its own indexes, 
> and won't need special server support for that. I'll also fix the key 
> problem for when a module goes from locked to unlocked, which of course, 
> will happen as copyrights expire and/or special permission is granted.
>
> Thank you for your patience.
>

 ___
 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
>>
>> ___
>> sword-devel mailing list: sword-devel@crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above 

Re: [sword-devel] PocketSword status

[Michael Johnson]

I think that dividing the eBible repository into sub repos is probably not the 
best solution to the problem of finding the particular translation(s) you want 
among nearly a thousand others. That actually becomes a front end problem, 
where better ways of filtering, sorting, and presenting lists by language, 
language autonym, continent, country, etc. could be helpful. Sub repos add 
problems of their own by making it harder to find certain translations.

On 3/13/20 10:30 AM, Michael H wrote:
> Is it possible that the modules and .conf can sunset ... pointing across 
> repositories to the new replacement?  I know there is some facility to name a 
> successor module in the conf/updating process, but can it name one on another 
> site?
>
> If that is possible, Some of the out of date editions of the WEB should be 
> removed from Crosswire (WMB, etc.) It might help the remaining editions get 
> updated with more frequency. 
>
> On the other side of that, ebible has added several works from Crosswire onto 
> it's Web directory and I see at least some of these on the ebible sword repo. 
>  However, As far as I can tell, these modules are not actually changing 
> visible content every time they update. It's more that defects introduced by 
> the transfer to ebible have been eliminated, so that they now represent a 
> truer copy of the original at Crosswire. These shouldn't be removed from 
> either, but maybe the ebible repo could be clearer that
> it's presenting content from Crosswire, and not changing it. 
>
> Is it possible the ebible repository could be divided into sub repos, like 
> the crosswire site has ?  It would be nice to select ebible-english, or 
> ebible-americas and have a list of only 20 or 100 languages to scroll 
> through, vs. selecting ebible creates 1000 entries to search in Bibletime, 
> which seems to have difficulty with that number... so the screen updates get 
> 10 second to a couple minutes behind the keystrokes and mouse clicks when 
> I've selected ebible for downloading? 
>
>
>
> On Fri, Mar 13, 2020 at 3:11 AM Cyrille  > wrote:
>
> Dear all,
> Actually my worry was about a question between the module team. We have
> duplicated modules, in Crosswire and in ebible.org . 
> Often the ebible.org 
> are updated and not in Crosswire. And we are very slow to update the new
> module in Crosswire. Then I proposed to remove in the Crosswire repo,
> all the old modules with issue reported on the bug tracker. But the
> question was: What to do if the users don't know how to change the repo,
> as it happened in the other post on this list, some of us didn't know
> how to change for IBT in Xiphos.
> I Bibletime, Andbible and Bishop, the repositories are updated all
> together, but not in Xiphos. I opened an issue about this on the xiphos 
> git.
> For this reason I proposed this for Swordpocket, even if it seems to be
> more or less easier than for Xiphos.
>
> Br Cyrille
>
> Le 13/03/2020 à 04:14, Nic Carter a écrit :
> > On the downloads screen, tap on the folder icon in the top right 
> corner, then refresh the source list.
> > That will show all servers in the Master Server List.
> >
> > Sent from my phone, hence this email may be short...
> >
> >> On 13/03/2020, at 09:24, Cyrille  > wrote:
> >>
> >> Hi Michael,
> >> Maybe add the updating of all the repositories at once, as with 
> Andbible
> >> and Bishop. This will help users who don't know they are other
> >> repository as ebible.org...
> >> My 2 cents :)
> >>
> >> Br Cyrille
> >>
> >>> Le 12/03/2020 à 20:30, Michael Johnson a écrit :
> >>> Hello, my brothers and sisters in Christ.
> >>>
> >>> I just thought I should post a status on PocketSword work. I have 
> started on updating it, but haven't yet gotten to a stable point for testing 
> using Test Flight. Right now, it is, unfortunately, on hold, as I have 
> another task in the foreground. I finished the main editing of the World 
> English Bible, with the exception of still correcting the occasional rare 
> typo. (I found one this morning in Ezekiel.) My foreground task at the moment 
> is integrating SILE into Haiola for better PDF generation,
> especially
> >>> with mixed complex scripts. After that is done, I hope to focus on 
> PocketSword. In its new incarnation, it will generate its own indexes, and 
> won't need special server support for that. I'll also fix the key problem for 
> when a module goes from locked to unlocked, which of course, will happen as 
> copyrights expire and/or special permission is granted.
> >>>
> >>> Thank you for your patience.
> >>>
> >>
> >> ___
> >> sword-devel mailing list: sword-devel@crosswire.org 
> 
> 

Re: [sword-devel] PocketSword status

[Michael H]

Is it possible that the modules and .conf can sunset ... pointing across
repositories to the new replacement?  I know there is some facility to name
a successor module in the conf/updating process, but can it name one on
another site?

If that is possible, Some of the out of date editions of the WEB should be
removed from Crosswire (WMB, etc.) It might help the remaining editions get
updated with more frequency.

On the other side of that, ebible has added several works from Crosswire
onto it's Web directory and I see at least some of these on the ebible
sword repo.  However, As far as I can tell, these modules are not actually
changing visible content every time they update. It's more that defects
introduced by the transfer to ebible have been eliminated, so that they now
represent a truer copy of the original at Crosswire. These shouldn't be
removed from either, but maybe the ebible repo could be clearer that it's
presenting content from Crosswire, and not changing it.

Is it possible the ebible repository could be divided into sub repos, like
the crosswire site has ?  It would be nice to select ebible-english, or
ebible-americas and have a list of only 20 or 100 languages to scroll
through, vs. selecting ebible creates 1000 entries to search in Bibletime,
which seems to have difficulty with that number... so the screen updates
get 10 second to a couple minutes behind the keystrokes and mouse clicks
when I've selected ebible for downloading?



On Fri, Mar 13, 2020 at 3:11 AM Cyrille  wrote:

> Dear all,
> Actually my worry was about a question between the module team. We have
> duplicated modules, in Crosswire and in ebible.org. Often the ebible.org
> are updated and not in Crosswire. And we are very slow to update the new
> module in Crosswire. Then I proposed to remove in the Crosswire repo,
> all the old modules with issue reported on the bug tracker. But the
> question was: What to do if the users don't know how to change the repo,
> as it happened in the other post on this list, some of us didn't know
> how to change for IBT in Xiphos.
> I Bibletime, Andbible and Bishop, the repositories are updated all
> together, but not in Xiphos. I opened an issue about this on the xiphos
> git.
> For this reason I proposed this for Swordpocket, even if it seems to be
> more or less easier than for Xiphos.
>
> Br Cyrille
>
> Le 13/03/2020 à 04:14, Nic Carter a écrit :
> > On the downloads screen, tap on the folder icon in the top right corner,
> then refresh the source list.
> > That will show all servers in the Master Server List.
> >
> > Sent from my phone, hence this email may be short...
> >
> >> On 13/03/2020, at 09:24, Cyrille  wrote:
> >>
> >> Hi Michael,
> >> Maybe add the updating of all the repositories at once, as with Andbible
> >> and Bishop. This will help users who don't know they are other
> >> repository as ebible.org...
> >> My 2 cents :)
> >>
> >> Br Cyrille
> >>
> >>> Le 12/03/2020 à 20:30, Michael Johnson a écrit :
> >>> Hello, my brothers and sisters in Christ.
> >>>
> >>> I just thought I should post a status on PocketSword work. I have
> started on updating it, but haven't yet gotten to a stable point for
> testing using Test Flight. Right now, it is, unfortunately, on hold, as I
> have another task in the foreground. I finished the main editing of the
> World English Bible, with the exception of still correcting the occasional
> rare typo. (I found one this morning in Ezekiel.) My foreground task at the
> moment is integrating SILE into Haiola for better PDF generation, especially
> >>> with mixed complex scripts. After that is done, I hope to focus on
> PocketSword. In its new incarnation, it will generate its own indexes, and
> won't need special server support for that. I'll also fix the key problem
> for when a module goes from locked to unlocked, which of course, will
> happen as copyrights expire and/or special permission is granted.
> >>>
> >>> Thank you for your patience.
> >>>
> >>
> >> ___
> >> 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
>
>
>
> ___
> 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] PocketSword status

[Cyrille]

Hi,
Thank for this reflexions.

Le 13/03/2020 à 19:33, Michael Johnson a écrit :
> I plan to update PocketSword so that it draws from all official repositories, 
> by default, much like AndBible does.
>
> Duplicating works in repositories is helpful, perhaps, for front ends that 
> only look at one repository at a time, especially if the work is kept up to 
> date in both repositories. When presented with an aggregate list, the user 
> would see duplicate or near-duplicate entries. If the UI displays repository 
> source and date of last update, as well as a full description of the module, 
> this could help the user decide which one(s) to choose.
>
> As far as eBible.org goes, removing a work from the repository is actually 
> more work than keeping it there, because of the way the automation is set up. 
> Therefore I'm disinclined to remove works unless there is a valid reason 
> other than duplication alone.
I was not speaking about removing on eBible.org but on Crosswire, and
not all the duplicated modules, but only modules which have issues on
the bug tracker, that means, Arab, Hindi an Chinese modules. The main
problem is people who can update the module are very busy, or don't have
time to do it. So it takes a long time before an update is offered. Some
modules have important issue, as Chinese.
>
> For the World English Bible and its variants (American/British, 
> standard/Messianic, with/without DC/Apocrypha), the eBible.org repository is 
> the authoritative source with the most current copy. The same is true for 
> hundreds of other translations. That older revisions are "out there" 
> including in Crosswire Main doesn't bother me, really, because the 
> differences generally don't affect meaning, but the English may be less up to 
> date. Staying updated, of course, is better. I'm disinclined to mark any 
> eBible.org
This would be only if we decide to remove a module on Crosswire main,
because people will not know that the module is now in the ebible.org repo.
> translations as obsoleting anything in another repository, absent a specific 
> request from the appropriate pumpkin holder for that repository, lest 
> confusion result. There are, of course, some translations where Crosswire 
> Main is more authoritative. There are also cases where one repository has 
> permission to distribute but the other one doesn't. We have an architecture 
> that supports multiple repositories, although it does look like an 
> afterthought. Still, we can make it work better, either by coming up with
> standard ways of aggregating them better in the API, or maybe we keep leaving 
> it up to each front end.
>
> Supporting multiple repositories is actually a good thing in terms of 
> resilience against server outages, censorship, etc. It also gives more 
> localized control to the various sources of modules. Otherwise, there would 
> be a temptation to make one big super-repository. Maybe that isn't a terrible 
> idea if it were just an automated aggregate mirror of all of the others, and 
> if it could be done without violating copyright agreements. For fault 
> tolerance and improved bandwidth, there could be more than one such
> super-repository.
Good point. And I agree also with the idea of multiple repositories.
>
> Any thoughts?
My two cents 
>
> On 3/13/20 7:56 AM, Cyrille wrote:
>>
>> Le 13/03/2020 à 12:55, David Haslam a écrit :
>>> Cyrille,
>>>
>>> I’m not in favour of removing modules from CrossWire simply because one of 
>>> the affiliated repositories has a similar module.
>> Why not?
>>> Nor should it ever be expected that a module published by eBible.org would 
>>> include an Obsoletes key with one of CrossWire’s modules as the parameter.
>> Idem why not?
>>>
>>>
>>> Regards,
>>>
>>> David
>>>
>>> Sent from ProtonMail Mobile
>>>
>>>
>>> On Fri, Mar 13, 2020 at 08:11, Cyrille >> > wrote:
 Dear all,
 Actually my worry was about a question between the module team. We have
 duplicated modules, in Crosswire and in ebible.org. Often the ebible.org
 are updated and not in Crosswire. And we are very slow to update the new
 module in Crosswire. Then I proposed to remove in the Crosswire repo,
 all the old modules with issue reported on the bug tracker. But the
 question was: What to do if the users don't know how to change the repo,
 as it happened in the other post on this list, some of us didn't know
 how to change for IBT in Xiphos.
 I Bibletime, Andbible and Bishop, the repositories are updated all
 together, but not in Xiphos. I opened an issue about this on the xiphos 
 git.
 For this reason I proposed this for Swordpocket, even if it seems to be
 more or less easier than for Xiphos.

 Br Cyrille

 Le 13/03/2020 à 04:14, Nic Carter a écrit :
> On the downloads screen, tap on the folder icon in the top right corner, 
> then refresh the source list.
> That will show all servers in the Master 

Re: [sword-devel] NASB, NBLA, LBLA

[John Dudeck]

Aha! I looked at my phone and there was a pending update for AndBible. Ran the update and now NASB is there.


Still waiting for configurable repositories...


John






David Haslam wrote:


See the And Bible Facebook page.


NASB is now available for free in And Bible due to Crosswire's new distribution contract! To use NASB (or LBLA or NBLA), please 
update to the latest version of And Bible first; update is now available in Play Store (3.2.343).


Sent from ProtonMail Mobile





On Fri, Mar 13, 2020 at 18:26, John Dudeck <
john.dud...@sim.org> wrote:

There is currently no way to add repositories in AndBible. I looked at the App code, and realized that it's not just a matter of 
hacking a URL string. It is also dependent on JSword, and there is repository-specific code for the three repositories that are 
available.




There are requests for this feature going back to 2015. Apparently Tuomas has it as a high priority feature request and is 
working on it: https://github.com/AndBible/and-bible/issues/238




John








Philip White wrote:




Great news that the NASB modulevis available! Probably not the place for this question, but it is in response to this news, so 
I'll ask anyway. I wanted to use the module on AndBible, but it doesn't look like there is a way to add the Lockman 
foundation's repository as a source. Has anyone done this without modifying the source code?



John Dudeck
Programmer at Editions Cle Lyon, France
john.dud...@sim.org    j...@editionscle.com
--
"The best time to be alive is when things look the worst." -- Dale Losch
  


___
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] PocketSword status

[Michael Johnson]

Actually, web servers don't get corona viruses, and people don't congregate in 
crowds around them physically, so COVID-19 has no direct effect on web servers 
or their use. The pandemic, however, does have some serious side-effects due to 
widespread panic, overreactions, shutdowns, shortages, etc., as well as 
increased malware attacks aimed at exploiting people's fear. One or more of 
those could cause a server shutdown. However, in general, electronic Scripture 
distribution is more robust than physical books
with respect to pandemics.

Case in point: Next week, the Nali half-NT dedication is scheduled on Manus 
Island. The printed waterproof books on order from Hong Kong will not be there 
on time. Instead, they will have just 100 print-on-demand paper editions, and 
will have tables set up to help people with smart phones to download the Nali 
Scriptures onto their smart phones. The edition on the eBible.org repository is 
actually more up-to-date and authoritative than the printed books, anyway, due 
to some corrections the translators sent
to me a few days ago. In that area of the world, it is OK to have the 
Scriptures online (and I do at https://PNG.Bible/nss/), but being able to 
download them and refer to them without Internet access later is great, because 
Internet access in that part of the world is expensive (paid by the megabyte), 
slow (2G), and intermittent.

So, in this case, COVID-19 has indirectly increased the importance of the 
ministry we do together.

On 3/13/20 8:38 AM, David Haslam wrote:
> And having multiple repository servers also makes sense in the context of the 
> Covid-19 pandemic.
>
> David
>
> Sent from ProtonMail Mobile
>
>
> On Fri, Mar 13, 2020 at 18:33, Michael Johnson  > wrote:
>> I plan to update PocketSword so that it draws from all official 
>> repositories, by default, much like AndBible does.
>>
>> Duplicating works in repositories is helpful, perhaps, for front ends that 
>> only look at one repository at a time, especially if the work is kept up to 
>> date in both repositories. When presented with an aggregate list, the user 
>> would see duplicate or near-duplicate entries. If the UI displays repository 
>> source and date of last update, as well as a full description of the module, 
>> this could help the user decide which one(s) to choose.
>>
>> As far as eBible.org goes, removing a work from the repository is actually 
>> more work than keeping it there, because of the way the automation is set 
>> up. Therefore I'm disinclined to remove works unless there is a valid reason 
>> other than duplication alone.
>>
>> For the World English Bible and its variants (American/British, 
>> standard/Messianic, with/without DC/Apocrypha), the eBible.org repository is 
>> the authoritative source with the most current copy. The same is true for 
>> hundreds of other translations. That older revisions are "out there" 
>> including in Crosswire Main doesn't bother me, really, because the 
>> differences generally don't affect meaning, but the English may be less up 
>> to date. Staying updated, of course, is better. I'm disinclined to mark any 
>> eBible.org
>> translations as obsoleting anything in another repository, absent a specific 
>> request from the appropriate pumpkin holder for that repository, lest 
>> confusion result. There are, of course, some translations where Crosswire 
>> Main is more authoritative. There are also cases where one repository has 
>> permission to distribute but the other one doesn't. We have an architecture 
>> that supports multiple repositories, although it does look like an 
>> afterthought. Still, we can make it work better, either by coming up with
>> standard ways of aggregating them better in the API, or maybe we keep 
>> leaving it up to each front end.
>>
>> Supporting multiple repositories is actually a good thing in terms of 
>> resilience against server outages, censorship, etc. It also gives more 
>> localized control to the various sources of modules. Otherwise, there would 
>> be a temptation to make one big super-repository. Maybe that isn't a 
>> terrible idea if it were just an automated aggregate mirror of all of the 
>> others, and if it could be done without violating copyright agreements. For 
>> fault tolerance and improved bandwidth, there could be more than one such
>> super-repository.
>>
>> Any thoughts?
>>
>> On 3/13/20 7:56 AM, Cyrille wrote:
>> >
>> >
>> > Le 13/03/2020 à 12:55, David Haslam a écrit :
>> >> Cyrille,
>> >>
>> >> I’m not in favour of removing modules from CrossWire simply because one 
>> >> of the affiliated repositories has a similar module.
>> > Why not?
>> >>
>> >> Nor should it ever be expected that a module published by eBible.org 
>> >> would include an Obsoletes key with one of CrossWire’s modules as the 
>> >> parameter.
>> >
>> > Idem why not?
>> >>
>> >>
>> >>
>> >> Regards,
>> >>
>> >> David
>> >>
>> >> Sent from ProtonMail Mobile
>> >>
>> >>
>> >> On 

Re: [sword-devel] PocketSword status

[David Haslam]

And having multiple repository servers also makes sense in the context of the 
Covid-19 pandemic.

David

Sent from ProtonMail Mobile

On Fri, Mar 13, 2020 at 18:33, Michael Johnson  wrote:

> I plan to update PocketSword so that it draws from all official repositories, 
> by default, much like AndBible does.
>
> Duplicating works in repositories is helpful, perhaps, for front ends that 
> only look at one repository at a time, especially if the work is kept up to 
> date in both repositories. When presented with an aggregate list, the user 
> would see duplicate or near-duplicate entries. If the UI displays repository 
> source and date of last update, as well as a full description of the module, 
> this could help the user decide which one(s) to choose.
>
> As far as eBible.org goes, removing a work from the repository is actually 
> more work than keeping it there, because of the way the automation is set up. 
> Therefore I'm disinclined to remove works unless there is a valid reason 
> other than duplication alone.
>
> For the World English Bible and its variants (American/British, 
> standard/Messianic, with/without DC/Apocrypha), the eBible.org repository is 
> the authoritative source with the most current copy. The same is true for 
> hundreds of other translations. That older revisions are "out there" 
> including in Crosswire Main doesn't bother me, really, because the 
> differences generally don't affect meaning, but the English may be less up to 
> date. Staying updated, of course, is better. I'm disinclined to mark any 
> eBible.org
> translations as obsoleting anything in another repository, absent a specific 
> request from the appropriate pumpkin holder for that repository, lest 
> confusion result. There are, of course, some translations where Crosswire 
> Main is more authoritative. There are also cases where one repository has 
> permission to distribute but the other one doesn't. We have an architecture 
> that supports multiple repositories, although it does look like an 
> afterthought. Still, we can make it work better, either by coming up with
> standard ways of aggregating them better in the API, or maybe we keep leaving 
> it up to each front end.
>
> Supporting multiple repositories is actually a good thing in terms of 
> resilience against server outages, censorship, etc. It also gives more 
> localized control to the various sources of modules. Otherwise, there would 
> be a temptation to make one big super-repository. Maybe that isn't a terrible 
> idea if it were just an automated aggregate mirror of all of the others, and 
> if it could be done without violating copyright agreements. For fault 
> tolerance and improved bandwidth, there could be more than one such
> super-repository.
>
> Any thoughts?
>
> On 3/13/20 7:56 AM, Cyrille wrote:
>>
>>
>> Le 13/03/2020 à 12:55, David Haslam a écrit :
>>> Cyrille,
>>>
>>> I’m not in favour of removing modules from CrossWire simply because one of 
>>> the affiliated repositories has a similar module.
>> Why not?
>>>
>>> Nor should it ever be expected that a module published by eBible.org would 
>>> include an Obsoletes key with one of CrossWire’s modules as the parameter.
>>
>> Idem why not?
>>>
>>>
>>>
>>> Regards,
>>>
>>> David
>>>
>>> Sent from ProtonMail Mobile
>>>
>>>
>>> On Fri, Mar 13, 2020 at 08:11, Cyrille >> > wrote:
 Dear all,
 Actually my worry was about a question between the module team. We have
 duplicated modules, in Crosswire and in ebible.org. Often the ebible.org
 are updated and not in Crosswire. And we are very slow to update the new
 module in Crosswire. Then I proposed to remove in the Crosswire repo,
 all the old modules with issue reported on the bug tracker. But the
 question was: What to do if the users don't know how to change the repo,
 as it happened in the other post on this list, some of us didn't know
 how to change for IBT in Xiphos.
 I Bibletime, Andbible and Bishop, the repositories are updated all
 together, but not in Xiphos. I opened an issue about this on the xiphos 
 git.
 For this reason I proposed this for Swordpocket, even if it seems to be
 more or less easier than for Xiphos.

 Br Cyrille

 Le 13/03/2020 à 04:14, Nic Carter a écrit :
 > On the downloads screen, tap on the folder icon in the top right corner, 
 > then refresh the source list.
 > That will show all servers in the Master Server List.
 >
 > Sent from my phone, hence this email may be short...
 >
 >> On 13/03/2020, at 09:24, Cyrille  wrote:
 >>
 >> Hi Michael,
 >> Maybe add the updating of all the repositories at once, as with Andbible
 >> and Bishop. This will help users who don't know they are other
 >> repository as ebible.org...
 >> My 2 cents :)
 >>
 >> Br Cyrille
 >>
 >>> Le 12/03/2020 à 20:30, Michael Johnson a écrit :
 >>> Hello, my brothers and 

Re: [sword-devel] NASB, NBLA, LBLA

[David Haslam]

See the And Bible Facebook page.

NASB is now available for free in And Bible due to Crosswire's new distribution 
contract! To use NASB (or LBLA or NBLA), please update to the latest version of 
And Bible first; update is now available in Play Store (3.2.343).

Sent from ProtonMail Mobile

On Fri, Mar 13, 2020 at 18:26, John Dudeck  wrote:

> There is currently no way to add repositories in AndBible. I looked at the 
> App code, and realized that it's not just a matter of hacking a URL string. 
> It is also dependent on JSword, and there is repository-specific code for the 
> three repositories that are available.
>
> There are requests for this feature going back to 2015. Apparently Tuomas has 
> it as a high priority feature request and is working on it: 
> https://github.com/AndBible/and-bible/issues/238
>
> John
>
> ---
>
> Philip White wrote:
>
> Great news that the NASB modulevis available! Probably not the place for this 
> question, but it is in response to this news, so I'll ask anyway. I wanted to 
> use the module on AndBible, but it doesn't look like there is a way to add 
> the Lockman foundation's repository as a source. Has anyone done this without 
> modifying the source code?
>
> John Dudeck  Tel: +1-704-588-9891  Cell: +1-803-504-8065
> john.dud...@sim.orgCharlotte, North Carolina
> --
> "It sometimes happens that God leads us by an obscure intuition
>  which makes us go to a particular place without our knowing what
>  awaits us there. It sometimes happens, too, that he leads us by means
>  of events that seem to have no religious significance. There is no
>  such thing as chance." -- Paul Tournier___
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] NASB, NBLA, LBLA

[David Haslam]

From the announcement on their Facebook page.

NASB is now available for free in And Bible due to Crosswire's new distribution 
contract! To use NASB (or LBLA or NBLA), please update to the latest version of 
And Bible first; update is now available in Play Store (3.2.343).

Regards,

David

Sent from ProtonMail Mobile

On Fri, Mar 13, 2020 at 17:52, Philip White  wrote:

> Great news that the NASB modulevis available! Probably not the place for this 
> question, but it is in response to this news, so I'll ask anyway. I wanted to 
> use the module on AndBible, but it doesn't look like there is a way to add 
> the Lockman foundation's repository as a source. Has anyone done this without 
> modifying the source code?
>
> On Fri, Mar 13, 2020, 13:40 Troy A. Griffitts  wrote:
>
>> Regarding the NASB 2020 text, here is the word from Lockman:
>>
>> We're not releasing the NASB 2020 in software until the print editions are 
>> available toward the end of this year. I don't have a date yet. Then we'll 
>> look at free software sometime in 2021 after the commercial release.
>>
>> On March 13, 2020 10:29:34 AM MST, Michael H  wrote:
>>
>>> There's also a NASB2020 in limited preview release right now.
>>>
>>> NASB will remain 1995 edition?  Does the license stipulate whether updates 
>>> are mandatory?
>>>
>>> On Fri, Mar 13, 2020 at 7:48 AM Tom Sullivan  wrote:
>>>
 Y'all:

 There was a request to change the module NASB to NASB95. Is this in the
 works or will it remain NASB? There are in fact, two versions of the
 NASB out there as those who have the older (especially  print) version 
 know.

 Thanks.

 Tom Sullivan
 i...@beforgiven.info
 FAX: 815-301-2835
 -

 On 3/12/20 12:42 AM, Troy A. Griffitts wrote:
> It's been a long long road, but after much negotiation and many
> volunteers contributing to the conversion efforts, we have finally been
> granted permission to distribute Lockman's:
>
> New American Standard Bible (NASB)
> Nueva Biblia de las Américas (NBLA)
> La Biblia de las Américas (LBLA)
>
> Additionally, a gracious gift from Lockman, they have granted permission
> for CrossWire to distribute all 3 of these modules unlocked, for free.
>
> The modules are immediately available on swordweb:
>
> http://www.crosswire.org/study/parallelstudy.jsp?del=all=NASB=LBLA=NBLA=Jn.3.16
>
> And have been updated in the "Lockman Foundation" repository.  Please
> refresh your repository in your favorite frontend to be sure you have
> the latest module configurations.
>
> If you have previously installed any of these modules using the test
> unlock keys, you may need to clear out the key for them to work property
> in your frontend.
>
> May God use these resources to draw people to Himself.
>
> Praise Him for always providing cool things,
>
> Troy
>
>
> ___
> 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
>
> __
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> __
>

 ___
 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
>>
>> --
>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>> ___
>> 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] PocketSword status

[Michael Johnson]

I plan to update PocketSword so that it draws from all official repositories, 
by default, much like AndBible does.

Duplicating works in repositories is helpful, perhaps, for front ends that only 
look at one repository at a time, especially if the work is kept up to date in 
both repositories. When presented with an aggregate list, the user would see 
duplicate or near-duplicate entries. If the UI displays repository source and 
date of last update, as well as a full description of the module, this could 
help the user decide which one(s) to choose.

As far as eBible.org goes, removing a work from the repository is actually more 
work than keeping it there, because of the way the automation is set up. 
Therefore I'm disinclined to remove works unless there is a valid reason other 
than duplication alone.

For the World English Bible and its variants (American/British, 
standard/Messianic, with/without DC/Apocrypha), the eBible.org repository is 
the authoritative source with the most current copy. The same is true for 
hundreds of other translations. That older revisions are "out there" including 
in Crosswire Main doesn't bother me, really, because the differences generally 
don't affect meaning, but the English may be less up to date. Staying updated, 
of course, is better. I'm disinclined to mark any eBible.org
translations as obsoleting anything in another repository, absent a specific 
request from the appropriate pumpkin holder for that repository, lest confusion 
result. There are, of course, some translations where Crosswire Main is more 
authoritative. There are also cases where one repository has permission to 
distribute but the other one doesn't. We have an architecture that supports 
multiple repositories, although it does look like an afterthought. Still, we 
can make it work better, either by coming up with
standard ways of aggregating them better in the API, or maybe we keep leaving 
it up to each front end.

Supporting multiple repositories is actually a good thing in terms of 
resilience against server outages, censorship, etc. It also gives more 
localized control to the various sources of modules. Otherwise, there would be 
a temptation to make one big super-repository. Maybe that isn't a terrible idea 
if it were just an automated aggregate mirror of all of the others, and if it 
could be done without violating copyright agreements. For fault tolerance and 
improved bandwidth, there could be more than one such
super-repository.

Any thoughts?

On 3/13/20 7:56 AM, Cyrille wrote:
>
>
> Le 13/03/2020 à 12:55, David Haslam a écrit :
>> Cyrille,
>>
>> I’m not in favour of removing modules from CrossWire simply because one of 
>> the affiliated repositories has a similar module.
> Why not?
>>
>> Nor should it ever be expected that a module published by eBible.org would 
>> include an Obsoletes key with one of CrossWire’s modules as the parameter.
>
> Idem why not?
>>
>>
>>
>> Regards,
>>
>> David
>>
>> Sent from ProtonMail Mobile
>>
>>
>> On Fri, Mar 13, 2020 at 08:11, Cyrille > > wrote:
>>> Dear all,
>>> Actually my worry was about a question between the module team. We have
>>> duplicated modules, in Crosswire and in ebible.org. Often the ebible.org
>>> are updated and not in Crosswire. And we are very slow to update the new
>>> module in Crosswire. Then I proposed to remove in the Crosswire repo,
>>> all the old modules with issue reported on the bug tracker. But the
>>> question was: What to do if the users don't know how to change the repo,
>>> as it happened in the other post on this list, some of us didn't know
>>> how to change for IBT in Xiphos.
>>> I Bibletime, Andbible and Bishop, the repositories are updated all
>>> together, but not in Xiphos. I opened an issue about this on the xiphos git.
>>> For this reason I proposed this for Swordpocket, even if it seems to be
>>> more or less easier than for Xiphos.
>>>
>>> Br Cyrille
>>>
>>> Le 13/03/2020 à 04:14, Nic Carter a écrit :
>>> > On the downloads screen, tap on the folder icon in the top right corner, 
>>> > then refresh the source list.
>>> > That will show all servers in the Master Server List.
>>> >
>>> > Sent from my phone, hence this email may be short...
>>> >
>>> >> On 13/03/2020, at 09:24, Cyrille  wrote:
>>> >>
>>> >> Hi Michael,
>>> >> Maybe add the updating of all the repositories at once, as with Andbible
>>> >> and Bishop. This will help users who don't know they are other
>>> >> repository as ebible.org...
>>> >> My 2 cents :)
>>> >>
>>> >> Br Cyrille
>>> >>
>>> >>> Le 12/03/2020 à 20:30, Michael Johnson a écrit :
>>> >>> Hello, my brothers and sisters in Christ.
>>> >>>
>>> >>> I just thought I should post a status on PocketSword work. I have 
>>> >>> started on updating it, but haven't yet gotten to a stable point for 
>>> >>> testing using Test Flight. Right now, it is, unfortunately, on hold, as 
>>> >>> I have another task in the foreground. I finished the main editing of 

Re: [sword-devel] NASB, NBLA, LBLA

[John Dudeck]

There is currently no way to add repositories in AndBible. I looked at the App code, and realized that it's not just a matter of 
hacking a URL string. It is also dependent on JSword, and there is repository-specific code for the three repositories that are 
available.


There are requests for this feature going back to 2015. Apparently Tuomas has it as a high priority feature request and is working 
on it: https://github.com/AndBible/and-bible/issues/238


John






Philip White wrote:


Great news that the NASB modulevis available! Probably not the place for this question, but it is in response to this news, so I'll 
ask anyway. I wanted to use the module on AndBible, but it doesn't look like there is a way to add the Lockman foundation's 
repository as a source. Has anyone done this without modifying the source code?


John Dudeck  Tel: +1-704-588-9891  Cell: +1-803-504-8065
john.dud...@sim.org    Charlotte, North Carolina
--
"It sometimes happens that God leads us by an obscure intuition
 which makes us go to a particular place without our knowing what
 awaits us there. It sometimes happens, too, that he leads us by means
 of events that seem to have no religious significance. There is no
 such thing as chance." -- Paul Tournier
  


___
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] PocketSword status

[Cyrille]

Le 13/03/2020 à 12:55, David Haslam a écrit :
> Cyrille,
>
> I’m not in favour of removing modules from CrossWire simply because
> one of the affiliated repositories has a similar module.
Why not?
>
> Nor should it ever be expected that a module published by eBible.org
> would include an Obsoletes key with one of CrossWire’s modules as the
> parameter.

Idem why not?
>
>
>
> Regards,
>
> David
>
> Sent from ProtonMail Mobile
>
>
> On Fri, Mar 13, 2020 at 08:11, Cyrille  > wrote:
>> Dear all,
>> Actually my worry was about a question between the module team. We have
>> duplicated modules, in Crosswire and in ebible.org. Often the ebible.org
>> are updated and not in Crosswire. And we are very slow to update the new
>> module in Crosswire. Then I proposed to remove in the Crosswire repo,
>> all the old modules with issue reported on the bug tracker. But the
>> question was: What to do if the users don't know how to change the repo,
>> as it happened in the other post on this list, some of us didn't know
>> how to change for IBT in Xiphos.
>> I Bibletime, Andbible and Bishop, the repositories are updated all
>> together, but not in Xiphos. I opened an issue about this on the
>> xiphos git.
>> For this reason I proposed this for Swordpocket, even if it seems to be
>> more or less easier than for Xiphos.
>>
>> Br Cyrille
>>
>> Le 13/03/2020 à 04:14, Nic Carter a écrit :
>> > On the downloads screen, tap on the folder icon in the top right
>> corner, then refresh the source list.
>> > That will show all servers in the Master Server List.
>> >
>> > Sent from my phone, hence this email may be short...
>> >
>> >> On 13/03/2020, at 09:24, Cyrille  wrote:
>> >>
>> >> Hi Michael,
>> >> Maybe add the updating of all the repositories at once, as with
>> Andbible
>> >> and Bishop. This will help users who don't know they are other
>> >> repository as ebible.org...
>> >> My 2 cents :)
>> >>
>> >> Br Cyrille
>> >>
>> >>> Le 12/03/2020 à 20:30, Michael Johnson a écrit :
>> >>> Hello, my brothers and sisters in Christ.
>> >>>
>> >>> I just thought I should post a status on PocketSword work. I have
>> started on updating it, but haven't yet gotten to a stable point for
>> testing using Test Flight. Right now, it is, unfortunately, on hold,
>> as I have another task in the foreground. I finished the main editing
>> of the World English Bible, with the exception of still correcting
>> the occasional rare typo. (I found one this morning in Ezekiel.) My
>> foreground task at the moment is integrating SILE into Haiola for
>> better PDF generation, especially
>> >>> with mixed complex scripts. After that is done, I hope to focus
>> on PocketSword. In its new incarnation, it will generate its own
>> indexes, and won't need special server support for that. I'll also
>> fix the key problem for when a module goes from locked to unlocked,
>> which of course, will happen as copyrights expire and/or special
>> permission is granted.
>> >>>
>> >>> Thank you for your patience.
>> >>>
>> >>
>> >> ___
>> >> 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
>>
>>
>>
>> ___
>> 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

___
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] NASB, NBLA, LBLA

[Philip White]

Great news that the NASB modulevis available! Probably not the place for
this question, but it is in response to this news, so I'll ask anyway. I
wanted to use the module on AndBible, but it doesn't look like there is a
way to add the Lockman foundation's repository as a source. Has anyone done
this without modifying the source code?

On Fri, Mar 13, 2020, 13:40 Troy A. Griffitts  wrote:

> Regarding the NASB 2020 text, here is the word from Lockman:
>
> We're not releasing the NASB 2020 in software until the print editions are
> available toward the end of this year. I don't have a date yet. Then we'll
> look at free software sometime in 2021 after the commercial release.
>
> On March 13, 2020 10:29:34 AM MST, Michael H  wrote:
>>
>> There's also a NASB2020 in limited preview release right now.
>>
>> NASB will remain 1995 edition?  Does the license stipulate whether
>> updates are mandatory?
>>
>>
>> On Fri, Mar 13, 2020 at 7:48 AM Tom Sullivan 
>> wrote:
>>
>>> Y'all:
>>>
>>> There was a request to change the module NASB to NASB95. Is this in the
>>> works or will it remain NASB? There are in fact, two versions of the
>>> NASB out there as those who have the older (especially  print) version
>>> know.
>>>
>>> Thanks.
>>>
>>> Tom Sullivan
>>> i...@beforgiven.info
>>> FAX: 815-301-2835
>>> -
>>>
>>>
>>> On 3/12/20 12:42 AM, Troy A. Griffitts wrote:
>>> > It's been a long long road, but after much negotiation and many
>>> > volunteers contributing to the conversion efforts, we have finally been
>>> > granted permission to distribute Lockman's:
>>> >
>>> > New American Standard Bible (NASB)
>>> > Nueva Biblia de las Américas (NBLA)
>>> > La Biblia de las Américas (LBLA)
>>> >
>>> > Additionally, a gracious gift from Lockman, they have granted
>>> permission
>>> > for CrossWire to distribute all 3 of these modules unlocked, for free.
>>> >
>>> > The modules are immediately available on swordweb:
>>> >
>>> >
>>> http://www.crosswire.org/study/parallelstudy.jsp?del=all=NASB=LBLA=NBLA=Jn.3.16
>>> >
>>> > And have been updated in the "Lockman Foundation" repository.  Please
>>> > refresh your repository in your favorite frontend to be sure you have
>>> > the latest module configurations.
>>> >
>>> > If you have previously installed any of these modules using the test
>>> > unlock keys, you may need to clear out the key for them to work
>>> property
>>> > in your frontend.
>>> >
>>> > May God use these resources to draw people to Himself.
>>> >
>>> > Praise Him for always providing cool things,
>>> >
>>> > Troy
>>> >
>>> >
>>> > ___
>>> > 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
>>> >
>>> > __
>>> > This email has been scanned by the Symantec Email Security.cloud
>>> service.
>>> > For more information please visit http://www.symanteccloud.com
>>> > __
>>> >
>>>
>>> ___
>>> 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
>>
>>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
> ___
> 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] NASB, NBLA, LBLA

[Troy A. Griffitts]

Regarding the NASB 2020 text, here is the word from Lockman:

We're not releasing the NASB 2020 in software until the print editions are 
available toward the end of this year. I don't have a date yet. Then we'll look 
at free software sometime in 2021 after the commercial release.

On March 13, 2020 10:29:34 AM MST, Michael H  wrote:
>There's also a NASB2020 in limited preview release right now.
>
>NASB will remain 1995 edition?  Does the license stipulate whether
>updates
>are mandatory?
>
>
>On Fri, Mar 13, 2020 at 7:48 AM Tom Sullivan 
>wrote:
>
>> Y'all:
>>
>> There was a request to change the module NASB to NASB95. Is this in
>the
>> works or will it remain NASB? There are in fact, two versions of the
>> NASB out there as those who have the older (especially  print)
>version
>> know.
>>
>> Thanks.
>>
>> Tom Sullivan
>> i...@beforgiven.info
>> FAX: 815-301-2835
>> -
>>
>>
>> On 3/12/20 12:42 AM, Troy A. Griffitts wrote:
>> > It's been a long long road, but after much negotiation and many
>> > volunteers contributing to the conversion efforts, we have finally
>been
>> > granted permission to distribute Lockman's:
>> >
>> > New American Standard Bible (NASB)
>> > Nueva Biblia de las Américas (NBLA)
>> > La Biblia de las Américas (LBLA)
>> >
>> > Additionally, a gracious gift from Lockman, they have granted
>permission
>> > for CrossWire to distribute all 3 of these modules unlocked, for
>free.
>> >
>> > The modules are immediately available on swordweb:
>> >
>> >
>>
>http://www.crosswire.org/study/parallelstudy.jsp?del=all=NASB=LBLA=NBLA=Jn.3.16
>> >
>> > And have been updated in the "Lockman Foundation" repository. 
>Please
>> > refresh your repository in your favorite frontend to be sure you
>have
>> > the latest module configurations.
>> >
>> > If you have previously installed any of these modules using the
>test
>> > unlock keys, you may need to clear out the key for them to work
>property
>> > in your frontend.
>> >
>> > May God use these resources to draw people to Himself.
>> >
>> > Praise Him for always providing cool things,
>> >
>> > Troy
>> >
>> >
>> > ___
>> > 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
>> >
>> >
>__
>> > This email has been scanned by the Symantec Email Security.cloud
>service.
>> > For more information please visit http://www.symanteccloud.com
>> >
>__
>> >
>>
>> ___
>> 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

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.___
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] NASB, NBLA, LBLA

[Michael H]

There's also a NASB2020 in limited preview release right now.

NASB will remain 1995 edition?  Does the license stipulate whether updates
are mandatory?


On Fri, Mar 13, 2020 at 7:48 AM Tom Sullivan  wrote:

> Y'all:
>
> There was a request to change the module NASB to NASB95. Is this in the
> works or will it remain NASB? There are in fact, two versions of the
> NASB out there as those who have the older (especially  print) version
> know.
>
> Thanks.
>
> Tom Sullivan
> i...@beforgiven.info
> FAX: 815-301-2835
> -
>
>
> On 3/12/20 12:42 AM, Troy A. Griffitts wrote:
> > It's been a long long road, but after much negotiation and many
> > volunteers contributing to the conversion efforts, we have finally been
> > granted permission to distribute Lockman's:
> >
> > New American Standard Bible (NASB)
> > Nueva Biblia de las Américas (NBLA)
> > La Biblia de las Américas (LBLA)
> >
> > Additionally, a gracious gift from Lockman, they have granted permission
> > for CrossWire to distribute all 3 of these modules unlocked, for free.
> >
> > The modules are immediately available on swordweb:
> >
> >
> http://www.crosswire.org/study/parallelstudy.jsp?del=all=NASB=LBLA=NBLA=Jn.3.16
> >
> > And have been updated in the "Lockman Foundation" repository.  Please
> > refresh your repository in your favorite frontend to be sure you have
> > the latest module configurations.
> >
> > If you have previously installed any of these modules using the test
> > unlock keys, you may need to clear out the key for them to work property
> > in your frontend.
> >
> > May God use these resources to draw people to Himself.
> >
> > Praise Him for always providing cool things,
> >
> > Troy
> >
> >
> > ___
> > 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
> >
> > __
> > This email has been scanned by the Symantec Email Security.cloud service.
> > For more information please visit http://www.symanteccloud.com
> > __
> >
>
> ___
> 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] PocketSword status

[David Haslam]

Perhaps the only exception I would consider would be the suggestion that the 
three WEB modules should be removed by CrossWire because these were based on a 
very early edition of the WEB source text files obtained from Michael Johnson.

They are now well out of date compared to the equivalents on eBible.org

But on this we should still defer to Michael J should he wish us to retain them.

David

Sent from ProtonMail Mobile

On Fri, Mar 13, 2020 at 13:24, Cyrille  wrote:

> Le 13/03/2020 à 12:55, David Haslam a écrit :
>
>> Cyrille,
>>
>> I’m not in favour of removing modules from CrossWire simply because one of 
>> the affiliated repositories has a similar module.
>
> At the beginning I understood because it's not clear how the sword UI propose 
> the access to the diverse repositories.
>
>> Nor should it ever be expected that a module published by eBible.org would 
>> include an Obsoletes key with one of CrossWire’s modules as the parameter.
>
> Maybe we can discuss of this, specialy with Michael. Sometimes Michael can 
> add this key. Two same modules, it's two times work, and already now the 
> modules team can't keep up with the updates, so adding work for nothing I 
> find it counterproductive.
> In addition we leave modules with errors lying around on Crosswire while they 
> have been corrected for a long time on ebible.
>
> Or we need to recruit new volunteers for help in the module team.
>
> Regards, Br Cyrille
>
> PS: For the Chinese modules I would agree with you, because we can use an 
> other iso code, closer to the language used (zh-hant and zh-hans, and not 
> cmn).
>
>> Regards,
>>
>> David
>>
>> Sent from ProtonMail Mobile
>>
>> On Fri, Mar 13, 2020 at 08:11, Cyrille  wrote:
>>
>>> Dear all,
>>> Actually my worry was about a question between the module team. We have
>>> duplicated modules, in Crosswire and in ebible.org. Often the ebible.org
>>> are updated and not in Crosswire. And we are very slow to update the new
>>> module in Crosswire. Then I proposed to remove in the Crosswire repo,
>>> all the old modules with issue reported on the bug tracker. But the
>>> question was: What to do if the users don't know how to change the repo,
>>> as it happened in the other post on this list, some of us didn't know
>>> how to change for IBT in Xiphos.
>>> I Bibletime, Andbible and Bishop, the repositories are updated all
>>> together, but not in Xiphos. I opened an issue about this on the xiphos git.
>>> For this reason I proposed this for Swordpocket, even if it seems to be
>>> more or less easier than for Xiphos.
>>>
>>> Br Cyrille
>>>
>>> Le 13/03/2020 à 04:14, Nic Carter a écrit :
 On the downloads screen, tap on the folder icon in the top right corner, 
 then refresh the source list.
 That will show all servers in the Master Server List.

 Sent from my phone, hence this email may be short...

> On 13/03/2020, at 09:24, Cyrille 
> [](mailto:lafricai...@gmail.com) wrote:
>
> Hi Michael,
> Maybe add the updating of all the repositories at once, as with Andbible
> and Bishop. This will help users who don't know they are other
> repository as ebible.org...
> My 2 cents :)
>
> Br Cyrille
>
>> Le 12/03/2020 à 20:30, Michael Johnson a écrit :
>> Hello, my brothers and sisters in Christ.
>>
>> I just thought I should post a status on PocketSword work. I have 
>> started on updating it, but haven't yet gotten to a stable point for 
>> testing using Test Flight. Right now, it is, unfortunately, on hold, as 
>> I have another task in the foreground. I finished the main editing of 
>> the World English Bible, with the exception of still correcting the 
>> occasional rare typo. (I found one this morning in Ezekiel.) My 
>> foreground task at the moment is integrating SILE into Haiola for better 
>> PDF generation, especially
>> with mixed complex scripts. After that is done, I hope to focus on 
>> PocketSword. In its new incarnation, it will generate its own indexes, 
>> and won't need special server support for that. I'll also fix the key 
>> problem for when a module goes from locked to unlocked, which of course, 
>> will happen as copyrights expire and/or special permission is granted.
>>
>> Thank you for your patience.
>>
>
> ___
> 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
>>>
>>> ___
>>> sword-devel mailing list: sword-devel@crosswire.org
>>> 

Re: [sword-devel] PocketSword status

[Cyrille]

Le 13/03/2020 à 12:55, David Haslam a écrit :
> Cyrille,
>
> I’m not in favour of removing modules from CrossWire simply because
> one of the affiliated repositories has a similar module.
At the beginning I understood because it's not clear how the sword UI
propose the access to the diverse repositories.
> Nor should it ever be expected that a module published by eBible.org
> would include an Obsoletes key with one of CrossWire’s modules as the
> parameter.
Maybe we can discuss of this, specialy with Michael. Sometimes Michael
can add this key. Two same modules, it's two times work, and already now
the modules team can't keep up with the updates, so adding work for
nothing I find it counterproductive.
In addition we leave modules with errors lying around on Crosswire while
they have been corrected for a long time on ebible.

Or we need to recruit new volunteers for help in the module team.

Regards, Br Cyrille

PS: For the Chinese modules I would agree with you, because we can use
an other iso code, closer to the language used (zh-hant and zh-hans, and
not cmn).
>
>
>
> Regards,
>
> David
>
> Sent from ProtonMail Mobile
>
>
> On Fri, Mar 13, 2020 at 08:11, Cyrille  > wrote:
>> Dear all,
>> Actually my worry was about a question between the module team. We have
>> duplicated modules, in Crosswire and in ebible.org. Often the ebible.org
>> are updated and not in Crosswire. And we are very slow to update the new
>> module in Crosswire. Then I proposed to remove in the Crosswire repo,
>> all the old modules with issue reported on the bug tracker. But the
>> question was: What to do if the users don't know how to change the repo,
>> as it happened in the other post on this list, some of us didn't know
>> how to change for IBT in Xiphos.
>> I Bibletime, Andbible and Bishop, the repositories are updated all
>> together, but not in Xiphos. I opened an issue about this on the
>> xiphos git.
>> For this reason I proposed this for Swordpocket, even if it seems to be
>> more or less easier than for Xiphos.
>>
>> Br Cyrille
>>
>> Le 13/03/2020 à 04:14, Nic Carter a écrit :
>> > On the downloads screen, tap on the folder icon in the top right
>> corner, then refresh the source list.
>> > That will show all servers in the Master Server List.
>> >
>> > Sent from my phone, hence this email may be short...
>> >
>> >> On 13/03/2020, at 09:24, Cyrille  wrote:
>> >>
>> >> Hi Michael,
>> >> Maybe add the updating of all the repositories at once, as with
>> Andbible
>> >> and Bishop. This will help users who don't know they are other
>> >> repository as ebible.org...
>> >> My 2 cents :)
>> >>
>> >> Br Cyrille
>> >>
>> >>> Le 12/03/2020 à 20:30, Michael Johnson a écrit :
>> >>> Hello, my brothers and sisters in Christ.
>> >>>
>> >>> I just thought I should post a status on PocketSword work. I have
>> started on updating it, but haven't yet gotten to a stable point for
>> testing using Test Flight. Right now, it is, unfortunately, on hold,
>> as I have another task in the foreground. I finished the main editing
>> of the World English Bible, with the exception of still correcting
>> the occasional rare typo. (I found one this morning in Ezekiel.) My
>> foreground task at the moment is integrating SILE into Haiola for
>> better PDF generation, especially
>> >>> with mixed complex scripts. After that is done, I hope to focus
>> on PocketSword. In its new incarnation, it will generate its own
>> indexes, and won't need special server support for that. I'll also
>> fix the key problem for when a module goes from locked to unlocked,
>> which of course, will happen as copyrights expire and/or special
>> permission is granted.
>> >>>
>> >>> Thank you for your patience.
>> >>>
>> >>
>> >> ___
>> >> 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
>>
>>
>>
>> ___
>> 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

___
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] NASB, NBLA, LBLA

[Tom Sullivan]

Y'all:

There was a request to change the module NASB to NASB95. Is this in the 
works or will it remain NASB? There are in fact, two versions of the 
NASB out there as those who have the older (especially  print) version know.


Thanks.

Tom Sullivan
i...@beforgiven.info
FAX: 815-301-2835
-


On 3/12/20 12:42 AM, Troy A. Griffitts wrote:

It's been a long long road, but after much negotiation and many
volunteers contributing to the conversion efforts, we have finally been
granted permission to distribute Lockman's:

New American Standard Bible (NASB)
Nueva Biblia de las Américas (NBLA)
La Biblia de las Américas (LBLA)

Additionally, a gracious gift from Lockman, they have granted permission
for CrossWire to distribute all 3 of these modules unlocked, for free.

The modules are immediately available on swordweb:

http://www.crosswire.org/study/parallelstudy.jsp?del=all=NASB=LBLA=NBLA=Jn.3.16

And have been updated in the "Lockman Foundation" repository.  Please
refresh your repository in your favorite frontend to be sure you have
the latest module configurations.

If you have previously installed any of these modules using the test
unlock keys, you may need to clear out the key for them to work property
in your frontend.

May God use these resources to draw people to Himself.

Praise Him for always providing cool things,

Troy


___
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

__
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
__



___
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] PocketSword status

[David Haslam]

Cyrille,

I’m not in favour of removing modules from CrossWire simply because one of the 
affiliated repositories has a similar module.

Nor should it ever be expected that a module published by eBible.org would 
include an Obsoletes key with one of CrossWire’s modules as the parameter.

Regards,

David

Sent from ProtonMail Mobile

On Fri, Mar 13, 2020 at 08:11, Cyrille  wrote:

> Dear all,
> Actually my worry was about a question between the module team. We have
> duplicated modules, in Crosswire and in ebible.org. Often the ebible.org
> are updated and not in Crosswire. And we are very slow to update the new
> module in Crosswire. Then I proposed to remove in the Crosswire repo,
> all the old modules with issue reported on the bug tracker. But the
> question was: What to do if the users don't know how to change the repo,
> as it happened in the other post on this list, some of us didn't know
> how to change for IBT in Xiphos.
> I Bibletime, Andbible and Bishop, the repositories are updated all
> together, but not in Xiphos. I opened an issue about this on the xiphos git.
> For this reason I proposed this for Swordpocket, even if it seems to be
> more or less easier than for Xiphos.
>
> Br Cyrille
>
> Le 13/03/2020 à 04:14, Nic Carter a écrit :
>> On the downloads screen, tap on the folder icon in the top right corner, 
>> then refresh the source list.
>> That will show all servers in the Master Server List.
>>
>> Sent from my phone, hence this email may be short...
>>
>>> On 13/03/2020, at 09:24, Cyrille  wrote:
>>>
>>> Hi Michael,
>>> Maybe add the updating of all the repositories at once, as with Andbible
>>> and Bishop. This will help users who don't know they are other
>>> repository as ebible.org...
>>> My 2 cents :)
>>>
>>> Br Cyrille
>>>
 Le 12/03/2020 à 20:30, Michael Johnson a écrit :
 Hello, my brothers and sisters in Christ.

 I just thought I should post a status on PocketSword work. I have started 
 on updating it, but haven't yet gotten to a stable point for testing using 
 Test Flight. Right now, it is, unfortunately, on hold, as I have another 
 task in the foreground. I finished the main editing of the World English 
 Bible, with the exception of still correcting the occasional rare typo. (I 
 found one this morning in Ezekiel.) My foreground task at the moment is 
 integrating SILE into Haiola for better PDF generation, especially
 with mixed complex scripts. After that is done, I hope to focus on 
 PocketSword. In its new incarnation, it will generate its own indexes, and 
 won't need special server support for that. I'll also fix the key problem 
 for when a module goes from locked to unlocked, which of course, will 
 happen as copyrights expire and/or special permission is granted.

 Thank you for your patience.

>>>
>>> ___
>>> 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
>
> ___
> 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] NASB Unlock Key

[David Haslam]

Refresh sources and re-install it.

The released NASB module is not locked.

Read the earlier message from Troy with the official announcement.

David

Sent from ProtonMail Mobile

On Fri, Mar 13, 2020 at 08:14, John A. Sullivan III 
 wrote:

> Hello, all. I was absolutely thrilled to see the Lockman Foundation
> now appear in the Bibletime bookshelf options and I downloaded the NASB
> module. I was about to purchase a key from Lockman but I see notes on-l
> ine that the module cannot yet be unlocked and is only for testing. I
> don't know if those are old notes.
>
> If I purchase a NASB key, can I use it to unlock the NASB module in
> Bibletime (or any other SWORD based applications)? Thank you for your
> dedication to this invaluable project - John
> --
> John A. Sullivan III
>
> Elmont Community Bible Study
> Join us in person or on-line at
> http://ElmontBibleStudy.org
>
> ___
> 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] [bt-devel] NASB, NBLA, LBLA

[John A. Sullivan III]

I'm thrilled. At last.  Thank you, thank you, thank you

On Wed, 2020-03-11 at 21:42 -0700, Troy A. Griffitts wrote:
> It's been a long long road, but after much negotiation and many
> volunteers contributing to the conversion efforts, we have finally
> been
> granted permission to distribute Lockman's:
> 
> New American Standard Bible (NASB)
> Nueva Biblia de las Américas (NBLA)
> La Biblia de las Américas (LBLA)
> 
> Additionally, a gracious gift from Lockman, they have granted
> permission
> for CrossWire to distribute all 3 of these modules unlocked, for
> free.
> 
> The modules are immediately available on swordweb:
> 
> http://www.crosswire.org/study/parallelstudy.jsp?del=all=NASB=LBLA=NBLA=Jn.3.16
> 
> And have been updated in the "Lockman Foundation" repository.  Please
> refresh your repository in your favorite frontend to be sure you have
> the latest module configurations.
> 
> If you have previously installed any of these modules using the test
> unlock keys, you may need to clear out the key for them to work
> property
> in your frontend.
> 
> May God use these resources to draw people to Himself.
> 
> Praise Him for always providing cool things,
> 
> Troy
> 
> 
> ___
> bt-devel mailing list
> bt-de...@crosswire.org
> http://www.crosswire.org/mailman/listinfo/bt-devel
-- 
John A. Sullivan III

Elmont Community Bible Study
Join us in person or on-line at
http://ElmontBibleStudy.org


___
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] NASB Unlock Key

[John A. Sullivan III]

Hello, all.  I was absolutely thrilled to see the Lockman Foundation
now appear in the Bibletime bookshelf options and I downloaded the NASB
module. I was about to purchase a key from Lockman but I see notes on-l
ine that the module cannot yet be unlocked and is only for testing.  I
don't know if those are old notes.

If I purchase a NASB key, can I use it to unlock the NASB module in
Bibletime (or any other SWORD based applications)? Thank you for your
dedication to this invaluable project - John
-- 
John A. Sullivan III

Elmont Community Bible Study
Join us in person or on-line at
http://ElmontBibleStudy.org


___
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] PocketSword status

[Cyrille]

Dear all,
Actually my worry was about a question between the module team. We have
duplicated modules, in Crosswire and in ebible.org. Often the ebible.org
are updated and not in Crosswire. And we are very slow to update the new
module in Crosswire. Then I proposed to remove in the Crosswire repo,
all the old modules with issue reported on the bug tracker. But the
question was: What to do if the users don't know how to change the repo,
as it happened in the other post on this list, some of us didn't know
how to change for IBT in Xiphos.
I Bibletime, Andbible and Bishop, the repositories are updated all
together, but not in Xiphos. I opened an issue about this on the xiphos git.
For this reason I proposed this for Swordpocket, even if it seems to be
more or less easier than for Xiphos.

Br Cyrille

Le 13/03/2020 à 04:14, Nic Carter a écrit :
> On the downloads screen, tap on the folder icon in the top right corner, then 
> refresh the source list.
> That will show all servers in the Master Server List.
>
> Sent from my phone, hence this email may be short...
>
>> On 13/03/2020, at 09:24, Cyrille  wrote:
>>
>> Hi Michael,
>> Maybe add the updating of all the repositories at once, as with Andbible
>> and Bishop. This will help users who don't know they are other
>> repository as ebible.org...
>> My 2 cents :)
>>
>> Br Cyrille
>>
>>> Le 12/03/2020 à 20:30, Michael Johnson a écrit :
>>> Hello, my brothers and sisters in Christ.
>>>
>>> I just thought I should post a status on PocketSword work. I have started 
>>> on updating it, but haven't yet gotten to a stable point for testing using 
>>> Test Flight. Right now, it is, unfortunately, on hold, as I have another 
>>> task in the foreground. I finished the main editing of the World English 
>>> Bible, with the exception of still correcting the occasional rare typo. (I 
>>> found one this morning in Ezekiel.) My foreground task at the moment is 
>>> integrating SILE into Haiola for better PDF generation, especially
>>> with mixed complex scripts. After that is done, I hope to focus on 
>>> PocketSword. In its new incarnation, it will generate its own indexes, and 
>>> won't need special server support for that. I'll also fix the key problem 
>>> for when a module goes from locked to unlocked, which of course, will 
>>> happen as copyrights expire and/or special permission is granted.
>>>
>>> Thank you for your patience.
>>>
>>
>> ___
>> 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



___
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