On May 5, 2006, at 4:39 AM, Sergio Queiroz wrote:
Le mercredi 03 mai 2006 à 10:24 -0400, DM Smith a écrit :
Just my thoughts as one who doesn't know Portuguese.
I have followed this thread and the prior ones for some time.
If we continue to leave the current PorAA online, we should fix the
technical difficulties in it. In doing so, it should not be
compared to
any version. That is textual problems such as missing verses,
misspellings, truncated words, wrong verse breaks and the like
should be
ignored. The result will be a module that performs better in the
various
SWORD apps, but has exactly the same content as before. The copyright
and naming issues will be exactly as they are today: still unsolved.
I also think that it is a good thing to seek permission to get a good
version online, perhaps replacing this one.
Hello DM Smith,
thank you for bringing your experience on the subject. Do you think
that
the best source we can get to fix the technical problems in the module
is the one obtained by mod2osis?
Yes. For two reasons:
1) The promise of mod2osis is that if an osis work is extracted with
it and then immediately re-encoded with osis2mod it will produce the
same result. (At this time there is a bug in osis2mod that prevents
this from being true, but that is being fixed.)
2) Using a different source might require obtaining permission. At
least it would require analysis of the copyright status of the
source. With this source, we know that blindly fixing programatic
problems does not change any of the copyright questions that people
have. The fundamental question remains the same.
Or there is a source repository
somewhere for the SWORD project?
There is, but it only consists of the KJV. I have suggested that it
include the "originals" that we convert to modules, in so far as
there are no ownership issues. Some of the "originals" are no longer
available. The repository is for intellectual property of CrossWire.
That is, CrossWire has added value to the KJV with the NT Strong's
markup.
I share your opinion on this matter, I just also think that most
"misspellings" are in fact just encoding errors, for instance, some
"à"
have been encoded as an invalid character (and show as a blank in
gnomesword). So I think these cases should also be fixed (we will
not be
changing the content, just fixing the encoding).
Would you send me your script that fixes these problems? I'd like to
see it. You can send it to me directly.
_______________________________________________
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
