<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">Le 13/03/2020 à 12:55, David Haslam a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:kapBnn2riFJkuoz54eMfaKuzpkjDhToKRc9g3XlNkc19rbkAS0v2NmD9JdIwr4QhEelgn66C7oT1jn6jHwpQDWRbaL1gj9ZOi5osAHDZOvM=@protonmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div>Cyrille,</div>
<div><br>
</div>
<div>I’m not in favour of removing modules from CrossWire simply
because one of the affiliated repositories has a similar module.</div>
</blockquote>
Why not?<br>
<blockquote type="cite"
cite="mid:kapBnn2riFJkuoz54eMfaKuzpkjDhToKRc9g3XlNkc19rbkAS0v2NmD9JdIwr4QhEelgn66C7oT1jn6jHwpQDWRbaL1gj9ZOi5osAHDZOvM=@protonmail.com">
<div><br>
</div>
<div>Nor should it ever be expected that a module published by
eBible.org would include an Obsoletes key <caret></caret>with
one of CrossWire’s modules as the parameter.</div>
</blockquote>
<br>
Idem why not?<br>
<blockquote type="cite"
cite="mid:kapBnn2riFJkuoz54eMfaKuzpkjDhToKRc9g3XlNkc19rbkAS0v2NmD9JdIwr4QhEelgn66C7oT1jn6jHwpQDWRbaL1gj9ZOi5osAHDZOvM=@protonmail.com">
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>David</div>
<div><br>
</div>
<div id="protonmail_mobile_signature_block">
<div>Sent from ProtonMail Mobile</div>
</div>
<div><br>
</div>
<div><br>
</div>
On Fri, Mar 13, 2020 at 08:11, Cyrille <<a
href="mailto:lafricain79@gmail.com" class=""
moz-do-not-send="true">lafricain79@gmail.com</a>> wrote:
<blockquote class="protonmail_quote" type="cite"> Dear all,<br>
Actually my worry was about a question between the module team.
We have<br>
duplicated modules, in Crosswire and in ebible.org. Often the
ebible.org<br>
are updated and not in Crosswire. And we are very slow to update
the new<br>
module in Crosswire. Then I proposed to remove in the Crosswire
repo,<br>
all the old modules with issue reported on the bug tracker. But
the<br>
question was: What to do if the users don't know how to change
the repo,<br>
as it happened in the other post on this list, some of us didn't
know<br>
how to change for IBT in Xiphos.<br>
I Bibletime, Andbible and Bishop, the repositories are updated
all<br>
together, but not in Xiphos. I opened an issue about this on the
xiphos git.<br>
For this reason I proposed this for Swordpocket, even if it
seems to be<br>
more or less easier than for Xiphos.<br>
<br>
Br Cyrille<br>
<br>
Le 13/03/2020 à 04:14, Nic Carter a écrit :<br>
> On the downloads screen, tap on the folder icon in the top
right corner, then refresh the source list.<br>
> That will show all servers in the Master Server List.<br>
><br>
> Sent from my phone, hence this email may be short...<br>
><br>
>> On 13/03/2020, at 09:24, Cyrille
<a class="moz-txt-link-rfc2396E" href="mailto:lafricain79@gmail.com"><lafricain79@gmail.com></a> wrote:<br>
>><br>
>> Hi Michael,<br>
>> Maybe add the updating of all the repositories at once,
as with Andbible<br>
>> and Bishop. This will help users who don't know they
are other<br>
>> repository as ebible.org...<br>
>> My 2 cents :)<br>
>><br>
>> Br Cyrille<br>
>><br>
>>> Le 12/03/2020 à 20:30, Michael Johnson a écrit :<br>
>>> Hello, my brothers and sisters in Christ.<br>
>>><br>
>>> 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<br>
>>> 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.<br>
>>><br>
>>> Thank you for your patience.<br>
>>><br>
>><br>
>> _______________________________________________<br>
>> sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
>> <a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
>> Instructions to unsubscribe/change your settings at
above page<br>
> _______________________________________________<br>
> sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
> <a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
> Instructions to unsubscribe/change your settings at above
page<br>
<br>
<br>
<br>
_______________________________________________<br>
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page</blockquote>
<div><br>
</div>
<div><br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page</pre>
</blockquote>
<br>
</body>
</html>