I'm trying to import a more complete journal abbreviation list into Bookends, but am having some problems. Because Bookends has the fields switched around, I have to use a spreadsheet to do the switching before importing into Bookends.
The problem is that Excel adds stupid quotes allover the place, even though I am exporting tab delimited only. Upon changing the file type to BEPG with Quickchange, Bookends reads the file fine.
Both Google Docs and OpenOffice export the tab delimited .csv (or .txt) files correctly. They can be opened in textedit and look correct, but after changing them to BEPG files, Bookends will simply not read the files. (Editing the Journal Glossary pulls up a blank list.)
Any ideas? I know this is probably not a Bookends problem, but a nudge in the right direction would be helpful.
Help with Journal Glossary import
Re: Help with Journal Glossary import
The glossary file text must be encoded as UTF-8 or there may be problems.
Jon
Sonny Software
Jon
Sonny Software
Re: Help with Journal Glossary import
Hrmm, pretty sure UTF-8 was selected in OpenOffice. I'll check tomorrow.
Re: Help with Journal Glossary import
Yeah, UTF-8 is selected. Not sure what is going on. Another option would be to use Excel, but find a way to remove the quotes.
Re: Help with Journal Glossary import
Post here what a line looks like in your text file (indicate where tabs and return characters are). And note that the returns should be ASCII 13, not ASCII 10.
Jon
Sonny Software
Jon
Sonny Software
Re: Help with Journal Glossary import
Ok, I figured out a way around Excel's stupidity (with the quotes thing). After rearranging the columns in Excel, I just copied and pasted into a plain text document. No quotes! 
Seems like it's working now.
As to what OpenOffice is doing, I just don't know. The file looks fine in textedit. I could tell you what it LOOKS like. Looks like tab text tab text. Then a new line. But who knows what's really there?

Seems like it's working now.
As to what OpenOffice is doing, I just don't know. The file looks fine in textedit. I could tell you what it LOOKS like. Looks like tab text tab text. Then a new line. But who knows what's really there?
Re: Help with Journal Glossary import
The new line character has to be ASCII 13 -- ASCII 10 displays the same way, but Bookends doesn't expect it.
Jon
Sonny Software
Jon
Sonny Software
Re: Help with Journal Glossary import
Ok, good to know. Thanks for your help.