This week I was looking up some long magazine articles and I thought this would really be better to read on my iPod than while sitting at the computer. There are choices on the iPod including Instapaper and Browse Later for saving web pages to the iPod, but reading articles in the browser is not one of the iPod’s strong suits. You wind up having to scroll left and right to read each line.
Instead I figured I could just get the text of the article and read a text document. But you don’t just put files on the iPod and open them like you do on a computer. I have a free eReader called Stanza on my iPod. It is pretty good, allowing you to customize the text size, color, background, etc. and it is easy to flip through pages with just a tap (as opposed to scrolling by brushing your finger on the screen).
Reading up on Stanza’s help it said that I could add eBooks to the library in iTunes by dragging them to Stanza’s file list. I wasn’t aware iTunes had such a feature, but if the iPod is connected to the computer you can click its icon. Then click the Apps tab. Then scroll down and see a list of apps that support file dragging. Stanza was there. So I clicked on Stanza and a window of files opened. I could also add files manually by using the Add button. Pretty neat. The other good thing about this is my database program supports dragging as well and now I can save a copy of my databases this way instead of by moving them wirelessly one-by-one.
Stanza supports pdf’s so I made a .pdf of my text file through Word. The result was a fixed page that I had to scroll around on and I couldn’t zoom in without the text getting jaggy. No good. So I made the text bigger and then did a .pdf, but I seemed to get the same result. It turns out .pdf’s don’t get along that well with most eReaders. So I tried a HTML file, which Stanza is supposed to support, but it wouldn’t open the file despite the HTML codes being incredibly simple.
Another thing I wanted to do was get my copy of the 9/11 Comission Report onto my iPod as it had been on my old Palm. I had never finished reading it. Stanza supports Palm formats which are .prc files. But for some reason my copy of the book was .pdb and it was also unrecognized.
Stanza’s website said that really everything needed to be in ePub format and that in order to translate you would need to download a free tool called Calibre. I started the download on that, but it was 50MB! So I took a little break.
It turns out ePub is some kind of XML format, so it is based on HTML and therefore translates best from HTML formats.
It turns out Calibre is much more than a format translator. It is really a manager for eBooks on your computer. But it can do translations. I translated my HTML magazine article and the PDB copy of the 9/11 report. Then I opened up iTunes and added those to Stanza’s document list. I had to tweak Stanza’s appearance setting for bigger text and to turn off right-justification. There seems to be a line of thought that right-justified text is easier to read but the resulting varying spaces between words are awful. It seems like most books are not right-justified but have a ragged right edge (this may not be true). Anyway, it is just a setting in Staza so I now I have things like I like.
Well, except that the quotation marks in the magazine article aren’t normal quotation marks, but curly quotes and those didn’t come over at all. Nor did the frequent em dashes used in the article or the apostrophes. So I went back and cleaned that up in the HTML by using extended character codes. There are some HTML codes that are supposed to be easier to remember than numbers that you can use for curly quotes, for instance &ldquo for “left double quote”. But XML doesn’t use those codes, so you need to use ASCII numbers. So I started using 146 for apostrophe and 147 and 148 for opening and closing double quotes. But reading further it turns out that those ASCII numbers were not adopted in HTML 4.0 (what!?) and so there are 4-digit codes you are supposed to use: 8220, 8221, and 8217 for left quotes, right quotes, and apostrophe, along with 8212 for an em dash. The good thing is it was pretty easy to do some find and replace commands and fix the whole file.
There is actually a series of about four articles, so I think it could be worth all the trouble and at least now I know how to turn long text files into something I can read on the iPod.