We find that support for printing web fonts varies quite a lot by browser and platform. If I recall correctly, it works in MSIE, Firefox/Linux and Firefox/Windows, Safari/Mac, Chrome/Linux, and Chrome/Windows. It does not work in Firefox/Mac or Chrome/Windows. There's a bug open on the last one.

Others have reported inconsistent results.

I suspect that another issue that people may be running into is web font providers who strip out the post table from fonts. Among other tools, font-optimizer does this. The chance of fonts printing correctly seems to be much lower when this table is missing. For this reason, the Google Font API preserves this table.

Thanks Raph.

>Was that functionality intended for naked font linking only (.otf & .ttf but not .woff) or a rumor wholly unfounded?

By the time the user asks the computer to print a web page that links to WOFF fonts, the WOFF fonts have already been converted and enumerated to the system as OT fonts. So this should not be a problem associated with WOFF.

I think the rumor that will not go away is that the user or web designer can make their browser window or web site, respectively, not match the page size of the user's printer quite easily.

Cheers!

@db

I think the rumor that will not go away is that the user or web designer can make their browser window or web site, respectively, not match the page size of the user's printer quite easily.

What do you mean? Don't get it.

@raph

Do you know if the testing included style sheets specifically for print?
(@media print {} in CSS or, as a link tag attribute: media="print").

Also,
+1 on the post table problem. A known issue. Don't mess with the post table - it's asking for trouble.

rich