> It is nice to know that the formats did change or that there were some
> problems with the system. I have been keep track of the mailing
> list for a
> while, a year + maybe, and I don't recall hearing that it needed
> reimporting for the module. Although I am not aware of how to do a
> reimport,
It is nice to know that the formats did change or that there were some
problems with the system. I have been keep track of the mailing list for a
while, a year + maybe, and I don't recall hearing that it needed
reimporting for the module. Although I am not aware of how to do a
reimport, I am on
It was a whole different process before. It was marked with a different
format and imported with a different importer. This process didn't
recognize some of these complexities in the RSV.
--Chris
Dan Adams wrote:
I am curious, does anyone know that it was marked incorrectly before? I
know t
I am curious, does anyone know that it was marked incorrectly before? I
know that I am not one who would have the ability or knowledge of how to
check. I am just curious, because it would be pointless for the people who
import it to import it and not have the changes in place.
Dan
On
Sat, 13
Yep, it's all marked correctly in our OSIS docuement though, and as soon
as the OSIS importers seem up to the task, we'll import the text and
release it.
--Chris
Sean Boisen wrote:
A similar problem occurs in Matt 18, where verse 11 is apparently from a
manuscript tradition which the RSV does
A similar problem occurs in Matt 18, where verse 11
is apparently from a manuscript tradition which the RSV does not include. So
rather than going directly from verse 10 to 12, all subsequent verses in the
chapter are off by one.
Sean
www.semanticbible.com
I have had the RSV converted to OSIS format for about a year now, but
haven't had a usable importer to run on it. Troy thinks he got his
importer working last week. Unfortunately, OSIS has changed a lot in
the last year, so I'll have to update the text (and then work thorugh
any ideosyncracie
> Unfortunately, that's definately not the only problem with the
> RSV module - I
> just happened to look at the Psalms (e.g., Ps. 3) and found that
> the headings
> ("A Psalm of David...") were converted to the first verse, and the actual
> verse numbers are thus off by one. I suspect that will b
(This is my last post for the day, I promise).
Unfortunately, that's definately not the only problem with the RSV module - I
just happened to look at the Psalms (e.g., Ps. 3) and found that the headings
("A Psalm of David...") were converted to the first verse, and the actual
verse numbers are
Thank you. This all works for me, and gives me a path forward.
I was trying to use OSIS format rather than the (Sword-specific?) imp format,
but I'll cheerfully abandon that for something I can actually get to work!
Tim
___
sword-devel mailing list
[
I have the RSV in formatted ASCII; if / when I get a my-format2mod working
I'll be happy to do a comparison to find the problem areas. Perhaps it's
just that one!
Tim
On Monday 24 November 2003 3:36 pm, Stephen Denne wrote:
> though. Perhaps someone could use it to automatically identify a com
> > So, now my confidence in that module is shaken.
>
> Well, I found several mistakes in one of modules - unfortunately, the
> one submitted by me (PBG - now it's being checked). So I know that
> proofreading is very important... Maybe starting the new thread "RSV" on
> the forum and listing mist
The details are at
http://www.crosswire.org/sword/develop/swordmodule/index.jsp
> examples I can
> find are compressed, but before one can compress a module one must have a
> working non-compressed version, right? I get blank text.
mod2imp will give you an uncompressed text ready for importing b
> Tim Meneely, Pittsburgh PA USA, wrote
> Is there somewhere other than the developer's list
> more appropriate to ask these module questions?
As far as I know you can try
http://www.crosswire.org/forums/mvnforum/index
(it is not official forum, is it? - anyway, I posted my question there
and g
14 matches
Mail list logo
