Jump to content

Crashing while Importing Bible Text


Dan McClellan

Recommended Posts

I'm using version 10.4.5, and when I try to import a user Bible, it crashes as soon as I assign a name. The text shows up in the Library upon restart, but it's empty. I believe I've followed the formatting instructions to the letter. Any idea what might be causing this? 

Link to comment
Share on other sites

I know that I had this quite often. Do you use non Mac Roman characters or German Umlaut? They are not supported until now. Is it possible to writhe the name here in the forums? 

 

Today with 11.0.8 I have the same with User Tools

 

Greetings

 

Fabian

Link to comment
Share on other sites

The Bible is in Portuguese. I saved the document in TextEdit in the Mac Roman style. I don't know if there were any incompatible characters.

 

There aren't umlauts, but ç appears, as well as several other diacritics over vowels.  

 

What name, specifically?

Link to comment
Share on other sites

Try to use a Bible name without  ç  or so.

 

Download TextWrangler from the AppStore or direct by http://barebones.com(whatever you prefer) and open it there, and try to choose as Mac Roman and Mac CR line breaks. If there are some characters that is not supported, that will give you a response. Maybe you can change them or save it as UTF-8. But then you loose Analytics.

 

Greetings

 

Fabian

Link to comment
Share on other sites

Thanks for the recommendations. I'll take a look. I removed all the diacritics I could find, but it still crashed. I saved it as UTF-8 and it crashed, but a few seconds later in the importing process.

Link to comment
Share on other sites

Do you have     <>      in the text? This was by me once.

 

No, no occurrences anywhere. 

Link to comment
Share on other sites

I figured out the problem. There were a series of little formatting errors here and there. The biggest issue was the postscripts in the Pauline epistles. My formatting had them separated from the final verses with a hard return, but Accordance interpreted that as a new verse that didn't have any verse number at the beginning. Got it all fixed. Thanks for your help!

  • 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...