Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Microsoft Software

MS vs. Open Source Office Suite Compatibility 576

Anonymous Coward writes "Though Microsoft may soon be blocking Office suite compatability with open source productivity tools, in the mean time Hal Varian (of Berkeley) has conducted the Microsoft Office-Linux Interoperability Experiment which shows a surprising amount of interoperability. Hey, another reason NOT to upgrade to the new version!"
This discussion has been archived. No new comments can be posted.

MS vs. Open Source Office Suite Compatibility

Comments Filter:
  • important to note (Score:5, Informative)

    by maharg ( 182366 ) on Wednesday September 03, 2003 @05:56AM (#6857261) Homepage Journal
    It is important to note that even Microsoft Office has trouble opening some versions of Microsoft Office programs

    Sad but true ;o)
    • by Anonymous Coward
      For microsoft any product other than the latest version is a competetor , whether its from other verndors or their own old version doesnt matter
    • Re:important to note (Score:5, Interesting)

      by madmarcel ( 610409 ) on Wednesday September 03, 2003 @06:54AM (#6857445)
      From the article:
      "forward compatibility has often been a problem."

      Correct, but I'd venture that most software would suffer from that, not just M$ Office.

      However, please note that backward compatibility is also problematic with (some/all) M$ software.

      IMHO there is no guarantee that a newer release of a given M$ program will be able to open files from an older release of that same program. Again, this is not unusual for (a lot of/some) software. But of course, with open source this doesn't pose as much of a problem.

      FWIW I seem to remember running into trouble when I used M$ Publisher. I have a newer version installed on one of these machines <<gestures>> that cannot open publisher files from an older version of Publisher. These 2 different version are sequential releases...I think that is unacceptable >:\
      • Re:important to note (Score:5, Interesting)

        by Laur ( 673497 ) on Wednesday September 03, 2003 @09:00AM (#6857993)
        Forget forward or backward compatibility, how about current compatibility? As in opening a file created in that version of Word and having it look the same! Just a few days ago I was working on several complex documents. They're about 100 pages each, and are an electronic revision of older hardcopy documents, so there is lots of formatting (manual page breaks, weird line spacings, custom margins and such) in order to closely match the hardcopy. I closed it down in the evening on one day, and when I opened it the next morning the formatting had changed! Text that used to fit over a single page was now spread over two pages, things like that. I had my coworker open the file and it looked correct on his computer, but was screwed up on mine. And according to Word we have THE EXACT SAME VERSION, down to the minor version numbers, and as far as I know nothing changed in my configuration overnight. Very irritating, I can tell you, but there was no other choice but to waste several hours going through page by page correcting margins, line spacing, etc. until it was once again correct. A program which can't even open its own files reliably is a total piece of crap, IMO.
        • Re:important to note (Score:5, Informative)

          by IM6100 ( 692796 ) <elben@mentar.org> on Wednesday September 03, 2003 @09:10AM (#6858063)
          Believe it or not, and it is unbelieveable in this day of networked computers with many printing and output resources available to them, Microsoft Word's formatting functionality is in part, and it's a significant part, dependent on what default printer you have it set up to use.

          It's an unbelievable anachronism, but it's the truth.
        • Re:important to note (Score:4, Interesting)

          by Planesdragon ( 210349 ) <<su.enotsleetseltsac> <ta> <todhsals>> on Wednesday September 03, 2003 @10:16AM (#6858541) Homepage Journal
          And according to Word we have THE EXACT SAME VERSION, down to the minor version numbers, and as far as I know nothing changed in my configuration overnight.

          Do you use the same default printer? Word pulls a lot of functions from there.

          In any case...

          If you want to replicate a printed document, you should use word to make PDFs. (There are free PDF makers that are almost-but-not-quite as good as Acrobat.) Word is a word-processing program, to be used for writing and "I don't really care about the specifics" document layout. If precise formatting is important, then _don't use word._ It wasn't designed to do more than "good enough" in that job.

      • by belloc ( 37430 ) <belloc@latinmaiO ... inus threevowels> on Wednesday September 03, 2003 @12:02PM (#6859532) Homepage
        Correct, but I'd venture that most software would suffer from that, not just M$ Office.

        Strange, I can open any document that I've created between 1989 & 2003 with any version of my word processor suite.

        God love ya, vi & tex.

        Belloc
    • Re:important to note (Score:4, Informative)

      by ortholattice ( 175065 ) on Wednesday September 03, 2003 @09:45AM (#6858283)
      I don't understand why the authors, who made this statement, didn't quantify it by including Microsoft's own software products in their table. Then it would be much more meaningful.

      On a personal note I have had several occasions when a corrupted .doc has refused to open at all in Word '97 but opened in StarOffice, with the corrupted place highlighted in red. I thought that was nice. (This particular version of Word had a tendency to corrupt its own documents occasionally, when we used a certain template imposed on us by our customer.)

      It would also would have been interesting to note whether the alternatives have Word's awful feature of formatting pages slightly differently as a function of what printer is currently active. A few years ago this caused us to postpone a telephone conference because everyone's page numbers were different; we faxed a hard copy to everyone to correct the problem. If the open source alternatives don't have this "feature" I would call that a significant plus.

  • A pity... (Score:3, Interesting)

    by Anonymous Coward on Wednesday September 03, 2003 @05:58AM (#6857269)
    that the new gtk+2 version of Abiword is not out yet. It would have fared much better. I am sure it is the same for Gnumeric. I hope they will repeat this test once they come out, I use cvs versions of both of these and imho they beat OOo in almost every department, be it looks, speed or ease of use. OOo does have slightly better MS Office compatibility, but not by much.
  • Plenty of reasons (Score:5, Interesting)

    by Pompatus ( 642396 ) on Wednesday September 03, 2003 @05:58AM (#6857270) Journal
    Hey, another reason NOT to upgrade to the new version!

    I use word processors to write school papers. When it comes down to it, writing a school paper requires one important feature, spell check. That was available on the C64. I'll bet most people are like me in that they NEVER need to upgrade (no, I don't have the trusty C64 anymore, but I haven't upgraded office since 97).

    You really have to hand it to the Microsoft marketing dept for making everyone believe they need to upgrade every year.
    • by rf0 ( 159958 ) <rghf@fsck.me.uk> on Wednesday September 03, 2003 @06:04AM (#6857290) Homepage
      Of course we need to upgrade....We need to see how annoying the new animated logos are

      Rus
      • by thebreathalyzer ( 601189 ) on Wednesday September 03, 2003 @09:18AM (#6858122)
        Regrettably, I think I found a use for clippy that's about on par. I started letting my preschooler play with Word with one of them visible. Later, I invested a whopping 12 or so hours to make a "game" that teaches the alphabet using the Agent control. That was my undoing.
        Now, whenever I open Word and I forgot to hide the assistant, my son (from the other side of the house, mind you) will run screaming from the other side of the house to play his game or type on Word. On the way, he usually racks up 1 or 2 cats, the dog, and at least one piece of furniture. When he gets to the computer, he finds me trying to get started on a report for school.

        Him: "I want to play my game, daddy"
        Me: "Not right now. I've gotta do something for school"
        Him: "That's not fair."
        Me: "Sorry, bud, but I have to get this done."
        Him (Alternate 1): "You want a piece of me?" (Assumes Jet Lee pose)
        Him (Alternate 2): "I'm gonna pop a cap in your ass, daddy." (Thank his mother for that one...)

        I for one have happily made the transition to OpenOffice because, well, it's just safer...
    • School papers need one other important features: the ability to quickly repaginate after changing fonts, margins, and spacing!
      • Re:Plenty of reasons (Score:5, Informative)

        by zakezuke ( 229119 ) on Wednesday September 03, 2003 @06:22AM (#6857342)
        School papers need one other important features: the ability to quickly repaginate after changing fonts, margins, and spacing!

        Actually, circa 1985-1990, was sorta pre-WYSIWYG. While the classic 8bit systems had "fonts" you couldn't really see them on screen. For the most part fonts were not proportional, as in print was typicaly in the form of a fixed number of characters per inch.

        Some printers did have an option for proptional fonts, but this was not commonly used because you had to change your habits like using a tab rather then spaces.

        There was NO real need to re-paginate if you just recycled your paper and just printed the number at the approperate point on each page. In fact, you can still do this in the 21st century if you had to.

        • by IM6100 ( 692796 )
          But back in 1985, computer users spent a good deal of money to get a printer that would closely emulate what a typewritten page looked like, i.e. expensive daisywheel printers.

          These days people have the arrogant notion that their written text should look like it was typeset in a proprotional font, without having crossed the desk of a good editor and being published first.

          And that's not really a good thing.
    • Re:Plenty of reasons (Score:5, Informative)

      by rsilvergun ( 571051 ) on Wednesday September 03, 2003 @06:27AM (#6857363)
      I think you'll find that features in modern office software that make creating 'Lovely Documents' (I think Dilbert coined the phrase) easier, very helpful in both academia and buisness. That's why MS-Office is such a killer app. People recieve attractive documents better irrespective of their content. Make your papers look nice and you'll get better grades.
      • Re:Plenty of reasons (Score:3, Informative)

        by richieb ( 3277 )
        in modern office software that make creating 'Lovely Documents'

        You're kidding, right? Compare the appearance of documents created with LaTeX to Word documents. LaTeX wins.

        Most academic papers (al least in math and CS) is still done using LaTeX. It let's the author concentrate on the content and let's the computer concentrate on beatiful output.

        • by Bob Uhl ( 30977 ) on Wednesday September 03, 2003 @11:15AM (#6859095)
          You're kidding, right? Compare the appearance of documents created with LaTeX to Word documents. LaTeX wins.

          Amen, brother. My senior year in college I converted from Mac to Linux & from WYSIWYG to LaTeX, and I never looked back. Absolutely beautiful output with hardly any effort at all. I got all As that year, and while part was due to improved study habits (to write a paper, check every possible book out of the library, head to the local pub and don't leave until it's written), I credit most of it to the fact that the standard LaTeX article template is so pleasant to read.

          WYSIWYG was really a step backward, unfortunately. Text should be written as content, then rendered into a visually appealing form automatically.

      • Re:Plenty of reasons (Score:3, Interesting)

        by Zigg ( 64962 )

        While I mostly agree, the sad fact of the matter is that no software yet exists that can magically apply lovely documentism. They all do a fairly good job if the end-user is of the "style" mental state rather than the "hand-tune" mental state -- i.e. semantic vs. presentational markup. If they can get themselves to defer to the computer for the style, then their documents will look good.

        Most people just don't grok it, though. At my church, there's a computer that runs PowerPoint slides with song lyrics

    • by laughing_badger ( 628416 ) on Wednesday September 03, 2003 @06:39AM (#6857400) Homepage
      Tell that to a friend of mine that submitted a design for a web book search database, which would be maintained by the school Liberian.
    • Re:Plenty of reasons (Score:3, Interesting)

      by muirhead ( 698086 )
      You really have to hand it to the Microsoft marketing dept for making everyone believe they need to upgrade every year.
      That's exactly the way it is. MS marketing have a huge bucket of money and will go on convincing, the great majority of people, that they need the latest MS product. It's called free speech, and it costs a fortune.

  • features (Score:5, Interesting)

    by KingJoshi ( 615691 ) <slashdot@joshi.tk> on Wednesday September 03, 2003 @06:00AM (#6857273) Homepage
    Most of the Microsoft Word files that we downloaded, for example, did not use mathematics, outlines, tracking changes, or other such features.

    Right there is where most problems will occur. Also, after reading enough of /., lack of support of VBScript would be another obstacle.

    Also, I wonder how KOffice will do after they switch their file formats and stuff. It could only help, right?

    • Re:features (Score:3, Interesting)

      Also, after reading enough of /., lack of support of VBScript would be another obstacle
      Not really... I think you'll find that just about everybody these days has got Macros turned off to prevent propagation of macro viruses... Besides... does anyone really use macros at all or were they yet another Gee-Whiz feature to count on the spec sheet that such and such competing product didn't have...
      • Business users (Score:3, Interesting)

        by ggeens ( 53767 )

        Home users typically don't care about VB macros. For companies, it's different.

        There must be thousands of little "business applications" that are Word or Excel macros. Each of those might contain only a few lines of code, but in a large organization, there are a lot of those.

      • Re:features (Score:4, Informative)

        by div_2n ( 525075 ) on Wednesday September 03, 2003 @08:08AM (#6857681)
        Believe it or not some companies actually use excel spreadsheets in their supply chain control. Toyota does. Office 2000.
      • Re:features (Score:3, Informative)

        by gspira ( 654441 )
        Well, the several thousand lines of Word VBA code that drive the Document Production system here are not considered to be a "Gee-Whiz" feature.

        In fact, the lack of VBA is one of the main reasons why I won't switch away from Word right now. Try finding a developer that can understand Corel PerfectScript.. :)

  • by Noryungi ( 70322 ) on Wednesday September 03, 2003 @06:01AM (#6857278) Homepage Journal

    As they say themselves, this was based on files downloaded from the Internet, which were probably designed in order to be viewed by the greatest number of people.

    Hmmm... Then again, putting MS Office files on the Internet, instead of PDF of plain HTML probably means the user do not have enough computer knowledge to optimize said files. So, it's a good point.

    On the other hand, I am surprised that the numbers for StarOffice are greater than the numbers for OpenOffice... How come?

    Anyway, this is good news, and should be a valuable lesson for most people with PHBs... =)
    • Re:Pretty light.... (Score:3, Informative)

      by neonstz ( 79215 ) *

      On the other hand, I am surprised that the numbers for StarOffice are greater than the numbers for OpenOffice... How come?

      They used StarOffice 6.0. OpenOffice is based on StarOffice 5.2 (at least the version they tested).

      • Re:Pretty light.... (Score:5, Informative)

        by bdeclerc ( 129522 ) on Wednesday September 03, 2003 @06:58AM (#6857456) Homepage
        They used StarOffice 6.0. OpenOffice is based on StarOffice 5.2

        StarOffice 6.0 is based on OpenOffice.Org, which in turn is based on StarOffice 5.2

        The reasons for the difference might be small differences between the OO.o version they tested, and SO6.0. If they use OO.o 1.1RC3, I suspect the results would be very different, as the MSOffice import filters are hugely improved in the new release.
    • Re:Pretty light.... (Score:4, Informative)

      by kfg ( 145172 ) on Wednesday September 03, 2003 @07:21AM (#6857515)
      "On the other hand, I am surprised that the numbers for StarOffice are greater than the numbers for OpenOffice... How come?"

      Money. StarOffice costs some.

      No, I'm not just being snide ( that's just a value added bonus), SO contains propriatary filter code that Sun distributes under third party license, thus SO has always been a bit better at compatibility.

      The OOo people are having to reverse engineering these propriatary filters themselves so they're still playing catch up. They get a bit closer with every release.

      KFG
  • Anti-trust ruling (Score:5, Insightful)

    by stephenry ( 648792 ) on Wednesday September 03, 2003 @06:01AM (#6857280)
    What I don't understand by this is that under the US anti-trust settlement, Microsoft were made to release the specifications of their communication protocols to competitors.

    Clearly, the intention of this settlement wasn't so that everyone could simply see what's in, for example, a word document (which is a communication protocol in itself), but how to build program which interoperate with them. Shouldn't the developers of Open Office then be able to simply download the DOC specs off of Microsoft.com and build it into their system? Or, am I assuming that the "settlement" was an actual binding agreement?
    • Re:Anti-trust ruling (Score:5, Informative)

      by carrier lost ( 222597 ) on Wednesday September 03, 2003 @06:52AM (#6857440) Homepage

      What I don't understand by this is that under the US anti-trust settlement, Microsoft were made to release the specifications of their communication protocols to competitors.

      That's true, in spirit. In actuality, if I remember correctly, the conditions under which MS is required to open the protocols for the office products contain at least two rather difficult obstacles:

      1 - Licensing fees [slashdot.org]
      2 - J. No provision of this Final Judgment [usdoj.gov] shall:

      1. 1. Require Microsoft to document, disclose or license to third parties:
        1. (a) portions of APIs or Documentation or portions or layers of Communications Protocols the disclosure of which would compromise the security of a particular installation or group of installations of anti-piracy, anti-virus, software licensing, digital rights management, encryption or authentication systems, including without limitation, keys, authorization tokens or enforcement criteria; or

      MjM

      Oops, they did it again...

      • by mijok ( 603178 ) on Wednesday September 03, 2003 @07:23AM (#6857523)
        Quote from the public comments on the revised proposal to final judgement [usdoj.gov]:
        373. However, the major comments concerning file formats request disclosure of the file formats of Microsoft products such as Office. Office does not meet the definition of Microsoft Middleware, and so it does not fall under Section III.D. Nor is Office implemented natively in a Windows Operating System Product, so it does not fall under Section III.E. Thus, the file formats for Office will not be disclosed or licensed pursuant to the RPFJ.
        Paragraphs 371-375 on the page contain more information about it but that's the main point.
  • by Boss, Pointy Haired ( 537010 ) on Wednesday September 03, 2003 @06:01AM (#6857282)
    Word 97 is a perfectly adequate word processor. So was Word 95 for that matter.

    Word 2004 can't be many lines of code from self-awareness.

    MS went absolutely over the top with Office; you get "features" now that well over 99% of their user base will never even SKIM the surface of.

    Clever marketing and PHB one-upmanship are what convinced the masses to go with this ridiculous and unnecessary upgrade path.

    Operating Systems progressing through research and improved hardware I can understand; but you DO NOT need a new version of a bleedin' word processor every year.
    • Don't forget ... (Score:4, Insightful)

      by zonix ( 592337 ) on Wednesday September 03, 2003 @06:14AM (#6857318) Journal
      Clever marketing and PHB one-upmanship are what convinced the masses to go with this ridiculous and unnecessary upgrade path.

      Don't forget incompatibility between formats used in some of their different MS Office versions.

      z
    • Outlook 97 (Score:5, Insightful)

      by cloudless.net ( 629916 ) on Wednesday September 03, 2003 @06:18AM (#6857331) Homepage
      Word and Excel are fine in Office 97, but Outlook is not. Outlook 97 sucks, and Microsoft had to release Outlook 98 upgrade free for Outlook 97 users. There is still room for improvement even for Outlook XP, you will see some cool stuff in Outlook 2003.
    • by pubjames ( 468013 ) on Wednesday September 03, 2003 @06:21AM (#6857338)
      MS went absolutely over the top with Office; you get "features" now that well over 99% of their user base will never even SKIM the surface of.

      And yet features that lots of people would find useful aren't incorporated because they don't fit in with MS strategy.

      When I tell small business clients that OpenOffice will write PDF documents just by going "save as", their eyes light up.
      • You can do that in MS Office on OS X - but only because "save as PDF" is built into the entire OS, so all apps have the ability to do so.

        I have found this to be an invaluable feature, since I use AppleWorks. I use the pdf features to create my CV and cover letters, and the rich text format to share with MS Office users.
    • by azaris ( 699901 ) on Wednesday September 03, 2003 @07:14AM (#6857496) Journal

      MS went absolutely over the top with Office; you get "features" now that well over 99% of their user base will never even SKIM the surface of.

      Clever marketing and PHB one-upmanship are what convinced the masses to go with this ridiculous and unnecessary upgrade path.

      The problem is, there are a lot of heavy-duty Office users who do use those features that somebody who just writes one research paper a month never uses. For example, some companies run their whole production and financial planning in custom-built Excel spreadsheets, and if Excel 2000/XP/2003 offers some feature OpenOffice doesn't they'll never switch in a million years if it requires them to rewrite the whole shebang.

      Just because you don't use a feature of your Office suite, don't assume no one does. One percentage of ten million Office users equals a hundred thousand people who absolutely depend on that feature.

      • Yes, but that means there are 9,900,000 people that don't need those features. Maybe the numbers don't exactly break down that way, but shouldn't that translate into a huge segment of the market which would be perfectly fine with OpenOffice? To rephrase another poster, why should they pay for those features that they won't need? But what I mean is that the majority shouldn't buy MS Office at all. Shouldn't niche features be for a niche market?

        And you might even break it down further. Maybe your accoun
    • MS went absolutely over the top with Office; you get "features" now that well over 99% of their user base will never even SKIM the surface of.
      And this is bad, why?

      Per Abrahamsen
      Church of Emacs

  • Comment removed (Score:4, Insightful)

    by account_deleted ( 4530225 ) on Wednesday September 03, 2003 @06:05AM (#6857292)
    Comment removed based on user account deletion
    • I've been struggling with the same issue as I prepare my resume. Do I write it in OpenOffice, impressing those who get it, and save to Office and PDF and give out all three versions? ...or do I just "do the smart thing" and go ahead and write it OfficeXP and make sure that all and sundry think I'm "normal". There's nothing I want less than to start a job interview niggling over compatibility issues!

      I've finally decided to just write my resume in XML (no kidding) and write a couple XSDs to turn it into an
      • Ok, now explain why RTF isn't good enough for your resume, which everyone under the sun can read? Of your choices, go pdf. Everybody can read pdf, and if your formatting is that important to you, it'll insure the hr department gets it right.
      • by gad_zuki! ( 70830 ) on Wednesday September 03, 2003 @07:35AM (#6857561)
        When I'm in a position like that I'm thankful everyone can read RTF. Its not feature rich, but it works for just about anyone. Also its becoming a de facto rule to make any 'fancy' document a PDF anyway. Personally, I prefer PDFs for something that isn't supposed to be edited by anyone else. I can pull this trick off because I can make PDFs free with PDF995, Open Office, or in Linux. Way too many people assume it will cost them $250 for the power of making a pdf and Adobe isn't quick to correct them.

        Not to mention the office copier at my only client site is Red Hat based and will take a scanned copy and email you a PDF. Very handy.

        What I'm very curious about is will MS make Word be able to open sxw files by default? Perhaps when OO hits critical mass? Something tells me sxw support, if it comes, will be in some hard to find converter pack that asks you for your original office CD.
  • by tcdk ( 173945 ) on Wednesday September 03, 2003 @06:06AM (#6857298) Homepage Journal
    We have a mixed office, with most users running MS-Office and (mainly) the developers running OpenOffice.org.

    Most of the problems are with word document are with imbedded graphics. Sometimes they show up in funny places. Sometimes not at all.

    Large spreadsheets can be a problem (export from something). OOo has a limit at 32000 rows, it does give a nice warning about it, thought.

    Haven't had any problems with powerpoint presentations.

    If I could get the rest of the house to spend the time to learn to use OOo, MS-Office would be dumped in a second.
    One thing is sure - we will not be buying new Ms-Office licences (but as we have already payed for those we have, I'll not be forcing something new on exsisting users, when it isn't nessesary).
    • "Most of the problems are with word document are with imbedded graphics. Sometimes they show up in funny places. Sometimes not at all."

      If they don't show up at all, the author made a link to the graphic, didn't actually embed it. It's still on their hard drive. If they show up in funny places, they left it as a "floating" embedded graphic, and the spacing shifted enough (change of fonts, margins, etc) to make it move.

      To nail a graphic into place in any word processor, don't link it, and make sure the "

  • by minus9 ( 106327 ) on Wednesday September 03, 2003 @06:07AM (#6857302) Homepage
    "Though Microsoft may soon be blocking Office suite compatability with open source productivity tools"

    Microsoft may soon be blocking office compatibility with ANY productivity tools. They don't care whether the source is open or closed, just that it is not a Microsoft product.
  • Really surprising? (Score:3, Interesting)

    by locknloll ( 638243 ) on Wednesday September 03, 2003 @06:08AM (#6857306) Homepage
    This more or less confirms my experiences I've had with MS Office -> OpenOffice interoperability in everyday use. While using Windows at work, I use Linux at home, and so far I've only had minor issues moving between the two worlds. So what's the deal about the story?
  • by dcordeiro ( 703625 ) on Wednesday September 03, 2003 @06:09AM (#6857308)
    You really should care if you can log in via LDAP in a Windows AD; or if you can share a file betweens different OSs, or be able to map a network drive.. but file formats ?

    If you want to send anything to outside your organization, send if in PDF format. Its portable and "write-protected".
    And inside your organization, for sure someone already has ditacted a office package as "the standart". If it is Windows Office, KOffice or StarOffice, it doesn't matter, because everybody will use the same product.
    If you get some of this files from outside, just use one of the many converters available around.

    The problem with the Linux Office packages is simply one:
    Everybody that already worked 2 days with a computer knows how to work with MS word, MS powerpoint and MS excel. Switching to another office package is seen as a dificult task, because the interface is always diferent.

    My 2euros (cents dont buy you anything these days)
  • by MadX ( 99132 ) on Wednesday September 03, 2003 @06:10AM (#6857309)
    Micro$oft is not going to simply say "Hey .. here is a free / opensource version of a comparable product to our office if you cannot afford it"

    No, I think that they will keep there advertising campaign going and offering the likes of MS Works as the alternative to their more expensive package. And how many basic system users do you know of that have been following the development of OpenOffice ??
    The average user walks into a computer store and says "I need a computer to type letters / send mail / basic calculations", and I can almost guarantee that the salesman will make an MS Office /Windows Sale. Maybe that is where projects like OpenOffice need to have "boxed" releases that the public can SEE the choice on the shelves.
  • Nice to see... (Score:5, Insightful)

    by Alkarismi ( 48631 ) on Wednesday September 03, 2003 @06:11AM (#6857311) Homepage
    an academic report backing real-world experience!

    Although it must be said that this study is *quite basic*. The authors, to be fair, do point out however that "This particular experiment should be considered a pilot study that could be extended to a larger one.

    Our experience in the 'real' world is exactly the same - compatiblity, for the most part, is *good enough*.

    We have been rolling out small pilots with a number of clients using exactly this line of reasoning. For many IT departments who have lived through the *gratuitous incompatibilities* between succesive generations of Microsoft Office, this is all that is required to evaluate alternatives.

    Yes, we should strive for 'perfect' interoperability. No, it is not necessary to begin migrating real businesses to an Open Source desktop.

    Just my 0.02!
  • Format change (Score:4, Insightful)

    by jabbadabbadoo ( 599681 ) on Wednesday September 03, 2003 @06:13AM (#6857317)
    Microsoft will change the format, but they are required to keep it in the open.

    What Microsoft is about to do, is to introduce an enourmously complex, ill-documented format. Just wait'n'see.

  • missing data? (Score:5, Interesting)

    by Sparr0 ( 451780 ) <sparr0@gmail.com> on Wednesday September 03, 2003 @06:14AM (#6857319) Homepage Journal
    What is really missing from the chart is statistics on MS Office :) I want to see Office 2003, Office 2002, Office ... 97 on that chart, and see how well each of them handles this 'random' sample of office files. Forwards compatibility is almost non-existent, and backwards compatibility is much more broken than you would think. I think Star Office and Open Office might actually beat MS Office * in that scoring methodology.
  • by Deton8 ( 522248 ) on Wednesday September 03, 2003 @06:15AM (#6857322)
    One of my engineers switched to StarOffice a few months ago and nobody noticed until he told us. His documents, spreadsheets, PowerPoints, and emails all open fine on our PC's with Office, and he reports no problems reading the stuff we send him. He gets lots of PowerPoints from vendors and reports no problems there, either. So it's good enough for routine office-type use. Serious tech writers don't use Office anyway, so minor glitches with table formats are not likely to work their way into formal product documentation.
  • by panurge ( 573432 ) on Wednesday September 03, 2003 @06:23AM (#6857347)
    It's worth noting that the Star Office 6.1 beta has PDF output available, which works nicely. It has also managed to cope rather well with the Office stuff I have thrown at it, including Powerpoint. The main problem is the lack of support for certain Excel structures (PivotTables, anyone), though privately I think that these have no place in a properly designed IT system- if you need this stuff you should be using a proper database engine and front end to give control.

    In fact, 6.1 seems a nice product generally and is the first version of SO that I think I can actually recommend to clients when it is released. It may even be possible to train users to export PDFs for email, which would be a big win.

  • Features (Score:5, Interesting)

    by ajs318 ( 655362 ) <sd_resp2@earthsh ... .co.uk minus bsd> on Wednesday September 03, 2003 @06:27AM (#6857360)
    I was made to do some text editing in MS Word in my last job. I had to modify a document somebody else had started.

    Beside attempting to do table formatting with strings of spaces {I know this is acceptable, even encouraged, in programming, when monospaced fonts are used; but it totally breaks proportional spacing}, the author also had manually numbered the pages.

    I was heavily tempted to refuse to do the editing on the grounds that (a) the original material was unfit to use as a starting point and (b) I was having difficulty finding a copy of MS Word.

    And now, the point, part one. What I'm really looking for is a word processor that can take such childish attempts and format them properly. Work out where the author was trying to line up the tabs, and change the space-spaced stuff to proper tabbed columns.

    Or, maybe someone could make a USB shotgun accessory that will blow a luser's head off if they try certain effects. Such as
    • Attempting to format using spaces
    • Attempting to generate page numbers, tables of contents, or anything else that the computer can do for you, by hand *
    • Using more than three fonts in a document
    • Using the font 'comic sans MS' for anything at all
    The point, part two, is that WordPad is not a word processor. It does not incorporate a spelling checker. Whose priorities are so warped that they would omit such a basic necessity while incorporating changeable fonts and colours? It matters not what meretricious decorations are applied to the text if the spelling is all cocked up! It does not even qualify as a text editor; it is a viewing tool. And a poor one at that, because its output often does not resemble the output of Word.

    * I have actually heard of someone creating a spreadsheet, then adding up the figures with an idiot-calculator and entering this in the total box
    • Re:Features (Score:3, Informative)

      by zakezuke ( 229119 )
      And now, the point, part one. What I'm really looking for is a word processor that can take such childish attempts and format them properly. Work out where the author was trying to line up the tabs, and change the space-spaced stuff to proper tabbed columns.

      Excel does this, does it very well.

      I often use Excel just for its ability to take data and organize it, assuming it's delimited by a common field. Wonderful for adapting documents. In theory star office offers this in their calc, but I have never a
  • by Jjaks ( 104293 ) on Wednesday September 03, 2003 @06:29AM (#6857368)
    We used Office 2000, which succeeded in opening all Office files, but we venture to guess that Office 98, say, would have had difficulties with some of them.

    The only version of Office that is called Office 98 is for MacOS, as far as I know. For Windows the more recent versions are 95, 97, 2000 and XP.

    It is also very interesting to see the difficulties for Microsoft's Office suite when it comes to the interoperabilities between Office 97 on Windows and Office 98 on MacOS. At a company I worked at in 1998, we had both Macs and Windows machines, and amazingly enough, it was not trivial to make some documents written in Office 97 on a Windows machine work in Office 98 on a Mac (and vice versa).
  • by broothal ( 186066 ) <christian@fabel.dk> on Wednesday September 03, 2003 @06:33AM (#6857382) Homepage Journal
    What I really would like to see was, if they'd tested Microsoft Office as well. By that I mean, they should try opening the same documents in, say, Office 97 and test it the exact same way as the others.

    The article does mention that, but I reckon most readers will just look at the table and say "I need 100% - I'll take MS office"
  • by davids-world.com ( 551216 ) on Wednesday September 03, 2003 @06:35AM (#6857388) Homepage
    What was tested here was how well different office suites could READ documents that were (most likely) produced with MS Office (since MS Office has a 9x% market share, and it's unlikely that you generate .doc for web dissemination if you're using Open Office).

    Unfortunately, this tells us very little about interoperability, as needed in an office/colaboration environment, where people need to read my files and my revisions to their files.

    Just to read other people's files, I prefer a format like PDF anyways.
    • Well kword and others just export to rtf, but give it the extension .doc - so word should always be able to handle it.
      OOo was thinking of doing the same iirc.

      (btw for those that say rtf is less powerful - it's not. rtf can do everything the latest word can do - even ole objects etc)

  • More recent tests? (Score:3, Interesting)

    by Framboise ( 521772 ) on Wednesday September 03, 2003 @06:42AM (#6857410)
    I wonder that a study made in January 2003 is only published in August! In the meanwhile OpenOffice (1.1rc3) has improved a lot, StarOffice 6.1beta is available. The experiment should be redone soon.
  • by JessLeah ( 625838 ) on Wednesday September 03, 2003 @06:49AM (#6857433)
    This story [slashdot.org], published on SlashDot less than 24 hours ago, notes that interoperating with the next version of the Word format may soon be a DMCA violation due to design decisions being made by MS (i.e. using DRM "features" in the format itself).

    What good is OpenOffice if it's illegal? It'd get railroaded right off of the "legitimate" Internet just like DeCSS, and if someone finds out that you used it, you could very well go to jail. Not my cuppa.

    I wish that we in the SlashDot community would have a longer memory, and that we would organize some sort of community against the DMCA (for it is the law which permits this sort of egregious BS). We should be rallying in the streets, but we're not. Pretty soon we may all be FORCED to buy a PeeCee with Windows and MS Office, or we will be completely unable to interoperate with the DRM-"protected" .DOC format everyone else will be using. (And if you think everyone won't upgrade eventually, you're wrong. When Win95 came out, people said that adoption would be slow... and then when Win98 came out... and so on. How many people are running Win95 today?)
    • I think the tin-foil is affecting your brain.

      First of all the DRM coming to Office is not manditory, its a choice the user can make. Secondly MS adoption is being hampered by their own products. There are plenty of corporate environments still using Office 97, NT 4 and Windows 98 if not for anything but the simple reason that it takes time to do large roll-outs. While new machines come with XP there wasn't the mass-exodis to it like MS hoped for, and in Servers most people are just now making it up to Win2
    • This story, published on SlashDot less than 24 hours ago, notes that interoperating with the next version of the Word format may soon be a DMCA violation due to design decisions being made by MS (i.e. using DRM "features" in the format itself).

      Take off your tinfoil hat. The DRM feature is not a part of the file format itself. It's a feature in Office that you can turn on when you save a document, so that you can secure it for other people in your company only to read it! It's not even on by default.

      W
  • by DrSkwid ( 118965 ) on Wednesday September 03, 2003 @07:09AM (#6857483) Journal
    Random documents on the net do not necessarily correspond to documents used internally.

    It would be interesting to see how the non-MS products coped with semi-embedded documents which are references to network shares.

    Office isn't 4 disparate applications it is an application framework that happens to have some pre-configured applications.

    There might be an application you know as Word but it is quite happy to live as an ActiveX control instatiated in your IIS Application.

    I used to use it as a report generator, fill in some web forms and out spits the documentation.

    The ability to open every word document on the planet is only part of the journey.

    Sad but troo.

  • by Halvard ( 102061 ) on Wednesday September 03, 2003 @07:31AM (#6857547)

    What would have made the article truly compelling would have been to also have compared things like Wordperfect and even MS Office itself. I haven't seen quite the same comparison of word processors or office suites in years, like 6 or 7. If Star Office and Open Office meet or exceed the compatibility of the commercial alternatives, that's a huge step.

    Many businesses are petrified to move from MS Office and Windows but won't look for themselves at alternatives. They believe what they see in print and a comparison like that includes other commercial suites as well as MS Office would be very compelling. Most of you have heard things like "well, PC Magazine says if I snort onions through my none, Windows won't crash as much" and they just believe it and might even do it because they read it somewhere.

    I don't think MS Office would achieve a 100 in any category either. Just from the font issues that crop up, formating issues, use by one person of a feature that another doesn't have installed, etc., would keep it down to 97-99 range also most likely. But it needs to be seen in print.

  • by mijok ( 603178 ) on Wednesday September 03, 2003 @07:31AM (#6857548)
    TextMaker [softmaker.de] promises "to seamlessly read and write Microsoft Word documents" [softmaker.de] but I haven't heard anybody's experiences with it. Has anybody here tried it?
  • by Max von H. ( 19283 ) on Wednesday September 03, 2003 @07:36AM (#6857565)
    I have successfuly deployed OpenOffice at several of my clients' and they seldom complain about having problems with MS Office files. A little training did the trick and they're very happy with it now. Furthermore, it seems their contacts (who use MS) have less trouble (if at all) opening .doc or .xls files produced by OpenOffice than ones made with various versions of MS Office.

    Now, we just need to squash a few annoying bugs (like the print preview in the spreadsheet module, still not fixed in 1.1rc3), make a native OS X build and we got a free, open-source, efficient cross-platform office suite that works, no matter the OS it's running on, with a consistent UI. Hey, Netscape got popular back in the days also because it was available on all platforms...

    Furthermore, the openoffice file format is so easy and straightforward (just zipped XML) it could just become the ideal ubiquitous file format we're looking for. Btw, I wonder why no other open-source office application can read and/or write it. Shouldn't be hard writing an import/export filter...

    Just my 2 cents there...
  • by unfortunateson ( 527551 ) on Wednesday September 03, 2003 @08:05AM (#6857656) Journal
    Macro code and applications targeted to the platform are a major impediment to moving from MS Office. It seems obvious that you need it in Excel -- after all, it's just extending the spreadsheet formulas, but while there's only a few macros/apps we've created in PowerPoint, automation of Word is almost a neccessity.

    The number of Word features we change, replace or enhance is enormous: "Wizards" to guide creation of tables with their captions, startup items to ensure option settings, repair commands to fix things when you've messed up your own document, etc. etc.

    Without at least source compatability with VBA and the object models, moving to any other platform would be a tremendous undertaking. We did it 8 years ago from WP to Word '95 (and to a lesser extent from Word '95 to Word 2000 four years ago), and we don't want to start from scratch.
  • by *weasel ( 174362 ) on Wednesday September 03, 2003 @08:27AM (#6857810)
    why wouldn't you upgrade? office 2003 will let you save and load xml formatted documents. they're even publishing their schema.

    whitepaper [ftponline.com]

    i've used the betas, i've seen it work. it's not a proprietary binary stream wrapped in xml headers - it's a fully ascii, 100% fidelity xml represented word document. with schema.

    the binary formats always change every major version. it's doubtfully due simply to malice, it's more likely due to increased business pressure to cram more features in.

    but all that aside, compatibility is the primary reason to upgrade to 2003.
  • by EmagGeek ( 574360 ) on Wednesday September 03, 2003 @09:10AM (#6858064) Journal
    Okay, I posted this in the other story about this, but here it goes again....

    OFFICE 2003 DOES NOT BLOCK ACCESS FROM OPENOFFICE UNLESS THE USER TELLS IT TO!!!!

    FFS, RTFA next time, people! Not only does the user have to tell Office2k3 to implement DRM and jumble the format, but there has to be a Win2k3 server on the network running the DRM manager application.

    In order to use IRM (Information Rights Management), according to the article, the customer has to spend boatloads of money.

    This feature is not about closing off office applications. It's about protecting IP and controlling access. M$ isn't selling O2K3 on the basis of "Hey, it's not compatible with other applications and that's why you should buy it!" They're selling it on "Hey, you can control who gets to read, print, and modify your documents, and that's why you should buy it!"

    It has nothing to do with OSS, FOSS, Slashdot, or anything else. It's just a feature they want to sell to the intellectually paranoid at an extremely high price.

    For the second time, there is nothing to see here, MOVE ALONG...
  • by YinYang69 ( 560918 ) on Wednesday September 03, 2003 @09:29AM (#6858183)
    Something which I think would go a long way to murder MS Office and speed adoption in commercial organizations would be the beginning/progression of a server-side office. Not in the vein of an Exchange replacement, but a bit more fundamental, keying toward interoperability. It would be nice, because I haven't seen any open-source applications that do this, to reduce the Save As functionality in Open Office to a series of command line tools or a good API which would take any arbitrary form of data (XML, YAML, text, etc.) and convert the data to an Office-usable format (doc, xls, etc.)

    It would then be desirable to be able to use this as part of my Perl, PHP, C, Java, and Python programs which I have to run a lot at work. That way I can, for instance, write custom forms to input timesheets, generate the timesheets on the fly as *.xls, store them to disk, send them via email, and generally decrease the amount of time it takes to get common clerical tasks completed for the employees, and (hopefully) they'd better spend the 5-10 minutes a week we saved by... I dunno... working.

    If there's any tools out there that do this already, and I've just missed the boat (or several), I'd love to know. But if there's nothing out there, I'd love to do it myself. It's the doing that gives me pause. ;)

  • by twoslice ( 457793 ) on Wednesday September 03, 2003 @09:41AM (#6858260)
    The competition should have scored major bonus points for not using clippy! [microsoft.com] That annoying little Fscker!
  • by hndrcks ( 39873 ) on Wednesday September 03, 2003 @10:24AM (#6858608) Homepage
    For small and mid-size businesses,the key is the brain-dead quick-learning-curve personal database with good reporting capabilites. Once OOO has an Access killer, it will be unstoppable. People will work around the file format issues.

    The OOO data design tools that allow you to work with MySQL and PostgresSQL via unixODBC are a start, but still too difficult for the average Joe.

  • Get this... (Score:4, Interesting)

    by duncanatlk ( 643480 ) on Wednesday September 03, 2003 @10:34AM (#6858711)
    A user here just complained they couldn't open a Excel spreadsheet. I couldn't open it either - no error message - just a new blank workbook. I suspected file corruption, but could see the data with a Hex editor. So I tried to open it with OpenOffice 1.0.1. Voila! Resaved from OO in Excel format and the document is now usable again.

You knew the job was dangerous when you took it, Fred. -- Superchicken

Working...