<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Thank you, Troy! With these explanations I understand the big
picture of markup transformation and filters a bit better!<br>
</p>
<p>For now, I'll go forward with the FMT_OSIS option for the
MarkupFilterMgr in node-sword-interface. I understand from your
explanations that this produces similar results as when
initializing SWMgr without any markup filters.</p>
<p>When I started out using SWORD in node-sword-interface I did not
set any filters at the time (not really knowing about it as a
newbie). Since then I have somehow handled the OSIS markup and I
am not unhappy with the formatting/styling in the frontend at this
point. It could probably be better and I have certainly not
explored all variants, yet ... so, I will keep the filter
possibilities on my mind for future adaptations!</p>
<p>Have a blessed Easter celebration :)</p>
<p>Tobias<br>
</p>
<div class="moz-cite-prefix">On 4/6/23 10:22 PM, Troy A. Griffitts
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:4A6F65DA-A9A8-42DA-9A9B-0C3CDCF833A8@crosswire.org">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Hi Tobias,<br>
<br>
Great that the encoding issue is solved. If you really want to
handle OSIS yourself (which is a lot of work) I would recommend
requesting OSIS markup. Remember, we support various markup
formats. Not everything is OSIS. If you ask for OSIS then you
should get generally the same markup you received previously, from
newer modules which are almost exclusively OSIS-- most markup will
just be passthru. If a user installs a GBF or ThML or some other
markup module, we will try our best to convert to OSIS on the fly
for you.<br>
<br>
Though I wouldn't recommend this path long-term. Quite a bit of
time goes into the various render filters to handle all the
nuances of our supported markup formats. I would recommend using
one of our render filter sets eventually (preferably WEBIF, XHTML,
or HTMLHREF) and let us give you nice HTML output with styles you
can adjust as you see fit. This will focus that burden of support
for new markup on the engine instead of your frontend. I don't
know of any other frontend team that tries to handle OSIS
themselves.<br>
<br>
If you feel you might lose control of how you want output, we have
various means to inject modifications, of you don't like what we
give you, but honestly, if you have a good objection, we're likely
to adjust the output for you. We try our best to just give classed
containers: divs and spans, etc., and there is an API call to give
you our default styles which give a sane styling for classes.
Typically, the strategy is to include these styles first in your
output, and then override anything you don't like afterward. This
way, if something new is added in the engine, at least you will
get some sane style applied for it. The call is:<br>
<br>
SWModule::getRenderHeader()<br>
<br>
Hope this helps a bit. Thanks for letting us know your progress. I
am excited about your app!<br>
<br>
<div class="gmail_quote">On April 6, 2023 12:36:41 PM MST, Tobias
Klein <a class="moz-txt-link-rfc2396E" href="mailto:contact@tklein.info"><contact@tklein.info></a> wrote:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<p>Hi Troy,</p>
<p>Thanks for your help! I have just tried using this
parameter for the construction of SWMgr and it looks good.<br>
I had another look at the example for the German Rieger
commentary where I observed the encoding issues before and
they are gone now!</p>
<p>Well, I guess I could have asked one or the other question
before ... but as long as a bit of code reading and
experimenting results in a solution, I'm usually fine.<br>
Thank you! I do appreciate all your efforts.</p>
<p>I do have another question regarding the construction of
MarkupFilterMgr.<br>
If I want to apply the encoding filter for UTF8, but do not
need the markup filter manager for XHTML is it ok to perform
the construction like this?<br>
<br>
new MarkupFilterMgr(sword::FMT_UNKNOWN, sword::ENC_UTF8)</p>
<p>I checked the code in markupfiltmgr.cpp and found that the
implementation of MarkupFilterMgr::createFilters does not
consider the case FMT_UNKNOWN, so in this case it would
simply not add any specific markup filter, right? Since I
haven't used any markup filters so far and my code already
depends on the standard output generated by the SWORD engine
I did not want to add a markup filter for the time being.</p>
<p>Is there another way to apply the UTF8 encoding without
using MarkupFilterMgr? (It just looks a bit weird when I
look at the construction now)<br>
<br>
Best regards,<br>
Tobias<br>
<br>
PS:<br>
I think one thing we could do one of these days is check
together with other frontend developers whether some helper
functions created in various frontends could also be moved
into the SWORD library.<br>
<br>
Consider some of the helper functions implemented here:<br>
<a class="moz-txt-link-freetext"
href="https://github.com/ezra-bible-app/node-sword-interface/blob/master/src/sword_backend/module_helper.cpp"
moz-do-not-send="true">https://github.com/ezra-bible-app/node-sword-interface/blob/master/src/sword_backend/module_helper.cpp</a><br>
<a class="moz-txt-link-freetext"
href="https://github.com/ezra-bible-app/node-sword-interface/blob/master/src/sword_backend/repository_interface.cpp"
moz-do-not-send="true">https://github.com/ezra-bible-app/node-sword-interface/blob/master/src/sword_backend/repository_interface.cpp</a></p>
<br>
<div class="moz-cite-prefix">On 4/3/23 9:27 PM, Troy A.
Griffitts wrote:<br>
</div>
<blockquote type="cite"
cite="mid:B751B62C-1202-4903-AE21-A02B6CB47012@crosswire.org">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
Hi Tobias,<br>
<br>
Yes, our documentation certainly needs much improvement. I
am surprised how far you've gone with so few questions. You
have a great talent for figuring things out. I wouldn't
worry about the guts of the details in the encoding filters.
All you should need to do is specify your desired output on
the SWMgr you use for rendering with something like:<br>
<br>
SWMgr mgr(new MarkupFilterMgr(sword::FMT_XHTML,
sword::ENC_UTF8));<br>
<br>
Let me know if you'd like help,<br>
<br>
Troy<br>
<br>
<br>
<div class="gmail_quote">On April 3, 2023 11:18:29 AM MST,
Tobias Klein <a class="moz-txt-link-rfc2396E"
href="mailto:contact@tklein.info" moz-do-not-send="true"><contact@tklein.info></a>
wrote:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<p>Thanks Troy!</p>
<p>I'll have a look at the EncodingFilters.</p>
<p>I think this is something not fully clear from the
SWORD documentation/examples.</p>
<p>Maybe these transformation points you had mentioned
in the thread below should be described somewhere in
the developer wiki?<br>
</p>
<p>Best regards,<br>
Tobias<br>
</p>
<div class="moz-cite-prefix">On 4/3/23 6:45 PM, Troy A.
Griffitts wrote:<br>
</div>
<blockquote type="cite"
cite="mid:B112C535-F787-4EA5-AADD-8DD886CE0DA1@crosswire.org">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
Dear Tobias,<br>
<br>
Please be sure to note my comment to you below in this
thread. It is likely the cause of your rendering
issues, while other apps have no problems.<br>
<br>
In brief, it says that I haven't seen anywhere that
you tell SWORD what markup and encoding you want from
the engine. If this is the case you will get whatever
the modules are encoded / marked up as, which might be
various things.<br>
<br>
Hope this helps,<br>
<br>
Troy<br>
<br>
<div class="gmail_quote">On January 22, 2023 12:03:22
PM MST, "Troy A. Griffitts" <a
class="moz-txt-link-rfc2396E"
href="mailto:scribe@crosswire.org"
moz-do-not-send="true"><scribe@crosswire.org></a>
wrote:
<blockquote class="gmail_quote" style="margin: 0pt
0pt 0pt 0.8ex; border-left: 1px solid rgb(204,
204, 204); padding-left: 1ex;">
<p>Hey guys,</p>
<p>Sorry for not jumping in on this thread more
quickly.</p>
<p>Please remember, SWORD has 4 transformation
points, each moving from the module source (as
described in the .conf file) to the client's
request:</p>
<p>RenderFilters - markup, e.g., GBF, ThML, OSIS
-> XHTML<br>
</p>
<p>StripFilters - prep before searching<br>
</p>
<p>OptionFilters - turning on an off markup in the
text stream based on user options, e.g., Strongs
Number, Words of Christ in Red, etc.<br>
</p>
<p>EncodingFilters - e.g., 8859 - > UTF-8</p>
<p><br>
</p>
<p>Module team: be sure the module has the correct
Encoding value in the .conf file (or the
default)</p>
<p>Tobias, be sure you are creating your SWMgr
with the correct MarkupFilterMgr to do the
transformation you desire, e.g., see:</p>
<p><a class="moz-txt-link-freetext"
href="https://crosswire.org/svn/sword/trunk/examples/cmdline/outrender.cpp"
moz-do-not-send="true">https://crosswire.org/svn/sword/trunk/examples/cmdline/outrender.cpp</a></p>
<p>Hope this helps,</p>
<p>Troy<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 1/22/23 10:39, Fr
Cyrille wrote:<br>
</div>
<blockquote type="cite"
cite="mid:c7a55f24-f1b5-f3c3-dc67-1f54175c7e37@tiberiade.be">
<meta http-equiv="Content-Type"
content="text/html; charset=UTF-8">
HI David,<br>
If you send me the file, I can convert it
quickly in osis. I script it from imp to usfm
and the with u2o.py.<br>
<br>
<div class="moz-cite-prefix">Le 22/01/2023 à
16:54, David Haslam a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:RxtUZFbR-TF0H0LJXbF7k_nQ9MAp48rxhOa8mbseA38Ph7NFq2Vj8O6zLuSwKooMtzkxS4q1kW1DKZgGyqY65jjgmWaNlascerCVlZLh35M=@protonmail.com">
<meta http-equiv="content-type"
content="text/html; charset=UTF-8">
<div dir="auto">Thanks Tobias,</div>
<div dir="auto"><br>
</div>
<div dir="auto">The problem is that CrossWire
no longer accepts module submissions that
use IMP format for the build process.</div>
<div dir="auto"><br>
</div>
We’d need to have a script (or equivalent
TextPipe filter) to convert IMP to OSIS
(whether directly or indirectly through some
other intermediate file format).
<div dir="auto"><br>
</div>
<div dir="auto">I’m not currently in a
practical position to work on that kind of
task.</div>
<div dir="auto">Is anyone else up to it?<caret></caret></div>
<div dir="auto"><br>
</div>
<div dir="auto">Best regards,<br>
<div dir="auto"><br>
</div>
<div dir="auto">David</div>
<div><br>
</div>
<div id="protonmail_mobile_signature_block">
<div>Sent from Proton Mail for iOS</div>
</div>
<div><br>
</div>
<div><br>
</div>
On Sun, Jan 22, 2023 at 15:39, Tobias Klein
<<a href="mailto:contact@tklein.info"
class="moz-txt-link-freetext"
moz-do-not-send="true">contact@tklein.info</a>>
wrote:
<blockquote class="protonmail_quote"
type="cite">
<p>The FinPR module that David sent me
works fine without rendering issues!
(see screenshot below)<br>
</p>
<p>It would be good to upgrade the module
in the repo accordingly.<br>
</p>
<p>Best regards,<br>
Tobias<br>
</p>
<p><img
src="cid:part1.vYS1WII0.eryF0oRZ@crosswire.org"
alt=""
src-original-pm-cid="imap://fr%2Ecyrille%40tiberiade%2Ebe@ssl0.ovh.net:993/fetch%3EUID%3E.INBOX%3E8824?header=quotebody&part=1.1.2.2&filename=inccpcpbnhmlapdi.png"
class="" moz-do-not-send="true"></p>
<div class="moz-cite-prefix">On 1/22/23
8:31 AM, David Haslam wrote:<br>
</div>
<blockquote type="cite">
<div dir="auto">Thanks Kristóf.</div>
<div dir="auto"><br>
</div>
<div dir="auto"><span style="San
Francisco", Helvetica, Arial,
sans-serif; letter-spacing: normal;
orphans: auto; text-align: start;
text-indent: 0px; text-transform:
none; white-space: normal; widows:
auto; word-spacing: 0px;
-webkit-text-size-adjust: none;
-webkit-text-stroke-width: 0px;
text-decoration: none; display:
inline !important; float: none;"
dir="auto">The rendering problem
could have been fixed a decade
ago!!!</span><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Checking through my
email archives yesterday, I discovered
that I had rebuilt the FinPR module
exactly 10 years ago! That rebuild <span
style="color: var(--text-color);
background: var(--bg-color);"
dir="auto">used mod2imp and imp2vs
and included </span><span
style="color: var(--text-color);
background: var(--bg-color);"
dir="auto">a fix to the text
encoding implemented on the IMP text</span><span
style="color: var(--text-color);
background: var(--bg-color);"
dir="auto"> file). The message was
sent to the modules address on
2013-01-21 but presumably never
progressed by Chris Little who was
then still supposed to be
responsible for module releases and
updates. He went permanently AWOL
from CrossWire around that time. </span></div>
<div dir="auto"><span style="color:
var(--text-color); background:
var(--bg-color);" dir="auto"><br>
</span></div>
<div dir="auto">Back then we had not
narrowed the policy for submitted
source text to be OSIS XML only. </div>
<div dir="auto"><br>
</div>
<div dir="auto">I wrote privately to
Tobias last night, forwarding the
email of 10 years ago complete with
both attachments. He will examine
those today.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Aside: I also replaced
<…> by {…} where these had
wrapped the ch:vs references that
recorded av11n in the original
upstream source. In 2012, there had
been no suitable av11n available in
SWORD but which we do have more
recently.</div>
<div dir="auto"><br>
</div>
<div dir="auto">mod2osis should not be
used, as has already been noted.</div>
A round trip with mod2osis and osis2mod
is not lossless, unlike one <span
style="color: var(--text-color);
background: var(--bg-color);"
dir="auto">with mod2imp and imp2vs.</span>
<div dir="auto">
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Best regards,</div>
<div dir="auto"><br>
</div>
<div dir="auto">David</div>
<div><br>
</div>
<div
id="protonmail_mobile_signature_block">
<div>Sent from Proton Mail for iOS</div>
</div>
<div><br>
</div>
<div><br>
</div>
On Sat, Jan 21, 2023 at 23:15, Kristof
Szabo <<a
href="mailto:kristof.szabo@web.de"
class="moz-txt-link-freetext"
moz-do-not-send="true">kristof.szabo@web.de</a>>
wrote:
<blockquote class="protonmail_quote"
type="cite">
<div dir="ltr">I managed to get Ezra
running (it was some libicu70
mess), and yes, the accented
characters in this module are
broken (as other modules accented
characters are OK; I assume it is
not a font issue). I tried the
conf file change, but it didn't
work either.
<div><br>
</div>
<div>The mitigation was to rebuild
the module, mod2osis leaves some
garbage in the OSIS, but that
would be easy to clean, anyway
osis2mod is possible with this
garbage left in and tada we have
a proper accents.</div>
<div><br>
</div>
<div><img
src="cid:part2.hDEilMi0.FuFLwKdw@crosswire.org"
alt="image.png"
style="margin-right: 0px;"
class=""
src-original-pm-cid="imap://fr%2Ecyrille%40tiberiade%2Ebe@ssl0.ovh.net:993/fetch%3EUID%3E.INBOX%3E8824?header=quotebody&part=1.1.2.3&filename=image.png"
moz-do-not-send="true"
width="486" height="255"><br>
</div>
<div>
<div><br>
</div>
<div>As the module was updated
last only 3,5 yrs ago I assume
the maintainer is still
active, ie. they can be
reached.</div>
<div><br>
</div>
<div>Or I can have a look too,
the challenge is, that such a
module rebuild can open
pandora's box, if I run some
tests (<a
href="https://github.com/krisek/sword-test"
moz-do-not-send="true"
class="moz-txt-link-freetext">https://github.com/krisek/sword-test</a>)
or David checks them, then for
sure there will be some
issues. I'm happy to fix some
of them, but I definitely do
not speak Finnish, so I'm not
sure this would be a
responsible action. If Dom
gives me the go I can fix
syntax & submit, but I
don't want to end up in the
rabbit hole :) Best would be
to reach out to the original
maintainer.</div>
</div>
<div><br>
</div>
<div>Kind regards,</div>
<div>k-</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On
Sat, Jan 21, 2023 at 8:26 PM
Greg Hellings <<a
href="mailto:greg.hellings@gmail.com"
moz-do-not-send="true"
class="moz-txt-link-freetext">greg.hellings@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="auto">Is Ezra properly
setting encoding on the
content it renders? Is it
maybe setting a font that
doesn't have the proper code
points?
<div dir="auto"><br>
</div>
<div dir="auto">--Greg</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr"
class="gmail_attr">On Sat,
Jan 21, 2023, 13:12 Tobias
Klein <<a
href="mailto:contact@tklein.info"
moz-do-not-send="true"
class="moz-txt-link-freetext">contact@tklein.info</a>>
wrote:<br>
</div>
<blockquote
class="gmail_quote"
style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div>
<p>Hi Kristof, David,</p>
<p>Adding Encoding=UTF-8
to the module conf file
~/.sword/mods.d/finpr.conf does not solve my issue.</p>
<p>The text still looks
the same as before ...</p>
<p>What else could I do to
further debug this?<br>
</p>
<p>Best regards,<br>
Tobias<br>
</p>
<div>On 1/21/23 5:18 PM,
Kristof Szabo wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">Hi
Thomas,</div>
<div dir="ltr">
<div><br>
</div>
<div>I suppose the
problem is that
finpr.conf
contains no
encoding
information (check
the Hun* modules
for reference),
and if there is
nothing specified
Latin-1 is the
default. mod2osis
(shouldn't be used
!! :)) shows that
the module is in
UTF-8, so there is
a misalignment.</div>
<div><br>
</div>
<div><a
href="https://wiki.crosswire.org/DevTools:conf_Files#:~:text=Plaintext-,Encoding,-UTF%2D8%0AUTF"
rel="noreferrer"
moz-do-not-send="true" class="moz-txt-link-freetext">https://wiki.crosswire.org/DevTools:conf_Files#:~:text=Plaintext-,Encoding,-UTF%2D8%0AUTF</a><br>
</div>
<div><br>
</div>
<div>Kind regards,</div>
<div>Kristof</div>
</div>
<br>
<div
class="gmail_quote">
<div dir="ltr"
class="gmail_attr">On
Sat, Jan 21, 2023
at 4:49 PM David
Haslam <<a
href="mailto:dfhdfh@protonmail.com"
rel="noreferrer"
moz-do-not-send="true" class="moz-txt-link-freetext">dfhdfh@protonmail.com</a>>
wrote:<br>
</div>
<blockquote
class="gmail_quote"
style="margin:0px
0px 0px
0.8ex;border-left:1px
solid
rgb(204,204,204);padding-left:1ex">
<div>
<div>Hi Thomas,</div>
<div><br>
</div>
<div>What about
other Finnish
modules?</div>
eg. FinPR92,
FinRK,
FinSTLK2017<br>
<div><br>
</div>
<div>Presumably
you already
tested (eg)
German modules
and found that
umlauts and
eszett are
both rendered
aright?</div>
<div><br>
</div>
<div>Btw. FinPR
renders aright
in PocketSword
(iOS/iPadOS).</div>
<div><br>
</div>
<div>David</div>
<div><br>
</div>
<div
id="m_-5808618193163782311m_-4503619881993391118m_4402206924634599083m_-2663245799789630859protonmail_mobile_signature_block">
<div>Sent from
Proton Mail
for iOS</div>
</div>
<div><br>
</div>
<div><br>
</div>
On Sat, Jan 21,
2023 at 15:25,
Tobias Klein
<<a
href="mailto:contact@tklein.info"
rel="noreferrer" moz-do-not-send="true" class="moz-txt-link-freetext">contact@tklein.info</a>>
wrote:
<blockquote
type="cite">
<p>Hi,<br>
<br>
</p>
<p>When
retrieving the
text of the
FinPR module I
am getting
some rendering
issues with
the Finnish
Umlauts. This
is based on a
user's problem
report.<br>
</p>
<p><br>
Romans 5:8
returns like
this in
node-sword-interface
/ Ezra:<br>
</p>
<p>Mutta
Jumala
osoittaa
rakkautensa
meit� kohtaan
siin�, ett�
Kristus, kun
me viel�
olimme
syntisi�,
kuoli meid�n
edest�mme.</p>
<p><br>
While it
should like
like this
(rendered text
copied from
Xiphos):</p>
<p><span
style="color:rgb(0,0,0);font-family:none;font-size:medium;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration:none;float:none;display:inline">Mutta
Jumala
osoittaa
rakkautensa
meitä kohtaan
siinä, että
Kristus, kun
me vielä
olimme
syntisiä,
kuoli meidän
edestämme.</span></p>
<p><span
style="color:rgb(0,0,0);font-family:none;font-size:medium;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration:none;float:none;display:inline"><br>
</span></p>
<p><span
style="color:rgb(0,0,0);font-family:none;font-size:medium;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration:none;float:none;display:inline">This
occurs both on
Linux and
macOS (have
not tested on
Windows yet).</span></p>
<p><span
style="color:rgb(0,0,0);font-family:none;font-size:medium;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration:none;float:none;display:inline">Any
pointers what
could be the
root cause? I
generally have
not observed
rendering
issues with
other modules.</span></p>
<p><span
style="color:rgb(0,0,0);font-family:none;font-size:medium;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration:none;float:none;display:inline"><br>
</span></p>
<p><span
style="color:rgb(0,0,0);font-family:none;font-size:medium;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration:none;float:none;display:inline">Best
regards,<br>
Tobias<br>
</span></p>
</blockquote>
</div>
_______________________________________________<br>
sword-devel
mailing list: <a
href="mailto:sword-devel@crosswire.org" rel="noreferrer"
moz-do-not-send="true"
class="moz-txt-link-freetext">sword-devel@crosswire.org</a><br>
<a
href="http://crosswire.org/mailman/listinfo/sword-devel"
rel="noreferrer
noreferrer"
moz-do-not-send="true"
class="moz-txt-link-freetext">http://crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to
unsubscribe/change
your settings at
above page<br>
</blockquote>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" rel="noreferrer" moz-do-not-send="true" class="moz-txt-link-freetext">sword-devel@crosswire.org</a>
<a href="http://crosswire.org/mailman/listinfo/sword-devel" rel="noreferrer" moz-do-not-send="true" class="moz-txt-link-freetext">http://crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page
</pre>
</blockquote>
</div>
_______________________________________________<br>
sword-devel mailing list: <a
href="mailto:sword-devel@crosswire.org" rel="noreferrer"
moz-do-not-send="true"
class="moz-txt-link-freetext">sword-devel@crosswire.org</a><br>
<a
href="http://crosswire.org/mailman/listinfo/sword-devel"
rel="noreferrer
noreferrer"
moz-do-not-send="true"
class="moz-txt-link-freetext">http://crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to
unsubscribe/change your
settings at above page<br>
</blockquote>
</div>
_______________________________________________<br>
sword-devel mailing list: <a
href="mailto:sword-devel@crosswire.org"
moz-do-not-send="true"
class="moz-txt-link-freetext">sword-devel@crosswire.org</a><br>
<a
href="http://crosswire.org/mailman/listinfo/sword-devel"
rel="noreferrer"
moz-do-not-send="true"
class="moz-txt-link-freetext">http://crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to
unsubscribe/change your settings
at above page<br>
</blockquote>
</div>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:sword-devel@crosswire.org" moz-do-not-send="true">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://crosswire.org/mailman/listinfo/sword-devel" moz-do-not-send="true">http://crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page
</pre>
</blockquote>
</blockquote>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:sword-devel@crosswire.org" moz-do-not-send="true">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://crosswire.org/mailman/listinfo/sword-devel" moz-do-not-send="true">http://crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page
</pre>
</blockquote>
<br>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org" moz-do-not-send="true">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://crosswire.org/mailman/listinfo/sword-devel" moz-do-not-send="true">http://crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page
</pre>
</blockquote>
</blockquote>
</div>
<div class="k9mail-signature">-- <br>
Sent from my Android device with K-9 Mail. Please
excuse my brevity.</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" moz-do-not-send="true">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://crosswire.org/mailman/listinfo/sword-devel" moz-do-not-send="true">http://crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page
</pre>
</blockquote>
</blockquote>
</div>
<div class="k9mail-signature">-- <br>
Sent from my Android device with K-9 Mail. Please excuse
my brevity.</div>
</blockquote>
</blockquote>
</div>
<div class="k9mail-signature">-- <br>
Sent from my Android device with K-9 Mail. Please excuse my
brevity.</div>
</blockquote>
</body>
</html>