Jump to content

Problem Importing a Qumran Text through User Files/Import Bible Text


mbjohn2

Recommended Posts

Greetings, 

 

I'm trying to import a Qumran text through the "Import Bible Text" feature, and I'm running into a versification problem. I am trying to import a text that corresponds to 1QHa 2:12–28:15, but I receive a verse reference error (see below). I can import a text that runs up to 1QHa 16:42, but there is something about the versification at the transition from 16:42-17:1 that prevents me from importing my entire text of 1QHa. Does anyone know how to address this problem?

 

Error:

The entry "1QHa 17:1" is not a valid verse reference. This error occurs after the reference "1QHa 16:42". 

 
All lines must begin with a valid verse reference for a single verse on that line. 
 
All book names cannot use a space within the name.
 

post-31929-0-32612000-1553097541_thumb.jpg

Link to comment
Share on other sites

Version 12.3.3, released last night improves Qumran text import. Which version are you running? 

Link to comment
Share on other sites

You are right, there is an error here.  The message should say that "1QHa 16:42" is not a valid verse reference.  One of the limitations of our text import is that your verses must match up exactly with whatever purchased module you have used for versification.  So if your file contains "1QHa 16:42", it doesn't know what to match it against, since that is not in our Qumran.

 

If your file doesn't contain "1QHa 16:42", you can post it as a reply here I'll see if there is another bug at work.

 

If it does contain "1QHa 16:42", then you could probably get away with the import by appending that verse to the end of the line containing "1QHa 16:41".

Link to comment
Share on other sites

Thanks Silas—I removed 16:42, and received a slightly different error:

 

"The entry "1QHa 17:1" is not a valid verse reference. This error occurs after the reference "1QHa 16:41". 

 
All lines must begin with a valid verse reference for a single verse on that line. 
 
All book names cannot use a space within the name."
 
I think I added 1QHa 16:42 earlier as I was trying to troubleshoot. Some columns of 1QHa have 42 lines, and I thought Accordance might expect there to be a placeholder for that line or something.
 
I was inspired to give this a try once I saw the details on the latest update. I am using 12.3.3.
Link to comment
Share on other sites

Ok, that makes sense.  I'd thought I'd thoroughly tested this, but there must be something I missed.

 

Here is a file I've just confirmed I am able to import using 12.3.3:

 

QumranSimpleVersification.txt

 

Importing it with our "QUMRAN.atext" module as the versification should give a text where the content of every verse is "-".

 

Can you see if importing this one gives you any trouble?

 

Also, are you able to post the one that is giving you trouble on here, so I can take a look at it?

Edited by Silas Marrs
Link to comment
Share on other sites

I ran into the same error with your text, but I think the problem is that I was using the Qumran non-biblical English versification. When I selected the Qumran non-biblical manuscripts versification it seems to work fine. I'll work with you text file as a template and see how it goes. Thanks for your help.

  • Like 1
Link to comment
Share on other sites

It's possible there are one or two verses different between the Qumran non-biblical English, and Qumran non-biblical manuscripts.

 

A good check you can do when importing a text is that the number of lines in your text file should exactly match the verse number of the last verse in the module you use for versification.  For instance, if I'm importing up to "4Q165 f10:3" and using QUMENG, I know there should be 5141 lines in my text file because it says "Verse 5141 of 36636", when I scroll to that verse in QUMENG.

  • Like 1
Link to comment
Share on other sites

I keep getting unwanted spaces before square brackets when my text displays in Accordance. Is there a quick or obvious fix for this? I'm hesitant to post my entire text publicly, otherwise I'd post an example.

 

Nevermind: I figured it out!

Edited by mbjohn2
  • Like 1
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...