Recently I need to put some map files to my kindle, so I don’t need to bring lots of paper.
Kindle can read jpg, yet it only support certain resolution in certain depth.
After some search and research, I found that converting the jpgs to pdf is usually a good idea.
Converting jpg to pdf is simple if you have ImageMagik, like so:
convert *.jpg foo.pdf
I frequently visit sites that show source codes of programming language, so I compare the Send to Kindle and Later on Kindle, and see how they handle <pre> in this article.
Well, I admit it’s not a full scale test, so my test is bias.
Anyway, according what I saw:
- On document selection, source field: Send to Kindle shows the host name of the site, while later on kindle shows, well “email@example.com”
- For normal <pre> tag display:
- On Send to Kindle every lines seem to be joined together, like:
- On Later on Kindle: lines are split like:
- For “tabled” <pre> tag display (last code block):
- On Send to Kindle, still every lines joined together, yet all the content is displayed:
- On Later on Kindle, lines are separated, but truncate at right margin, you can only rely on either rotate to landscape view or use smaller fonts and margins.
To sum up, Later on Kindle generally better showing the pages with source code, but not good on long lines.