<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
All front ends should display all text with the punctuation as
given. Anything other than that is a bug that must be fixed.<br>
<br>
They will differ on their styling of that text.<br>
<br>
On 03/06/2012 02:17 PM, Kahunapule Michael Johnson wrote:
<blockquote cite="mid:4F5662B0.7000303@mpj.cx" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
On 03/06/2012 12:47 AM, Jonathan Morgan wrote:
<blockquote
cite="mid:CAOOKcO4gsOzC46Rwke5=XYHrCq=XVVtcwORw=vWBTKx6w7r+3Q@mail.gmail.com"
type="cite">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<ol>
<li>You accurately preserve all of the original text and
punctuation (including quotation punctuation) exactly as
it was in the original USFM. This involves the complete
process from module creation to display in all front
ends. This is an absolute requirement with respect to
the canonical text. If this condition isn't met, then I
don't have permission to convert these Scriptures to
Sword format, nor do you have such permission.<br>
</li>
</ol>
</div>
</blockquote>
<div><br>
I'm afraid I do not understand how either you or CrossWire can
ensure that *all* front ends display all text correctly. I
have no idea from your descriptions whether BPBible or any
other frontends would meet the requirements currently.
However, even if they did it is conceivable that a new front
end is created which does not meet the requirements. Does
this mean that CrossWire immediately loses permission to
distribute the text for use in any of the front ends?
(including all the front ends that are compliant, of course).<br>
</div>
</blockquote>
<br>
That is a very good question-- one that I really don't want to
have to raise with the copyright owners!<br>
<br>
At a minimum, noncompliant front ends may not use the texts if
they cannot do so without corrupting them.<br>
<br>
I'm not talking about getting all of the formatting correct. I'm
just talking about exactly preserving all text and punctuation of
the canonical text. If a front end cannot do that, it should be
withdrawn from public distribution, as it is clearly a threat to
our ability to distribute Scriptures. Actually, there is a greater
threat that copyrights: the fear of God. I wouldn't want to be
caught dead or alive corrupting the Holy Bible. I would think that
you wouldn't, either. It is a fearsome thing to fall into the
hands of God when He is angry.<br>
<br>
I'm glad He is also merciful and full of grace, but I don't want
to test His limits.<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<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>