Any ideas when we can get a copy of it in the UK?

@jason millward: Don’t have an exact date. US-published books generally take a month or two after the US release to show up in the UK. I blame the Tories.

To be fair I did initially learn HTML from a book all those years ago so when it’s released on amazon.co.uk I may pick up a copy.

I know what you mean. But I’ve personally learned quite a lot about the web from books by David Siegel, Lynda Weinman, Jeff Veen, Steve Krug, Eric Meyer, Joe Clark, Dan Cederholm, Jeremy Keith, Andy Budd, Curt Cloninger, etc.

Indeed… But that still means that the mini site does not work everywhere. So should we care? [etc.]

@Bertil Wennergren:

Good points, sir.

But using a handheld CSS to send the G1 phone a different style sheet wouldn’t fix the problem in desktop Chrome, and it would also deny the embedded font to other phone browsers that support @font-face but also read handheld CSS, such as Mobile Safari. Constructing a bug-driven workaround that sends one version of Webkit one CSS and another version of Webkit a different CSS may be possible, but it seems like a lot of quarters for a short dance.

I’m inclined to sit this out and let Google fix it.

It’s a file reference problem. IE requires that the “font-family” line use the font’s name, not the file name, e.g. “Franklin Medium,” not “FranklinITCPro-Med.” Because this is a custom font, it uses a custom name, and my OS doesn’t reveal that name to me, because Mac OS doesn’t support EOT. I’ve sent a note to the manufacturer and expect to hear back today. Meantime, I’m guessing at alternate names.

Please have a look in IE and see if it’s working now. You’ll know it’s working, because you’ll see Franklin Gothic instead of a default Windows sans-serif.

Thanks for helping me trouble-shoot!

As far as handhelds, the page looks fine in Blazer and Opera Mini on my not-very-modern Palm Centro. System font of course, but I would have been astonished to see anything else.

A big fail for Chrome, I agree.

Indeed… But that still means that the mini site does not work everywhere. So should we care? Don’t know… Maybe little used browsers don’t count.

Anyway: It’s possible to give the G1 Chrome a helping hand. It pays attention to stylesheets linked like this:

[link rel="stylesheet" type="text/css" href="handheld.css" media="handheld, only screen and (max-device-width: 480px)" /]

But other “handhelds” might not use such stylesheets, so it’s not a universal solution. And some handhelds that might use it probably don’t need it. So what do we do?

Maybe there’s a chapter on this in the book..

I consider my oddly jocular writing style, I wonder…

French translation of the edition was great, except maybe for the “untranslatable” writing style. We have your blog for this. Can’t comment on the Chinese and Korean ones :)
Well, I’ll have to keep on coding with my feet for the next 18 months…

I hope to make it to AEA next year, since this year didn’t work out after attending 2 years in a row. Hope to steal you for a moment and maybe get it even singed ;)

Petra, I’ll be delighted to sign your book. I hope you can come!