So, my mother has a shiny new Amazon Kindle, and before they continued on the next leg of their vacation, I helped fill it up with free e-books from Mobipocket’s web site. I also played with it for a while.

Notes:

1. Every time I picked it up, I hit a button by accident.
2. There's no reliable way to void a pending button-press, and it keeps a queue at least five clicks deep.
3. The "like a book" way of holding it with the cover makes the "previous page" button awkward to use.
4. Western European/American font support only. I didn't really expect it to have kanji, but I was surprised that it was also missing things like "ō", affecting things like the English-language Wikipedia entry for Toshirō Mifune.
5. Web sites that can't be rendered are falsely reported as down. I was all set to rush into the co-lo to reboot dotclue.org when I checked from my laptop and discovered that it was fine. The Kindle just refused to render it, because of the Japanese text.
6. It always took a long time to connect to Whispernet, leaving me wondering if our hotel was in a cellular dead zone. No, it's just that slow.
7. Frequent ghosting on the display, something that's less of a problem with newer e-paper displays and ones that do a full erase before a full redraw.
8. Unlike the early photos they showed off of it, it's not hideous to look at. It definitely needs some work in the human-factors department, but it looks much cleaner than I expected.
9. The sidebar-slider UI is a reasonable compromise between clarity and responsiveness, but takes some getting used to.

Net result: I’ll hold off until Kindle 2.0, at least.

I like Google Earth. I even pay for the faster performance and enhanced features. A few things, though:

• Why can't I keep North at the top of the screen? I hate constantly double-clicking the "N" in the gaudy navigation scroll-wheel.
• Why do you auto-enable new layers in my view, so that, for instance, I suddenly see every golf course on the planet, even though I had that entire category disabled?
• Why can't I switch between different sets of enabled layers?
• Why is the "Google Earth Community" layer such a dumping ground of unsorted crap? For instance, what value does this have to anyone who's not an airline pilot? Or this, where points scattered around the globe are all labeled, "here's my collection of 4,728 placemarks".

I’m sure I can come up with more if I think about it for a bit…

[update: ah, press ‘n’ for north, ‘r’ for a total view reset, and then figure out how to fix all of the KMZ files that were broken by the upgrade]

[Update: Thanks, guys; the check is in the mail. More new-camera-porn here.]

Now that you’re releasing a 24+ megapixel full-frame 35mm CMOS sensor, don’t you feel a little stupid for making some of your high-end Zeiss lenses for the Alpha line APS-C-only? I doubt you’ve actually sold many of them, given the price and scarce distribution, but still, you had to know that full-frame was a requirement for a serious player in the DSLR market, and your recent announcements show that you’re not just keeping the low end of the old Minolta lineup.

Just to be clear on this: if you put that sensor into a body that’s the equivalent of Minolta’s 7 or 9 series (pleasepleaseplease a 9!), you’ve got a customer here already waiting in line.

For the past few weeks, my mother has been calling to say, “we sent you a monkey for Christmas, has it arrived yet?”. Each time, she seemed disappointed that I didn’t have my monkey.

Last night, it arrived. The Powertraveller Powermonkey-explorer universal charger. It’s an external battery for extending the charge on your gadgets, and it comes with a bunch of adapter tips for different phones and toys, a charger with a set of international plugs, and a small solar panel for charging off-grid.

The only additional adapter tip I’ll need to buy is for the DS-lite, which isn’t quite a standard mini-USB. Can’t have my kanji practice tool dying on me!

Now available from Amazon.

So I bought the second-generation Sony Reader. Thinner, faster, crisper screen, cleaned-up UI, USB2 mass storage for easy import, and some other improvements over the previous one. It still has serious limitations, and in a year or two it will be outclassed at half the price, but I actually have a real use for a book-sized e-ink reader right now: I’m finally going to Japan, and we’ll be playing tourist.

My plan is to dump any and all interesting information onto the Reader, and not have to keep track of travel books, maps, etc. It has native support for TXT, PDF, PNG, and JPG, and there are free tools for converting and resizing many other formats.

Letter and A4-sized PDFs are generally hard to read, but I have lots of experience creating my own custom-sized stuff with PDF::API2::Lite, so that’s no trouble at all. The PDF viewer has no zoom, but the picture viewer does, so I’ll be dusting off my GhostScript-based pdf2png script for maps and other one-page documents that need to be zoomed.

I’ll write up a detailed review soon, but so far there’s only one real annoyance: very limited kanji support. None at all in the book menus, which didn’t surprise me, and silent failure in the PDF viewer, which did. Basically, any embedded font in a PDF file is limited to 512 characters; if it has more, characters in that font simply won’t appear in the document at all.

The English Wikipedia and similar sites tend to work fine, because a single document will only have a few words in Japanese. That’s fine for the trip, but now that I’ve got the thing, I want to put some reference material on it. I have a script that pulls data from EDICT and KANJIDIC and generates a PDF kanji dictionary with useful vocabulary, but I can’t use it on the Reader.

…unless I embed multiple copies of the same font, and keep track of how many characters I’ve used from each one. This turns out to be trivial with PDF::API2::Lite, but it does significantly increase the size of the output file, and I can’t clean it up in Acrobat Distiller, because that application correctly collapses the duplicates down to one embedded font.

I haven’t checked to see if the native Librie format handles font-embedding properly. I’ll have to install the free Windows software at some point and give it a try.

[Update: I couldn’t persuade Distiller to leave the multiple copies of the font alone, because OpenType CID fonts apparently embed a unique ID in several places. FontForge was perfectly happy to convert it to a non-CID TrueType font, and then I only had to rename one string to create distinct fonts for embedding. My test PDF works fine on the Reader now.]

Our product is no longer a secret. Most of the tech blogs and news sites have something up today, although the quality of information varies. I won’t be commenting on it here much.

Sony’s first Minolta-compatible SLR was the A100, which was a rebadged and slightly improved Minolta 5D. They’ve now shown off prototypes equivalent to the old 7-series and 9-series bodies, which is good news for people like me with a significant investment in Minolta glass.