
Microsoft takes on PDF 983
bhhenry writes "Linux Format reports on a new Microsoft PDF-killer technology to be included in Office 11, called XDocs. From the article: "Adobe's stock took an immediate hit, and some analysts went so far as to compare Adobe to erstwhile MS competitor Netscape.""
OpenOffice/StarOffice (Score:4, Interesting)
Re:OpenOffice/StarOffice (Score:5, Informative)
Under UNIX based systems where spadmin, the printer administration program, uses ghostscript, ps2pdf, etc. We're working on a new 'create PDF' feature on all the platforms we support, you can find it in the 'developer' builds today.
The full document is Here [openoffice.org]
Re:Nah - Is there PDF licensing? (Score:4, Interesting)
And, after diggout out the 500-page PDF1.3 spec (some interesting reading -- PDF is a cool format.), (Pages 15 and 16, too, by the way.) yes, indeed, you can pretty much implement it in anything you want to read or write PDF's, as long as you include an appropriate Adobe-indicating copyright notice.
So, MS could implement PDF if it really wanted to.
Although, now, in the crazy days of XML, and as PDF is sort of, well, old, maybe xDocs is something better.
Mind you, if it's not free and open, nobody will use it.
Monopoly Abuse? (Score:5, Insightful)
Re:Monopoly Abuse? (Score:4, Insightful)
Re:Monopoly Abuse? (Score:3, Insightful)
What are you talking about? The USSR invaded countries that tried to implement a political system that it didn't like. Why, it would defend any Middle Eastern country that would ally with it, regardless of the brutality of it's government. And don't forget that they invaded Afghanistan!!!
Um. Never mind.
(To be fair, by most reports Stalin killed 10 million of his own people. He made a secret pact with Hitler to split Poland, and was a real bad guy. I hate George W. as much as the next expat, but let's not get carried away.)
Re:Monopoly Abuse? (Score:4, Insightful)
I hope you're not serious. Can you please explain to us how having two products that do basically the same thing competing for market share is a bad thing?
Before you start worrying too much about how having a competetor to PDF will kill the economy, think about what will actually happen: 1) Consumers will save money because competition will drive the price of the technology down, and 2) those consumers will have a little extra cash in their pockets that they can use to purchase other goods or buy stock, or just save for a rainy day.
I'm sorry, but I don't think Adobe is the cornerstone of the US economy. If their market for electronic documents (aka PDF) shrinks, then they may have to cut a few jobs or sit down and figure out how to make their product more competetive. Meanwhile, the rest of us are saving money and getting a better product.
BTW, have you looked at the price that Adobe charges for Acrobat (not the reader, which is free)? If you want to use PDF you are paying more for it than the copy of Windowz you're running it on.
Re:Monopoly Abuse? (Score:5, Insightful)
The danger (as always with things Micro$oft) is that they will embrace, extend, and then exterminate. Witness the web, which is now 99% geared towards IE (which has YET to implement W3C standards).
Re:Monopoly Abuse? (Score:5, Informative)
1. which is now 99% geared towards IE
That is false. 99% of the web does not require IE. Very few sites actually require IE. Mostly clueless idiots.
Some recent surveys [com.com] on browsers indicate that IE is used by about 96% of users. That's not 99, but I think it's sufficiently large that any web site developer will insure first that their pages look good in IE, then maybe Netscape, if they have time. The W3 standards are all fine and good, but the de facto standard is defined by how IE behaves. MS owns that behavior and can change it at will.
2. Um... please explain how something that's free can get any cheaper.
Adobe charges money for its PDF creation products. They are not free. MS is competing with them. Therefore, Adobe's products will get cheaper or Adobe will lose the market. Imagine that.
I think distribution of a PDF competitor as part of a default distribution of Windows or Office would kill off Adobe's version of PDF in much the same manner that bundling of IE with Windows killed off Netscape, despite the latter being reduced to zero price. It was more hassle for people to download some large binary from Netscape over their modems and to try to disentangle IE's tentacles, that most people just caved in and accepted IE as their browser. It's been demonstrated that zero price is not enough to compete with Microsoft.
MS will embrace Adobe's PDF idea, extend it using XDocs, and then let Adobe's PDF wither as Office defaults to output XDoc instead of PDF. And wither it will, because Office, too, is used by about 90% of the office productivity suite marketplace.
When a desperate Adobe offers an Office plug-in for free download that enables one to write PDF, they'll get the same rousing response as Netscape did for free downloads of its application.
I don't want to belabor these points because how MS operates is well-known by now.
That said, however, the basic technical ideas of both PDF and of XDoc are good.
Publishing their respective specifications and letting an international standards body ratify those standards is a great idea. I would move to XDoc from PDF if it were technically-sound, completely and openly published, and ratified by an international standards organization.
Companies, either Adobe or Microsoft, trying to own a standard and use it to wring the most dollars out of it, simply by tripping up the competition with a deft change of the standard is not a good idea.
Just one thing (Score:5, Interesting)
Since when does Office output PDF files by default? Office only will output PDF files if you spend several hundred dollars on Acrobat. When you print to PDF, you either click a little icon or click File->print PDF. There is absolutely no way MS could stop or influence that. Unless when people try to print PDF files MS hijacks the Adobe buttons and makes them print Xdocs instead. That would have them in a losing court battle with Abode instantly as what MS would have done is break Acrobat on purpose. Adobe actually has the money to defend itself.
The other thing is for this to take off everyone needs to be running Office 11 which isn't going to happen for quite some time. There are a ton of Office 97/2000/XP installs out there. So really just like Acrobat most people would have to download some sort of addon program to read Xdocs correctly since they won't have Office11. Also most people won't even have the ability to make Xdocs.
So although I wouldn't bet against MS, I'm not so sure PDF is going to be dying anytime soon.
Re:Monopoly Abuse? (Score:5, Insightful)
Re:Monopoly Abuse? (Score:5, Insightful)
1) Consumers will save money:
Bzzt. PDF Viewer is free. Additionally, the format for PDF is published so that people can write both viewers and creators for free.
2) Consumers will have extra money:
Bzzt. Again wrong. You have PDF which is still free versus a feature that will be included in the latest version of Office, which isn't free. Additionally, XDocs competes with the Forms feature in PDF, not with PDF in general.
So, have you looked at the price MS charges for Office? Oh yeah, in addition you'll need to be running Win 2K SP3 or XP in order to run this version of Office.
Now on to your straw man. The poster wasn't saying that the fall of PDF was going to destroy the economy. He was stating that the settlement handed to MS will give them carte blanche to wage full scale war against any and all "competitors" in the computer industry.
THAT could lead to further damage to the economy as we see how MS prices things once they get control of the market segment.
Re:Monopoly Abuse? (Score:5, Insightful)
I'll give some examples of how competition can be either good or bad for consumers.
Good for consumers:
(depending on your point of view)
Bad for consumers:
(depending on your point of view, whether or not you have a monopoly on a related technology)
The Microsoft shills can say all they want about how the second set of examples are so good for everyone. Now it is possible that XDoc is just another name for PDF, and Microsoft intends the type of competition illustrated by my first set of examples.
Guessing which type of competition Microsoft intends is an exercise left for the reader. (Hint: you are allowed to examine Microsoft's past behavior to aid you in forming a conclusion. Be sure to explain your reasoning.)
(Extra credit: be the first to point out that I've managed to use "competition" and "Microsoft" in the same sentence!)
Re:Monopoly Abuse? (Score:4, Insightful)
Sure, glad I could help
Past performance is the best indicator of how something will perform in the future
Look at MicroSofts track record.
Yes, competiton is good, But when a Monopoly uses it's power to further maintain it as being a monopoly, that is not considered being "competivie" and good for the consumer.
While I will admit that as times change, all monopolies lose that strangehold power (who want's to be railbarron?). In the meantime, with price fixing, genuine invovation being destroyed before it is brought to the market, and new "features" being added, not because they are a benefit to the user, but because they further the interest of the monoploy.
Case in point, when the new version of office comes out, it will only run on Y2k with SP3 or on XP. All news systems will have to be loaded with XP, and the new version office will be the only version available.
At this point, business will end up with a mix of "new office' and "old office", which will not be compatible. They will be forced to upgrade, because it is good for MicroSoft.
If MicroSoft was not a monopoly, abusing it's power, there would be real free market competion, and the consumer could, at cost, swith to different word processor that does not lock them in like that. However, lets face it, as all the MS zelots out there constantly remind us, neither WordPerfect or OpenOffice are viable alternatives for most business that are entrenched MS Office users.
Competition is good (and possible), when you are not competing against a monopoly.
Bart Bucks are not legal tender
PDF Files arn't easily modifiable. (Score:4, Insightful)
Re:PDF Files arn't easily modifiable. (Score:3, Funny)
Re:PDF Files arn't easily modifiable. (Score:3)
What is wrong with a plain old PS, you can even embed EPS files into PS files. Has always worked, will always work. I use Framemaker + xfig + matlab for my documents, and this far, I've never had any problems. As for PS portability, that's what ps2pdf is for
Re:PDF Files arn't easily modifiable. (Score:4, Insightful)
Let me just see if I understand Slashdot's position on all of this:
So my question to the Slashbots is, will you criticize everything Microsoft does - even if it's something you wanted them to do - just because it's Microsoft? Or is there a serious technical reason that this product is inferior?
Because, y'know, the best product should always get the support of the market. That's why Excel is so popular.
Re:PDF Files arn't easily modifiable. (Score:5, Insightful)
PDF isn't a very good format either because Adobe controls the spec. It isn't open.
Looking at Microsoft's XDocs FAQ since I can't get to the article, it appears to be geared primarily towards creating forms so it's not obvious how it competes directly. I never liked PDF forms and they seems to be used rarely.
The evilness of XDocs depends on whether you will be able to easily use them without Office. PDF has wide support on many platforms.
-Kevin
Re:PDF Files arn't easily modifiable. (Score:5, Interesting)
It wasn't always fully open... I've followed xpdf for many years. In the early days, Derek could not show encrypted PDF files because Adobe would not release specs on the encryption . Long ago, xpdf printed a message with contact info for someone at Adobe, saying "contact them and tell them to make good on their claim that PDF is an open format" (or something like that... it's been years). Apparantly there was quite a bit of tension between Adobe and Derek, and people from Adobe claimed (lied) that xpdf could not show those files because Derek was a bad programmer. Finally, Adobe relented and released full specs including the encryption. This probably never would have occured if it weren't for Derek Noonburg and his xpdf program (and Adobe's initial refusal to release a linux version of acrobat reader).
Re:PDF Files arn't easily modifiable. (Score:5, Insightful)
But why is Excel the best? Is it because they just made a better product and everybody else gave up because they couldn't innovate? Or is it because Microsoft crushed the opposition by exploiting their monopoly?
I think you'll find that Microsoft ensured that the "best product" never got made, because they knew it wouldn't be theirs.
Re:PDF Files arn't easily modifiable. (Score:4, Informative)
Nope. They have good devs just as other firms. the "best product" wouldn't be made because MS will not be able to charge for an upgrade later.
This is not an MS-specific tactic, many SW firms use it, but MS has used it most successfully, so far.
problem with this kind of tactic is that eventually it WILL backfire.
Re:PDF Files arn't easily modifiable. (Score:5, Insightful)
Two. XML is good, because it's a format that parsers have been written for, so developers don't have to write yet another file format parser, but merely write some additional logic ontop of an existing XML parser.
Three. Microsoft using XML isn't bad. However, given the history of their actions with regards to standards, and common sense, it is highly probable they'll find some way to subvert XML into some bizarre format that only MS Office can handle. This is what some of us at Slashdot feel will happen. XML isn't bad, but Microsoft doesn't have a track record for following standards. They do however, have the high score for subverting them.
Re:PDF Files arn't easily modifiable. (Score:5, Funny)
Re:PDF Files arn't easily modifiable. (Score:5, Informative)
| * OpenOffice uses XML, and that's good.
| * Now Microsoft want to use XML too... but |that's also bad
Big difference:
Microsoft's DTD (Document Type Definitions) are proprietary, which makes use of the open framework XML just as proprietary.
Microsoft's use of XML *is* bad indeed.
Re:PDF Files arn't easily modifiable. (Score:5, Insightful)
[..]
Now Microsoft want to use XML too... but that's also bad
It's simple. The people who post to Slashdot generally don't trust Microsoft. And they've good reason not to. Even when they say they are using a particular format, they deliberately do stuff to make it incompatible with anything that isn't from Microsoft.
Try this simple test. Open a document in Microsoft Word 2000. Save as HTML. Look at the HTML. You will find yourself looking at something that is unlike any other HTML you'll ever come across.
So when Microsoft say that XDocs is in XML format, it doesn't really mean it will be in XML format, just something they themselves call XML format.
Microsoft hasn't done anything recently that has convinced me that I can trust what they say. So I don't. The mistrust runs so deep that I, and I expect may other people who post on Slashdot, will be absolutely amazed if we open an XDoc and see something like this: rather than (and this is a small extract from a very simple document in Word 2000 saved as "html"):
Re:PDF Files arn't easily modifiable. (Score:5, Funny)
Shop Owner: We sell forbidden objects from places men fear to tread. We also sell frozen yogurt, which I call "Frogurt"!
Homer tells the owner that he is looking for a present for his son's birthday. The owner hands him a talking Krusty doll.
Shop Owner: Take this object, but beware it carries a terrible curse!
Homer: [worried] Ooooh, that's bad.
Shop Owner: But it comes with a free Frogurt!
Homer: [relieved] That's good.
Shop Owner: The Frogurt is also cursed.
Homer: [worried] That's bad.
Shop Owner: But you get your choice of topping!
Homer: [relieved] That's good.
Shop Owner: The toppings contains Potassium Benzoate.
Homer: [stares]
Shop Owner: That's bad.
Homer: Can I go now?
Re:PDF Files arn't easily modifiable. (Score:5, Insightful)
You can open them and edit them in Acrobat.
You can open them and edit them in Illustrator.
You can open them and edit them in Ghostscript (including stripping the "protection" that is meant to stop you from printing, copying and editing locked PDFs)
PDF isnt going to be replaced, unless MS releases a distiller like app for free, and makes it available to all applications in windows as a virtual printer.
If they then release a free and full featured reader to go with this imitation distiller, then you MIGHT eventually have an "Acrobat Killer".
Anything that stops the widespread creation of files in the new format will kill this idea. Just ask the people who used to make Replica (which came out almost at the same time as adobe released PDF); it only allowed you to create 5 "Replica files" before you had to buy the software. If they had allowed you to produce as many Replica files as you wanted, the number of files in that format would have exploded, and Replica would have become a contender. Instead, it dissapeard off of the face of the earth.
Re:PDF Files arn't easily modifiable. (Score:5, Insightful)
XDocs are based around the XML specification. Hence, wouldn't they be easily modifiable?
XML is just a format.
Word .docs are based around long strings of bytes. They are easily modifiable. But modifying them in a way that makes sense is much harder. Similarly, knowing the file is in XML format doesn't mean you know what goes where.
Just that some given programming language has source code in ASCII doesn't mean you immediately know how to use it either.
Of course, they could make their XML files self-documenting, with good names for tags, and some freedom in where they are placed. Or they could use obfuscated names, use many arcane little rules for their structure, or even encrypt stuff in it. It all depends on the DTD, which isn't open. I wouldn't trust them to suddenly put work into making a format that's maximally open for everybody, would you?
Netscape? (Score:5, Insightful)
Curious. I don't recall Netscape having the market leading graphics suite for professionals, nor a well-regarded video authoring suite, nor a revenue stream from the licensing of Postscript rendering engines in printers.
Oh well. Analysts said it. I must be wrong.
Cheers,
Ian
Re:Netscape? (Score:3, Insightful)
Re:Netscape? (Score:3, Funny)
Re:Netscape? (Score:3, Interesting)
An that evil as hell HTML help, MSDN has never been the same.
Two of the greatest reasons for uninstalling IE.
Why are you running a GUI on a server anyhows? There servers arn't they?
Ok, so microsoft trides to do this now (Score:5, Insightful)
With browsers 6 years ago there was very little loyalty, so MSIE could move in before everyone realized just how powerful MS was going to be over Netscape and the other companies involved in browsers.
But with Adobe Acrobat we're talking about a refined and popular format. Actually, Acrobat is one of the best file ideas out there, IMHO. It is perfectly cross platform, well designed, and (neglecting to note the whole russian programmer fiasco) Adobe has a good business model behind it.
MS's only strong point could be integration, like they offer with all of their other 'solutions', but Adobe already has great integration wih their own suite of programs and even with Microsoft Word.
They should call it Bob...
I'm not buying into this... (Score:5, Interesting)
Also there have been very FEW viruses that infect PDF's, imagine the viruses that will be written for M$'s version.
Re:Ok, so microsoft trides to do this now (Score:3, Interesting)
Bah! I have some issues with PDFs.
A gzipped postscript file is always smaller than a PDF. Add bzip2 compression, and it's even smaller.
Neither PS or PDF can be modified significantly or easilly. Even with Acrobat, you can change some text, but you can't move anything around.
Similar to the previous, you can't easilly parse and modify it, non-interactively. If I want to change something in all my HTML files, I have no problem. To do it in PDF is a nightmare.
What I think we need is an HTML archive. That way, you can distribute a single file that contains one or more HTML files, along with all the images, CSS, et al. It could simply be a zip or tar file. And, of course, browers and editors need to understand how to fully utilize that archive. Right now, if you delete an image from a page, it doesn't remove the image file; that would need to change.
The only thing HTML needs to match PDF is a page-break character, so you can closely control the page layout (if you want to), and someone else could easilly change that layout you wanted, for their own needs/preferences.
That would be easy to modify interactively, easy to script/automate changes. Easy to create, easy to distribute, print, etc. Everything that PDF is, and everything that it isn't.
You clearly haven't done print. (Score:5, Informative)
However, saying all HTML needs to match PDF is page breaks is like saying all a Pinto needs to take on a Porsche is not to explode.
PDFs are entirely editable in many applications. They can include font data. They include everything needed to output cleanly on a variety of output devices. They are made to look the same on screen as they will on output devices. They solve many of the main problems with delivering files to press.
HTML is markup. PDF is page description. There is an enormous difference.
-j
Umm... (Score:5, Informative)
PDF is to XML, as Acrobat is to XDocs (Score:5, Insightful)
XDocs is only Microsoft's front-end application for modifying XML (which the original slashdot post never mentioned). XDoc [microsoft.com] is positioned as a Word-like way of manipulating XML form data (Screenshot [microsoft.com]).
If anything, XML will be the PDF-killer. Adobe trapped themselves into a corner when they devoted themselves to a proprietary file format instead of using XML. With everyone jumping on the XML bandwagon, no wonder Adobe's stockholders are getting nervous.
Re:PDF is to XML, as Acrobat is to XDocs (Score:4, Insightful)
The only fundamental difference is:
binary format (Acrobat) versus ASCII/Unicode (XML) i.e. 'human readable'.
First, proprietary not human readable. Proprietary means an undisclosed file format.
XML without a published DTD or Schema (published both the scheme and how to interpret it) is just as proprietary as any other undisclosed file format. At best, it might be easier to reverse engineer (which is forbidden in the US).
AFAIK, Acrobat is an open format (yes, even binary formats can be open, gasp). Whether XDoc(s) shall be open remains to be seen.
This irritating misuse of proprietary and concept of 'not binary == good' misleads to many mistakes and creates false understanding.
Re:Umm... (Score:4, Funny)
Yes, but... (Score:3, Insightful)
...surely the issue is not whether or not it's Microsoft, but whether or not the technology actually works.
IMHO, postscript/PDF is one of the most ingenious formats around. It is extremely portable, handles fonts, vector graphics and (perhaps to a lesser extent) bitmaps wonderfully, and, if used sensible, can be extremely compact. And just about every typsetting machine on the planet uses it.
So for Microsoft to win this one, they are going to need to produce a pretty innovative product, for which the precedents are not good...
Re:Yes, but... (Score:3, Insightful)
No, it's about how open it is, if it's portable, patented, if 3rd parties can implement it, and things like that.
but whether or not the technology actually works.
If it's not portable I can't use it.
If it's not open, Free Software developers can't implement it in the programs I use.
Then it's not working. Not for me at least.
Re:Yes, but... (Score:3, Informative)
Yes. From the PDF specification [pdfzone.com]:
Adobe gives permission to anyone to:
Trying to reach Linux Format: (Score:5, Funny)
Warning: Too many connections in
Warning: MySQL Connection Failed: Too many connections in
Error connecting to dbnuke
Program:
Database: nuke
Error (1040) :
Well, I guess "Database: nuke" is a fairly accurate description of what's happening just now...
Will XDocs support 'ALL' the features in PDF? (Score:4, Interesting)
-Transparency
-Full compression via JPEG, ZIP, LZW, GIF, PNG, etc
-Font sampling, ie: reduced character sets
-Full interactivity, media support (audio, video, forms)
-Seamless support by industry standard vector editors... think Illustrator, Freehand
Look at OS X... the whole damn GUI is rendered via PDF then spit out as an OpenGL texture... will XDocs compete with that level of sophistication?
Interesting but I doubt it will be a "PDF Killer".
Maybe it will be an alternate digital media format (most likely with some insane DRM/Palladium tie in).
Re:Will XDocs support 'ALL' the features in PDF? (Score:4, Insightful)
And since this idea wasn't mentioned at all during the DOJ Antitrust trials, DOJ probably wont bother touching it.
PDF = open format, won't go away (Score:3, Insightful)
XDOC == XUL + WebServices for Office.Net (Score:4, Informative)
What it does is 'just' provide an link between a document and databases through
What does that mean?
Well, now the office suite will be able to do the same thing as XUL+Soap in moz, in a much nicer way for the end user [remember, word _IS_ the computer for most persons].
I think that's a sweet move, as long as the webservices talking to XForms are not crippled and accessible from Moz, everyone will be happy... and as long as it's not yet another vb-only scripting language :
XXX (Score:5, Funny)
MS eXchange
MS Xbox
MS Windows XP
What next?
MS Xwindow?
MS Xnotfree86?
Re:XXX (Score:5, Funny)
MS OS X.
XDocs might threaten pdf in workflow environments (Score:5, Interesting)
But I don't think it can threaten pdf in other areas, because pdf is very, very established as the standard for online read-only documents. For instance, when I was looking for a new job earlier this year, I used Open Office to generate pdf files containing my applications that I sent to employers, and I didn't get a single complaint that they couldn't read it.
Shocking, just shocking (Score:3, Interesting)
Personally, I find .pdf files a pain - they are memory intensive and usually the machine I am working on doesn't have Acrobat loaded on it (already noted here).
If MS can make this a simpler and more ubiquitous process, then so be it.... Adobe has a hell of lot more going for it than Acrobat - why didn't they just sell it to MS for a profit and be done with it? Adobe makes money and their Acrobat becomes a defacto standard.So bloody typical MS (Score:3, Insightful)
Fortunately, there's a big difference with netscape : netscape was a small company, the web was still in its infancy. Adobes pdf market (press) on the other hand is a billion dollar industry and adobe has quite a tad of experience with lawsuits. I doubt they'll just sit and scream murder...
Re:So bloody typical MS (Score:5, Funny)
Yes, I can.
They invented the gui. no wait...
They invented the PDA. no wait...
They invented the little 'x' in the corner to close the window. no wait...
They invented the mouse. no wait...
They invented the task bar. no wait...
They invented a multi-user OS. no wait...
They invented their IP stack. no wait...
They invented multi-media on the computer. no wait...
They invented the internet browser. no wait...
They invented new ways to extend monopolies and even when busted they never get punished. They only have to promise not to break the law in the same way in the future.
YUP, that is what they invented.
Re:So bloody typical MS (Score:4, Insightful)
For example, one could easily accuse Adobe of the exact same theft of concept:
(1)They patented Postscript type as a way to allow desktop publishing to advance to a point where it could compete with conventional printing shops, while similarly giving themselves a near monopoly on the desktop with applications such as Pagemaker. Speaking of which...
Pagemaker was a desktop publishing app that basically put Adobe on the map, despite it's being released at a time when there were multiple companies making various flavors of SOHO publishing solutions. Other than the GUI and certain key tools, it wasn't really that innovative, and Adobe can easily be accused of "ripping off" other software companies.
Also, the same applies to Photoshop. One could easily claim as well that it was almost a direct rip of MacPaint when it first came out. Once again, other than the GUI and key tools, it wasn't that innovative, there were hundreds of paint/edit programs on the market. Similarly, the same applies to Freehand (surprisingly, the sole piece of software that's not innovative at all, and still recieving ample competition from Corel).
Ahhh, and then we move to the PDF format, which ironically was an application meant to provide an alternative to rich text Word documents. Not exactly any innovation there either, in fact, far more bloated and complicated than even Word could ever hope to be.
So Microsoft made their own "PDF Killer"... It isn't like they haven't ripped off other companies before, the implied fear of Adobe somehow losing to Microsoft in a market where they have a considerable share is ridiculous.
Personally, I dislike PDF, especially in terms of bloat and loading delays in browsers. It's ridiculous, to have to wait an extra 5-10 seconds for Acrobat to load (and another 10-15 seconds just to load the document into the browser, just to read a tech sheet. It's gotten increasingly slower as they add idiotic things like update scans that bog the system down with redundant inquiries, and the software steers further away from what it was originally meant to do: Read PDF documents.
Now as for real innovation, don't hold your breath hoping for it. The market currently depends on a very limited range of hardware, and as long as they're locked into established standards, they won't truly become innovative. Add to that the hobbling of VC funded "innovations", which never take off due to the incapacity of CEOs to look at the big picture (as evidenced from IBM's first taste of the microprocessor, without the slightest idea of what to do with it).
At least until they learn to, and this should be the mantra: Invent.
Re:So bloody typical MS (Score:3, Informative)
Uhm, Pagemaker was originally made by Aldus. Adobe got Pagemaker by buying Aldus and killing off the company. Now Adobe is trying to kill Pagemaker itself with their Indesign.
Photoshop succeeded because it was made by photographers (the Knoll brothers) for photographers. It could handle CMYK separations, crucial for any prepress work.
Discussion (Score:5, Funny)
Steve: Why Bill, what are we going to do tomorrow evening?
Bill: The same as every evening, we try to take of the world! (whispers: Total world domination is also your friend.)
Immediate Stock Hit? (Score:5, Informative)
I can't read the slashdotted article right now, but if by "immediate hit" they mean that the stock jumped almost 12% in one day, they're right. Of course, maybe that's just related to their confirmation of projected 4th quarter earnings.
Workflow (Score:3, Insightful)
In effect, Microsoft depends on its users - largely technology ignorant - to push its technologies into areas of resistance regardless of the problems it causes. It is so like the old IBM that one can only assume the managers read IBM internal memos before bedtime. Except that IBM had better R&D, a wider range of products, and a captive market for mainframes...and it still ended up in trouble.
At the analysts party... (Score:4, Funny)
"...a new Microsoft PDF-killer technology..."
PDF-Killer. Yeah! New Technology! WOOOOP! Developers, developers, developers! Yeah. GIVE IT UP FOR ME! Dig it. WHO TOLD YOU TO SIT DOWN??? *hopping, screeching, headbutting and making satan-finger-sighns*
Dear Stockbrokers, M$ CEOs and Marketeers, what ever you smoked, don't ever offer me anything of it.
"PDF-Killer"...I just don't believe all this. Is this just me or the world or
Not really new "News" (Score:3, Informative)
For all you guys trying to read the article and cannot, here some more infos: The actual announcement is about a month old. Here's [internetnews.com] one story on internetnews (ty to /. this) covering this; and a follow-up [internetnews.com].
An alternative story can be found at Betanews [betanews.com].
BTW, creating XML-documents out of M$-Word-documents is not a new idea. Check out icoya WordXML [struktur.de] (click solutions, than icoya WordXML). It is a high performance extension for Microsoft Word in order to convert content easily into the open, format-neutral and manufacturer-independent XML format.
a replacement for Microsoft Word forms (Score:3, Insightful)
Adobe tried to make PDF widely used for that purpose but failed. And that's quite fortunate: PDF's page oriented format isn't all that hot for on-line forms either.
Why adobe purchased accelio (Score:3, Informative)
Hence the impact of this announcement. If you've actually used the Accelio stuff (and I have, a lot) you'll know that it could be massively improved upon; other [scansoft.com] products [mozquito.com] are biting at their heels already.
So MS weighs in immediately after Adobe's fanfare and says they're going to enter the market (note that XDocs does not even have a release date yet!) - its hardly surprising that Adobe's stock takes a hit.
Xdocs will feature... (Score:3, Troll)
- Windows-only support
- Enforces "Digital Restrictions Management"
- Break the format at every new Office version
- EULA that gives MS copyright for all your documents
XDocs is not a pdf competitor!!!! (Score:5, Informative)
It is basically a way to create a front-end for XML docs or XML web services. This way, a user can say, well this field is a drop-down and this one is a date field and this is how I want to arrange it on a screen. While they are doing this, they are linking the fields to nodes in the XML doc.
Think of it as a MS Access gui front-end tool over an XML source. It's focus is data entry not presentation, exactly the opposite of PDF.
If you think xdocs and acrobat are equivalent, then the same could be said about any word processor or html editor or desktop publishing tool, etc.
Article:
---
XDocs vs. Adobe:
POSTEDON 2002-10-31 13:07:47 by Linux Format Admin
Microsoft hyperdaz writes "Two weeks ago Microsoft announced XDocs, a new application that will be part of the upcoming Office 11 suite.
XDocs, according to Microsoft, will make it easier to create richly formatted online forms, and to simplify the collection of form data. Because it uses XML, XDocs form data should integrate with a variety of data repositories with relative ease.
The first reaction from tech pundits was to proclaim that a mortal blow had been struck against Adobe, the PDF file format, and Adobe's Acrobat family of PDF manipulation products. Adobe's stock took an immediate hit, and some analysts went so far as to compare Adobe to erstwhile MS competitor Netscape.
It's a bit premature to be ringing alarm bells for Adobe, though. XDocs will be a strong challenge to certain facets of Acrobat, but there are significant differences between the two products, and where they are similar, Adobe is in a position to put up a good fight.
XDocs's obvious challenge to Acrobat is in the online forms market.
In that narrow field, it's clear why XDocs is perceived as a threat: Forms, by their nature, require a client and a server. Between their virtual lock on the office productivity suite market and the popularity of SQL Server, Exchange, and the rest of the
While PDF forms can be integrated with backend sources like SAP and PeopleSoft, XDocs forms will be able to do this as well, according to Microsoft, and if XDocs is deeply integrated into Exchange and other
While Acrobat Reader may be everywhere, it's safe to say that it probably isn't used as often as Office, and Microsoft could gain an advantage in the forms market simply by producing a well designed, easy-to-use product with a user interface that's familiar and inviting to people who already use the other Office products regularly. Adobe's defense against this has been to make it possible to create PDFs from any application, including Office. How these differences will work out competitively remains to be seen, and depend on how well XDocs is executed, and how well both Adobe and Microsoft educate potential customers.
But it's important to remember that most people don't use PDFs for online forms--in fact, many people aren't aware that they even can be used for that purpose. The most common use of PDF is to securely distribute documents that can be viewed and printed consistently across different platforms. XDocs, judging from Microsoft's announcements to date, doesn't address these features, and for the foreseeable future Adobe has this market to itself. What this means is that XDocs is unlikely to take market share away from PDF--what Microsoft appears to be trying to do is limit the growth of PDF, because PDF's true strengths in secure document distribution and printing remain unchallenged.
Well before the XDocs announcements, though, Adobe was expanding the forms functionality of PDF.
"PDF is evolving beyond a document format, and is now a rich information container," according to Julie McEntee, Director of Product Management for Adobe. As part of that effort Adobe recently announced a new, more forms-friendly version of Acrobat Reader, and beefed up its line of PDF server products. And PDF has supported XML for a number of years."
---
XDocs is just a modern clone of Lotus Notes (Score:5, Insightful)
"XDocs," a code name for the newest member of the Microsoft Office family, streamlines the process of gathering information by enabling teams and organizations to easily create and work with rich, dynamic forms. The information collected can be integrated with a broad range of business processes because XDocs supports any customer-defined XML schema and integrates with XML Web services. As a result, XDocs helps to connect information workers directly to organizational information and gives them the ability to act on it, which leads to greater business impact.
Does that sound like a pdf killer to you? Does it even sound like they're after the same market? Sure they're using XML and they're making "documents" - still sounds more like Lotus Notes than Acrobat. But who uses Acrobat/PDF to collect data? Yes, there are forms in PDF, but the implementation is not nearly flexible enough to build a data collection application, nor can you build decent data collection apps around MS Word.
XDocs is designed to work with any customer-defined XML schema. Where's the proprietary nature there? You give it your proprietary schema and then you use it to build forms to collect data into that schema. All Microsoft is doing is implementing a framework to easilly collect and present information. This is exactly what Lotus Notes was doing more than 5 years ago, only with XDocs the collected data is stored using your XML DTD instead of Lotus's proprietary NSF format. I'm sure Microsoft will extend it to the web - just using an XSL transform to change the XDoc into HTML and collect your data that way.
None of this prevents you from using a PDF to archive resulting documents. To be sure, you can probably embed an XDoc form into an XML dataset and view the resulting file with an XDoc viewer - but that's still one more app that everyone needs, and PDF is still the best portable format for archiving all sorts of documents and images. XDoc just collects information. Yes... all very insidious of Microsoft. A PDF killer.. I don't think so. I don't even see it as a PDF competitor.
Not needed (Score:5, Funny)
SVG (Score:5, Interesting)
Since Adobe itself is heavily into SVG [adobe.com], it (SVG) is positioned to become the leading display document format. This is, in some ways, ironic, because most people think of SVG as an image format.
Consider:
Wow! (Score:5, Funny)
XDocs' Potential (Score:4, Informative)
One poster correctly observed that to many users _WORD_ is the computer. XDocs makes users more depenent on Microsoft. Now it'll be easier to share spreadsheets, databases, and other documents... they can do it with one program not several.
X [You can type more than that for your subject] (Score:4, Funny)
Why doesn't Microsoft avoid the confusion of a plethora of names with "X" in them and just start calling all of their products "X". Everyone should. "X reports on a new X X-killer technology to be included in X, called X." Of course, it will never run on X.
Re:Well, (Score:3, Funny)
Re:Question? (Score:3, Funny)
More importantly... (Score:3, Funny)
Re:Stock took a hit? (Score:5, Insightful)
Re:Stock took a hit? (Score:5, Insightful)
That says as much about the sad state of the way the stock market works as it does about MS. If people believe that other people believe this will affect Adobe, then they will bail out before those 'other people' do. This of course causes other people to bail out, and the next thing you know, the bottom has dropped out of the stock.
Ray
Re:Stock took a hit? (Score:4, Insightful)
Re:Stock took a hit? (Score:5, Insightful)
Re:Stock took a hit? (Score:5, Insightful)
Re:Stock took a hit? (Score:5, Insightful)
That says as much about the sad state of the way the stock market works as it does about MS.
After the result of the lawsuit came out, MS stock went up, of course. And then, so did the stock of a lot of other tech companies. After all, as my newspaper explains, when the biggest company of them all goes up so much, that means the whole sector must be on a rise!
So, in short, stock market logic:
1. Microsoft abuses their competitors, abusing a monopolistic stranglehold on many other businesses
2. But they avoid bad punishment in the resulting lawsuit, and can basically continue their practices
3. That's good for Microsoft!
4. That must be good for the competition!!
("5. Profit!" occurs only in their dreams).
Judge CKK verdict leaked before market close (Score:5, Informative)
According to él Register the report was emailed out 2 hours before time, which meant trading could happen for those fortunate enough to get such a mail before everyone else. Slashdot even reported it _before_ time.
http://theregister.co.uk/content/4/27910.html [theregister.co.uk]
Also interesting is the analysis [theregister.co.uk]
Re:Stock took a hit? (Score:4, Insightful)
That being said, the stock market is designed to be unstable and fluctuate. Why it doesn't fluctuate even more is beyond my understanding, but there must be some factors that stabilize it as well (they are called long-term investors, I guess).
Re:Stock took a hit? (Score:4, Insightful)
Take the Microsoft Pledge! (Score:5, Funny)
I Pledge Allegiance
To the Flag
That Appears on my Desktop Startup Screen.
And to the Monopoly
For Which it Stands;
One Operating System
Over All,
Inescapable,
With Freedom and Privacy for none.
(Sorry, couldn't resist. Feel free to mod me down.)
Re:Take the Microsoft Pledge! (Score:4, Funny)
To the Flag
That Appears on my Desktop Startup Screen.
And to the Monopoly
For Which it Stands;
One Operating System
Over All,
Inescapable,
With Freedom and Privacy for none.
I would like to amend this by adding "under Bill" to the "One Operating System" line.
Re:Just a side note (Score:5, Insightful)
As Office evolves it will be more and more integrated into IE and even though IE is not required by the OS, it will be required by Office. I believe that the recent ruling only concerned their dominance in the OS area, not in productive software (i.e. Office), but I may be wrong about that.
Re:IE and Office are already squabbling (Score:5, Interesting)
I'm a Web developer, and the vacillating ways IE has handled links to Office documents have caused our department no end of headaches over the last three versions of IE we've used on our corporate WAN. We're wedded to framesets for some purposes, and IE and Office can't seem to work together.
They open Office docs inside framesets, with the app in the background, like Acrobat -- and printing is screwed up and users can't save the documents. They open a separate IE window with each Office document, including menu options that are sort of half-enabled, not allowing users to use obvious features. They give up on the IE-for-Office-docs idea altogether, opening separate Office app windows for each document, and it works... but it kind of makes one wonder whether they could have figured out that frameset thing to start with, rather than slowly lurching toward the workaround we'd already resorted to for their first hacked implementation.
Print to file from Excel 2000 sometime, and see if you get a Windows API save dialog. See if it looks like the same thing in Word, for example. Um, no.
More integrated over time? Seems to me like the MS departments for Word and Excel are warring factions, leave alone IE.
Re:And just out of curiosity (Score:4, Funny)
What do you mean? Why, just the other day it took me only three hours to pick just the right font (I went with Comic Sans) for the PowerPoint presentation I may be giving (time permitting) to my peers in middle management during our half day "Effective Use of Bullet Points, Bold, and Underlining" seminar.
I can't wait for next week's "Attaching Word Docs with Large Embedded Images to an Email" class!!!
Re:Just a side note (Score:5, Informative)
It was mentioned at MozillaZine for a month ago or so that IE7 won't be released (although I have my doubts) and Microsoft will go 100% MSN Explorer in future releases of Windows.
But I'm sure what you meant was "Let me guess, The Next Browser will include built-in support for them" and I guess that's likely.
Now or never... (Score:5, Interesting)
The result is that it is up to the people to take back control. Solution, spend as a little as possible to support MS. Remember MS is a company controlled by profits. Hurt them where it hurts them the most.
Use Linux... If not, then use Windows XP, but use Open Office or other compatible tools. Remember the goal here is not to entirely stop, but stop the gravy train. MS needs growth and if we take back control and stop that growth to status quo MS will have problems. They will have to raise prices and start gouging the consumer like they do with their enterprise licensing. And with time people will come to their own senses.
The key here is not to be complacent!
Re:XDocs and PDF are quite different (Score:3, Insightful)
Given the number of PDF generators under GPL (Ghostscript, pdftex, dvipdf and various others) there doesn't seem to be much about the PDF format that's not already open.
TWW
Re:Sorry boys (Score:5, Funny)
>blockquote>I have to go and install some v.slow and large application to load them.
How is this any different from Word Documents?
Re:Sorry boys (Score:4, Informative)
I had this issue too on a laptop at the weekend. Thankfully I was connected to the internet so I just plugged the URL into google and it provided an option to convert it to HTML.
Of course, it's not exactly the best conversion in the world, but at least you can read what is in the file.
Re:Sorry boys (Score:3, Interesting)
Re:Sorry boys (Score:3, Interesting)
Portable Document Format. As in documents you can edit. You don't happen to have missed the fact that you can actually load and edit PDF files just like DOC files if you have an application which can handle it?
On my linux box, DOCs are just as limited for me as PDFs are for you.
Re:Sorry boys (Score:5, Funny)
You cannot, however, get Adobe Acrobat 5.x for free from Adobe's website (to be able to edit files). Nor is there another free utility (that I know about at least) that lets you edit existing PDF files.
Furthermore, Adobe Acrobat Reader does not kill its process when you exit. It happily hangs around eating up your memory, which makes it a pain in the ass to use on older computers without 74 gigafloppy interweb RAMs of memory (that's technical talk for "a lot of memory" by the way).
I think that if Apple or a third party came up with a non-Adobe solution for a PDF-like document, that could easily kill Microsoft's idea. Or, you can create confusion by offering so many choices that the user just says "F- that! I'll just stick with what I have."
Also, the original's story comparison of this to IE vs. Netscape is a bit faulty. There's no real reason for Joe McRegularUser to have both Internet Explorer and Netscape. Both will allow him to check NBA scores and hot asian teen pix. However, unless this Microsoft application can now handle PDF files as well (my winword.exe only spits out gibberish), AAR will always be necessary. It's kind of akin to me really really hating RealNetworks, but still having bloated GUIware like RealPlayer installed because there's no other real option (pun intended). Just because I have the new XCrap.net document editor, doesn't mean that I don't need Adobe Acrobat Reader.
My solution to this whole big mess? Do what warez kiddies do. Just releases everything in
Of course Microsoft would write back and say that now Edit.com will be integrated into Office, Windows Media Player, and Microsoft Soccer.
Re:Sorry boys (Score:3, Insightful)
And this is precisely what I look for when I publish a document for public or customer consumption. I want the final image of the document locked down, unmodifiable, the way I intend it to be. No messing with the formatting, fonts, colours or anything else that I carefully put together to convey my message.
To too many people a document is just text. This is far from the truth. A document is a presentation, and says a lot about the person or organisation that prepared it. From technical notes to marketting, control over document format is a vital part of publishing.
And that is why PDF kicks the arse of other formats when it comes to this type of use.
Re:Sorry boys (Score:3, Insightful)
A document is a presentation
That is the bad viewpoint that I wish PDF didn't promulgate. I know, I know, Adobe is just responding to demands of the market...
so I really have to focus my ire against the unwashed masses who think they're graphics designers and that they actually need fancy layouts. Or at the even greater masses who allow themselves to be swayed by such trivalities.
The kind of publishing that needs formatting, fonts, and color is mainly about deception. With rare exceptions, text is the truth, and the window-dressing tries to hide it. From Madison Avenue advertising shills to corporate Annual Report polishers to the legions of "PowerPoint(tm)
Engineers" infesting government contracting, its all about getting your words to be judged by something other than what they say.
Many authors aren't concious about doing this- they just want to fit in with everyone else- but that doesn't make it any more honest.
(Yes, there are people who prepare truely graphical data, and who need to lay it out precisely. They are in the minority)
(Yes, for content not delivered over computer- flattened wood pulp or something- carefully prepared alignment is an aid to comprehensibility. But there's no reason to carry this forward into the digital era).
In a more ideal future, all presentation issues will be decided on the client side. You send me the data, and I've configured my software to present it the way I prefer. It won't happen for a while yet, but I can dream. And the continued use of PDF blocks this dream.
Re:Why not use DjVu? (Score:3, Informative)
But, as far as I can tell, that's where the fun stops. AFAIK, it doesn't handle vector graphics, and has nothing to offer over PDF for strictly digital documents. In the digital world, PDF produces perfect results, automatically.
OTOH, PDF is not geared toward scanned documents. I've seen a lot of examples of, say, scanned datasheets in PDF; all of them were bad.
I thus submit that each respective format has its own well-defined niche, and fills it admirably.
Ghostview certainly could support DjVu, if someone wrote the appropriate code for ghostscript. That it supports GIF, JPEG, PNG and PDF would tend to indicate that it's well within the scope of the software's design parameters.