Slashdot Mirror
Office 12 to Include Native PDF Support
parry writes "Microsoft announced today at the MVP summit that Office 12, the next version of Microsoft Office, will have native support for the PDF document format. Support will be built into Word, Excel, PowerPoint, Access, Publisher, OneNote, Visio, and InfoPath." From the article: "Currently, on our OfficeOnline site, we are seeing over 30,000 searches per week for PDF support. That makes a pretty easy decision"
So we just need to go search for Open Document?
Does this mean it will have PDF-import capabilities too? Or is this just export-only? It says on the article that it can publish to PDF. Just curious...
... they could incorporate a minimalist, fast pdf viewer into Windows itself, I would happy. Ever since zip support was incorporated into XP, I've been so pleased that I've had no reason to download winzip. And the Windows "Picture and Fax" image viewer is exactly what I had wanted for a while- a fast, simple way to view images, zoom in, etc. That's what I would want for .pdf's in Windows, a simple way to quickly open, view, and print. And with Adobe's latest offerings getting bigger, more bloated, and more irritating with each new release, believe me, it can't come fast enough.
Thank God for www.oldversion.com.
http://en.wikipedia.org/wiki/Mac_OS_X
"Redmond, start your photocopiers"
The next pasture is always greener
For those who haven't seen them yet, Office 12 Screenshots: http://pdc.xbetas.com/?page=o12preview1
WOW, PDF support in Office 12, amazing how innovative microsoft is... let me just print and save this amazing article through my Native PDF print driver here on my little ole' primitive Macintosh for later use...
Isn't there such a thing hanging around as freeware already in Windows, btw?
Say what you will about Microsoft, this is one company that knows how to innovate. Innovation runs in its blood. Microsoft really innovates like nobody else. Built-in PDF support is an excellent idea. No one ever thought about doing it but Microsoft did. Sometimes we are ready for their innovation as is the case with the PDF support. And sometimes Microsoft is ahead of the times as in the case of Microsoft Bob. This is one innovative company though.
While I'm generally system-agnostic (It'll get me modded to oblivion, but IMO the best system is the one which does what you want it to do), there is one minor historical fact here.
Microsoft are not an innovative company, technology-wise. Innovation, invention, call it what you will, implies either creating something totally new or at the very least putting an original spin on something which already exists.
Where Microsoft do excel is in marketing. They have historically been masters at looking at the market and making their decisions based on where the market is going - generally by buying out or essentially copying the competition. cf. Excel vs. Lotus 1-2-3, Netscape vs. IE (granted, Netscape 4 was more than a little bloated and crufty, but I don't think the outcome would have been much different if it was sleek and efficient).
Don't get me wrong, they do have a few good products in their portfolio (I don't care whether or not YOU find shared calendars in Exchange useful, the business world does). But practically nothing that's particularly innovative.
There is a pint of beer sitting on my desk waiting for the first person who can name a reasonably successful product or technology - past or present - which Microsoft pioneered.
Foxit reminds me of OS X's Preview every time I use it. Fast, lean, and loads quickly. It may not read some of the more advanced stuff that PDFs may contain, but it's great for previewing/printing. Free as in beer. No install required, so I even carry a copy on my thumbdrive.
I always thought the PDF format was a free format (hence Apple has preview) and there's also tons of other PDF editors and printers besides Adobe. The format that is licensed to Adobe is the PS (post-script). That's why printers that support PS are so expensive because each printer with PS support sold needs to pay royalty to Adobe.
r mat
from http://en.wikipedia.org/wiki/Portable_Document_Fo
These documents can be one page or thousands of pages, very simple or extremely complex with a rich use of fonts, graphics, colour, and images. PDF is an open standard, and anyone may write applications that can read or write PDFs royalty-free.
HD Trailers
Metro? Thy production team be disbanded...
More likely PDF support will be built through Metro, as basically Metro is the XPS system in a Document.
As for the post above... Silly...
PDF will be rendered using Metro technologies is my guess, as they are not coding to the GDI but XPS. XPS is the new Windows/Document/Printer XAML format that the OS uses for virtually EVERYTHING.
Even CALLS between applications in exchanging data will pass XAML XPS information, let allow this is how the OS passes info to the Screen to Draw and the Pinter to Print.
GDI conversion layers are included for both way compatibility for Screen and Printer. i.e. your app uses XAML(WPF/XPS) to display something, but your driver only knows GDI, it will convert it.
Does everything Microsoft does have to be sinister?
How about this for a 'senerio'... For better performance and to take advantage of some of the new drawing capabilities in the WPF, chances are Adobe will even make a PDF reader for Windows that uses XAML/XPS/WPF to render the PDF information to the screen and the printer.
So does that make Adobe evil too?
These are such borderline (as a lot of people get them confused) concepts, but yet different. Metro is an extention of how elegant the new 3D Vector system built in Windows is - and also how different it is from anything Apple or anyone else has even attempted to do. Bascially when new applications for Windows are rendering cool graphics on the screen or printer, they are using XML in the from of XAML - which looks a lot like SVG, but has a 'chunk' of different abilities and purposes than SVG does.
So Metro is basically just saying, ok instead of drawing this to the screen, save it in a Document, a Metro Document - because the communication system for Graphic and any form of Media content throughout Windows is built in a simple and efficient XML format.
I though Slashdot like using concepts like XML?
native support for the PDF document format
In other words,
native support for the Portable Document Format document format
live(free) || die;
Well, Microsoft did extend their JVM with some extra ties into windows and classes that specifically made it easier to write Windows applications that were run under Java (but not write once, run anywhere). However, this was back at Java version 1.0. Microsoft totally didn't bother upgrading their JVM to support features in Java 1.2, and above. Thus, most computers were shipped with a crippled, outdated version of Java.
The problem is, that most web java apps were based on this crippled version of Java. Since that's the case, if you're a web developer you're not going to force people to upgrade your version, so you just stay with what comes standard on Windows. In this way, Microsoft prevented Sun's Java from gaining a significant foothold on Windows.
Metro is an extention of how elegant the new 3D Vector system built in Windows is - and also how different it is from anything Apple or anyone else has even attempted to do. Bascially when new applications for Windows are rendering cool graphics on the screen or printer, they are using XML in the from of XAML - which looks a lot like SVG, but has a 'chunk' of different abilities and purposes than SVG does. So Metro is basically just saying, ok instead of drawing this to the screen, save it in a Document, a Metro Document
So after you get done hyperventilating over this super-exciting "new" Microsoft innovation, why don't you read up on OS X and what it has done with PDF for the past five years? Quartz, also vector-based, is built on the PDF object graph, which is itself a subset of Postscript, and has allowed applications to save their contents to a PDF for years. It's one of the reasons OS X is so great with desktop publishing--what you see really is exactly what you'll get, down to the typography spacing, because the same graphics operations drawing the screen are also what get sent to the printer and what get saved to PDF.
"Sufferin' succotash."