Sonny Software

I'm having a bit of an issue getting Bookends to scan a latex document. Here is the situation:

Bookends X 7.7.5
MacOS X 10.3.7
SubEthaEdit 2.1.1

I'm using SubEthaEdit to write and save my latex document. I'm saving it as "filename.tex". When I attempt to scan the document using Bookends, the file is greyed out in the file selection dialog box. The only way I've been able to get Bookends to recognize the file is if I copy and paste the document into TextEdit and save it as "filename.txt". I can then select and scan the file in Bookends.

I've selected SubEthaEdit as my Word Processor in the Bookends preferences but it doesn't seem to change anything. I have the funny feeling I had this problem a long time ago but I can't remember what I did to solve it. Any suggestions would be greatly appreciated.



Kindest regards,
Matthew James

Hi Matthew,

Bookends 7 doesn't recognize the .tex suffix. It looks for either a TEXT file type (metadata) or the .txt extension. Just add that to your SubEthaEdit document and I think it will scan OK (if not, please get back to me).

Bookends 8 will recognize .tex files.

Jon
Sonny Software

Hi Jon,

Thanks for the quick reply. If I save it as a .txt file in SubEthaEdit I still can't select it. Does Bookends prefer ascii text to be in a certain format?

I had SubEthaEdit set to write text files with Western (ASCII) with Unix (LF) line endings. I switched it to Western (MacOS) with Mac (CR) line endings with no luck.

I should also mention that after I copy and paste the text to TextEdit I convert it to Plain Text and then write it to a file as Western (MacOS Roman). I'm wondering if Bookends doesn't like the text file that SubEthaEdit produces?

Cheers,
Matthew

Matthew wrote:If I save it as a .txt file in SubEthaEdit I still can't select it. Does Bookends prefer ascii text to be in a certain format?

I had SubEthaEdit set to write text files with Western (ASCII) with Unix (LF) line endings. I switched it to Western (MacOS) with Mac (CR) line endings with no luck.

I should also mention that after I copy and paste the text to TextEdit I convert it to Plain Text and then write it to a file as Western (MacOS Roman). I'm wondering if Bookends doesn't like the text file that SubEthaEdit produces?

Hm, it may be that SubEhaEdit also assigns a Mac file type -- that always trumps the extension.

Ah, yes, I just checked. It assigns a Type of ****. I suggest you contact the developers and ask if there is a way to export as a plain text file with either no file type (empty) or the file type set to TEXT.

Jon
Sonny Software

Thank you for your very prompt help. I guess I'll send them a note and see what happens.

Cheers,
Matthew

Matthew wrote:Thank you for your very prompt help. I guess I'll send them a note and see what happens.

Cheers,
Matthew

I highly suggest you to try TextWrangler, is free and very powerful.