Where do YOU store the code that goes with technical books?

[technomom]

I have to think this topic has come up before, but I searched in this topic (which seemed the logical place) and couldn't find anything about it, so I'm asking. Please forgive me and just redirect me if it has already been discussed ad nauseum. My normal searching skills just don't seem to work so very well here.

Many technical books come with samples of the code being discussed. If you buy the physical book, you get the code on a physical disk. In our household, that has always resulted in me getting the book off the shelf, finding the little plastic pouch where the disk should be empty, then asking my husband and daughter what they did with it. The ensuing goose hunt often ends up finding a scratched and useless disk somewhere hours later (out comes the toothpaste!), or never finding the disk at all.

So - happiness! eBooks come, instead, with a the code included as an accompanying download, right? And since I store my eBooks in Calibre, and I don't lose my eBooks, I'm not going to lose the code either.

But - Calibre stores the eBook. Where am I going to put the code to have it with the book, never separated?

Can I place the code archive in the book's Calibre folder without causing some terrible error? I normally keep my fingers OUT of Calibre's file structure completely, fearing disaster!

Advice? Tested solutions? Pretty please?

Thank you!
Cyn

[Starson17]

Originally Posted by technomom

Can I place the code archive in the book's Calibre folder without causing some terrible error?

Yes - you can do this outside Calibre, although a library check will warn you about the files.

Calibre will also let you add any file format/file extension you want and will track, but ignore it (if it's not a recognized ebook format). Put your code into a zip file having the extension .zip.code and Calibre will see it as a .code file and ignore it, but list it as a stored format of type CODE.

[itimpi]

I tend to use a RAR file instead of a ZIP file as that does not conflict with Calibre's use of ZIP files for HTML documents.

I have also used .iso files where the relevant files come on a CD by just making an image of the CD and storing that in Calibre. If I later need to us the .iso file I can use a utility such as Daemon Tools to allow me to mount the image and get at the contained files.

[technomom]

I was considering using an .ISO file. I think Calibre can also handle .RAR files for HTML documents, although that isn't its default.

I appreciate both answers!

[theducks]

Are we talking code: as in Text source LISTING?
Why not add an Appendix or 2 or 3...
to your book?

[Starson17]

Originally Posted by technomom

I was considering using an .ISO file.

That will work fine. Just drag the ISO into calibre and merge the new record, or drag it into the edit metadata screen for the book.

I think Calibre can also handle .RAR files for HTML documents, although that isn't its default.

Calibre will open zip and rar compressed files when you add them. If it finds a single ebook format it recognizes inside, it will add that book as though it was not provided in compressed form. HTML will be put inside a zip. If you go behind the scenes, into the library record where there is an existing rar or zip, and replace the contents of the compressed file with any other single format inside the rar or zip, then try to view it, Calibre also seems to gracefully handle it, although it's not recommended.

In your case, I'd just stick with the ISO format.

[technomom]

That's a good idea when they are just text source listings. Sometimes they aren't. That's a very good idea, though, for the eBooks I can edit. I don't know how to deal with appendices in Calibre otherwise.

[Starson17]

Originally Posted by technomom

That's a good idea when they are just text source listings. Sometimes they aren't. That's a very good idea, though, for the eBooks I can edit. I don't know how to deal with appendices in Calibre otherwise.

Code listings in text form may/will suffer if you convert them. You may want to convert the book, but not the code.

[technomom]

Thank you, Starson17. I certainly don't want to mess up the code and make it useless.

[theducks]

Originally Posted by Starson17

Code listings in text form may/will suffer if you convert them. You may want to convert the book, but not the code.

Would wrapping the code in a <pre> tag stop the mangle?

[Starson17]

Originally Posted by theducks

Would wrapping the code in a <pre> tag stop the mangle?

It should. (You wouldn't have asked, I suspect, if you didn't already know that ). I haven't done it enough to know for sure if there are any cases where it might fail. I know, however, if I had code attachments, I'd prefer they never went through any conversion stage at all. I'd probably keep the .iso format for use, and add the <pre> tags if I also wanted to be able to browse the code on a handheld.