Following up on the news that Office 12 will directly output documents in PDF format, Mary Jo Foley writes:
[Office program manager Brian] Jones’ disclosure was somewhat surprising, given Microsoft’s announcement earlier this year of plans to incorporate “Metro,” Microsoft’s PDF/PostScript alternative, into Windows Vista. (Microsoft currently is using the XML Paper Specification (XPS) to refer to many of its Metro components.)
And Microsoft’s Metro announcement was seen by industry watchers just one of a growing number of direct shots by Microsoft at Adobe’s PDF/PhotoShop/Illustrator empire.
This is probably going to be the single biggest misconception you read this week. Only trouble is, it’s based on a fundamental misunderstanding. As I posted last April from the Windows Hardware Engineering Conference:
I also got a chance to look more closely at the “Metro” technology. It looks like there will still be room in the world for PDF files. The real impact is to replace the old Enhanced Metafile (EMF) format with a new, smarter native format for printed output. There’s a big overlap with PDF files, but it’s not as direct a competitor as early reports, including mine, might suggest.
Microsoft did a poor job when they initially talked about the Metro technology, leading lots of people to speculate that it was a PDF-killer. A closer look reveals it’s no such thing, but the original flawed description has already spread far and wide.
Update: Read more technical details on the XML Paper Specification (XPS) here. XPS is first and foremost a container specification for application data. It’s true that the XPS Document format is very PDF-like, but I don’t think anyone has any illusions that it will replace PDFs. If you use Office 12, it probably will allow you to edit XPS Documents in the same way that Acrobat (the full product) allows you to edit PDF files, without having to leave Office or buy a separate program.