The first KB article (2479426) specifically refers to sending the fonts within the job as bitmaps.
Print jobs initiated with Windows XP and Server 2003/2008 in a point and print environment may not print correctly with documents containing double-byte characters
Print jobs using point and print on Windows 7 and Vista with Server 2003 as a print server may not print correctly or may cause printer errors Microsoft has recently published two relevant KB articles.
Microsoft recommended loading the newer version of Calibri on the print server along with some complex scripts. One way of fixing this is to disable Advanced Printing Features. Normally the print servers the clients are using don’t have this newer version installed. One of the issues with Office 2010 is that it uses a newer version of the Calibri font as its default. Most noticed was the issue with Calibri Font failing to print or printing out wrong when it is not installed on their server (often Server 2003) This allows the job to process on the client, where that font resides. I, as you, have seen a number of things improve by deselecting “Advanced Printing Features” We tested at the customer and it corrected the issue. If I go into the font viewer and print the entire Calibri font from prints out fine. This only happens with Office related products and the new version of Calibri. I have a case open with MS and the only thing that has helped thus far is an idea that I came up with.replacing the Calibri version 5.62 included with Office 2010 with the version 5.0 Calibri font of Office 2007. This came from one of the Microsoft Answer Groups:
If you pull the Calibri font from Office 2007 and overwrite the Calibri font in 2010, it will correct the problem. The devices hang and the queues must be cleared and the device rebooted to correct. We did verify the version numbers in both Office 20.
It looks like Microsoft used a newer version of the font in Office 2010 that is causing the problem. (printing garbage (PCL code) or sometimes PS Error - Invalid Font: xshow) MS did release a fast publish KB article on this (KB2592142) but like you, we have not had success with installing Calibri 5.62 on our serversīTW - we have seen other models/drivers affected by this issue but the symptoms vary depending on the PDL used. Give that a try and let me know the results - the more info we can share on this the better :) The print file will be slightly larger but not nearly as large as coverting the fonts to images.
(among other things) I have not tested the PS driver but I beleive that setting the PostScript Output Option to Optimize for Portability will accomplish the same thing. The makes the print file more page independant by making font declarations every page instead of just the header.
In my case, we are using the PCL driver and was able to correct the issue by disabling the Print Optimization feature in the driver. We had numerous WC74xx producing 116-324 and 016-720 errors and we traced to this font issue. I have also been struggling with this new version of Calibri font causing printing problems.