I saved a document as a text file and the passage list doesn't seem to be picking up any verses. I know it has worked with at least an html file in the past. anyone have any ideas or insights?
I just tested it and it worked for me, both a simple list of verses and verses interspersed with text...
How big is the text file? I've only worked with tiny ones in relationship to Verse Lists so far. If the content isn't sensitive, could you upload it to the forum for others to test on their installations?
I've go the same problem here. I can't upload most .txt files successfully. I can only upload very small files it seems.
I'm confused; are you talking about uploading files to the forum, or adding text files to a Passage List?
What kind of document is it? If you open that text file that you saved in Notepad, is any of it human-readable? (For example, just saving a Word 2007 docx file with a ".txt" extension doesn't automatically make the file readable by Logos 4; you would also have to make sure it was saved in the plain text format.)
I just added some passages to a passage list via a notepad document (*.txt) and it worked perfectly. I'm using 4.0c RC-1
Sorry, I'm talking about adding files to a Passage list. Attached is a .txt file (created from Word) that doesn't add.
2063.Sermon.txt
(Also, when a file fails to add, Logos doesn't release the file for writing afterwards.)
Aah. I think I see the problem. The first file had curly quotes. When I search/replaced the curly quotes, Logos accepted the file.
This sounds like it could be indicative of an encoding problem, but I was able to successfully add 13 passages from that file whether it was saved in UTF-8, UTF-16, Windows-1252, ISO-8859-1, etc. We'll continue to investigate.
That's weird. But I think I've worked out the problem. It's not to do with encoding, at all. Instead, I think Logos requests exclusive access, and baulks when it doesn't get it. Here's how to re-create:
Instead, I think Logos requests exclusive access, and baulks when it doesn't get it.
Thanks for determining the underlying issue; this bug will be fixed in the next release (you will be able to import passages without closing Word).
I created a txt file in NoteTab Pro which is a plain text editor. The contents are below. When I insert this into a passage list only the 3rd reference (Gal 5.22) comes through. Looking at the list here I notice that is the only one using a colon to separate the chapter:verse -- the others are using a period. This ought to be made more robust. When I type references in the passage list using periods they are accepted fine.
[edit] I did a search-replace in NoteTab, changing the periods to colons and saved to a new file name. The passage list still only brings in Gal 5.22. Made a new file in notepad and the same results.
1 jn 3.91 jn 5.18Gal 5:221 peter 1.31 peter 1.23jn 3.3-5 jas 1.18jn 1.13
I created a txt file in NoteTab Pro which is a plain text editor. The contents are below. When I insert this into a passage list only the 3rd reference (Gal 5.22) comes through. Looking at the list here I notice that is the only one using a colon to separate the chapter:verse -- the others are using a period. This ought to be made more robust. When I type references in the passage list using periods they are accepted fine. [edit] I did a search-replace in NoteTab, changing the periods to colons and saved to a new file name. The passage list still only brings in Gal 5.22.
[edit] I did a search-replace in NoteTab, changing the periods to colons and saved to a new file name. The passage list still only brings in Gal 5.22.
Ken ~ The reason that Gal 5:22 is coming over and the others are not is due to capitalization, not the colon/period. It is case sensitive, just as the Logos rich text editor is currently, requiring the book name to be capitalized for auto-detection. We are looking into changing this for the rich text editor. I will submit a request for Passage List text file import, too.
currently, requiring the book name to be capitalized for auto-detection
That is good to know. Thanks. And thanks for submitting this request. I guess I'm lazy with the shift key. It's a good thing NoteTab has a function to convert text to caps -- using that makes my file import fine.
currently, requiring the book name to be capitalized for auto-detection That is good to know. Thanks. And thanks for submitting this request. I guess I'm lazy with the shift key. It's a good thing NoteTab has a function to convert text to caps -- using that makes my file import fine.
To follow up on this thread, and the request I submitted, it is designed this way (case sensitive) to prevent getting too many false positives.
it is designed this way (case sensitive) to prevent getting too many false positives.
I'd like the option to turn that off.
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
