Jump to content

Importing User Bible question


Chuck Schneider

Recommended Posts

After some testing, I went ahead and converted the whole NLB ebook to the format that Accordance requires for importing a user Bible.

 

One of the problems that I'm facing, though, is that many verses start with numbers and not with text. For example, a text with verse two has the number 50 in it, but the import feature errors out saying something like:

 

The reference "2 50"does not have a valid book name.

 

Is there a better way to deal with this than to change the verse line to read:

 

2 Fifty ...

 

?

 

If I have to, I'll do it, but I'm hoping I won't have to.

Link to comment
Share on other sites

In case my first attempt was more confusing than helpful, here's an actual example of the kind of text that I'm speaking of from Ezra 2:3-10:

 

3 2.172 Nachkommen von Parosch,

4 372 Nachkommen von Schefatja,

5 775 Nachkommen von Arach,

6 2.812 Nachkommen von Pahat-Moab, das sind die Nachkommen von Jeschua und Joab,

7 1.254 Nachkommen von Elam,

8 945 Nachkommen von Sattu,

9 760 Nachkommen von Sakkai,

10 642 Nachkommen von Bani,

 

This goes on, of course, through verse 39.

 

Once I have this in the correct format (verse number, verse text, next line, verse number, verse text), for each verse, the Accordance import Bible is surely going to complain that "3 2.172" does not have a valid book name, "4 372" does not have a valid book name, etc., and the only work-around that I can imagine (besides adding weird symbols or letters in front of each number) is to type out the numbers in German.

Link to comment
Share on other sites

I would think that if you put in the chapter:verse number on each verse, it should ignore the number that begins the verse, i.e. 1:1, 1:2 etc.

Link to comment
Share on other sites

I believe we can call this a bug, actually, but we are looking into it and hope to fix or tweak it. I'll keep you posted. In the meantime, Helen's workaround should work.

Link to comment
Share on other sites

Hi All, thanks for the attempt at a work-around, but this doesn't seem to overcome the error.

 

Since it might be considered a bug, I'll just add # in front of each number for now. The # symbol makes the error go away, it won't be confusing in the text and it can be removed later if a fix arrives.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...