Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Google Cloud Microsoft News

Google Docs Ditching Old Microsoft Export Formats On Oct. 1 199

An anonymous reader writes "Google today announced a huge change for Google Apps, including its Business, Education, and Government editions. As of October 1, users will no longer have the ability to download documents, spreadsheets, and presentations in old Microsoft Office formats (.doc, .xls, .ppt)." The perils of cloud computing; LibreOffice will probably be the best conversion utility at that point. Apropos: Reader akumpf writes with an essay about the dangers of letting our data and our tools be hosted by the same provider.
This discussion has been archived. No new comments can be posted.

Google Docs Ditching Old Microsoft Export Formats On Oct. 1

Comments Filter:
  • by Anonymous Coward on Wednesday September 26, 2012 @03:49PM (#41469187)

    is now gone. We used it at work because so many of our customers could read what we created. By requiring the strange .XML.ZIP format from Microsoft that isn't widely supported, we, like most people, will have to switch to another product if we want other people to be able to open our documents.

    • by Jeng ( 926980 ) on Wednesday September 26, 2012 @03:55PM (#41469251)

      If I read the article correctly you can still create documents in MS Office formats, you just can't download them in those formats. So your customers will still be able to open the files you send them, but you may not be able to open the documents they send you.

      this means that the search giant will still support exporting into these Microsoft formats: Word (.docx), Excel (.xlsx), and PowerPoint (.pptx).

      • It wasn't really clear in the short article, but I didn't see anything that indicated reading .doc, etc. files was unsupported. You just can't "save as .doc" something you create. If a client sends you a .doc, you can still read it, but whatever reply or edits you craft for them would have to saved in another format. I'm not a Docs user, though, so I don't know for sure.

        • by Pieroxy ( 222434 )

          It wasn't really clear in the short article

          Do you mean to say Slashdot's summary? If so, you are correct. Is it rarely clear but often plain misleading or even just wrong.

      • by jimicus ( 737525 ) on Thursday September 27, 2012 @03:24AM (#41475215)

        Have you ever used Google Docs?

        There is no such concept as "create documents in MS Office formats" in Google Docs; your sentence doesn't make any sense. You create a document or a spreadsheet, give it a name and that's it - exactly how or where it's saved isn't something you as the user worry about.

        It only becomes necessary to worry about it when you need to get the document out of Google Docs and give it to someone else.

        This isn't necessarily the end of the world because, as Google have pointed out, there is a compatibility pack available from Microsoft which allows older versions of Office to open .docx files.

        There is, however, one minor issue which appears to have entirely gone over Google's head. The only time anyone's likely to use this export facility is when you're sending the document to someone outside your company and whose computers you have precisely zero control or influence over. If they don't have the compatibility pack installed, the generally accepted polite thing to do is re-send in a format they can open. It is not to ask to speak to their IT department and tell those guys how to do their job.

    • Your customers will still be able to read the old .doc files, they just won't be able to export the files from Google Docs as .doc files.
    • Interestingly, MS office has been implemented as a online service, in javascript, that runs in the browser. If you have any MS-network email accounts you can use it. It will probably be the best conversion solution, for the time being at least. LibreOffice would be a second choice, but it doesn't always convert properly.
      • by Pieroxy ( 222434 ) on Wednesday September 26, 2012 @04:34PM (#41469825) Homepage

        MS Office in JAVASCRIPT? Holy cow, I need to see that.

        Wait... Are you sure there's not a few million lines of C# running on the server as well?

        • finger slipped while trying to mod up, accidently marked as redundant. My appologies.

        • As sardonic as your reply appears to be, it is available, and it works surprisingly well - if you need MS Office that is.
          • by Pieroxy ( 222434 )

            So you're telling me there is a version of MS Office I can run in my browser offline? Please point me to it.

            BTW, I have no clue what sardonic means. Did you mean sarcastic?

      • would that not make microsoft office even more easy to pirate by simply copying all of the scripts and saving them locally? I'm pretty sure it is a lot more then just javascript running on their the front end may be written in javascript bu the work is being done deep in the bowls of a microsoft server farm somewhere.

        • It's up and running. I bet just running it and hitting F12 will start to answer those types of questions. The point is, it's available as a web-based application, and they've integrated it with document sharing for collaborative editing - just like google docs - except it's office. For people who (think they need to) use ms office, it's great.
    • by JDG1980 ( 2438906 ) on Wednesday September 26, 2012 @04:04PM (#41469401)

      We used it at work because so many of our customers could read what we created. By requiring the strange .XML.ZIP format from Microsoft that isn't widely supported, we, like most people, will have to switch to another product if we want other people to be able to open our documents.

      Are you or your customers still running Office 97?

      Every version of MS Office from 2000 onward supports the new XML formats if the Compatibility Pack [microsoft.com] is installed. And if you've been interacting with anyone who uses Office 2007 or above, you will probably already have been receiving documents in these formats, since that is what newer versions of Office default to when you save.

      • by Anonymous Coward on Wednesday September 26, 2012 @04:23PM (#41469677)

        I chose to use Google Docs, because it allowed at a team of us to all view and edit the same spreadsheet at the same time.

        Then I wrote some Python and Perl software to automatically download the .XLS file and generate calendars based on it.

        It took about a day to rewrite the programs to work with the .XLSX format -- I had to do it about two weeks ago, when Google suddenly stopped allowing us to download .XLS files.

        I wish they'd continue to support .XLS files, because there are Perl modules for both reading and writing them, while there are Perl modules for only reading .XLSX files.

        I also wish Google had announced this change before they made it! I had to scramble over the weekend when they broke our system.

        • by h4rr4r ( 612664 )

          You can still import xls, and ssconvert will convert xls to xlsx just fine.

        • by xaxa ( 988988 )

          Are there not Perl/Python libraries for working with OpenDocument ODS spreadsheets? That would have been a much better choice, rather than relying on a proprietary format.

      • by obarthelemy ( 160321 ) on Wednesday September 26, 2012 @04:29PM (#41469733)

        Many people still use the old formats, if only because they already have lots of documents in those formats. Also because there's not much reason to change, and there are always outliers that won't handle the new formats well.

        • by anubi ( 640541 ) on Wednesday September 26, 2012 @06:42PM (#41471217) Journal
          Thanks. That is the first thing I thought too when I saw this topic under discussion.

          I have been working in electronic design for many years, I started out in CAD with "Futurenet" schematic capture and PADS for PCB layout. Both ran under DOS on 386 machines ( actually the Futurenet would run on a '286 ). I had SPICE analog circuit simulators which also ran on a '286.

          I still use these programs today. They are almost thirty years old. So far, I have been able to migrate them to run on the hardware I have.

          A couple of months ago, I had a customer I did a design for ten years ago tell me the ADC on the board I had designed for him was no longer available, and could I re-do it to use something else? The files were still on my machine and came right up. It did not take me long to completely redesign the layout to make him a highly upgraded board with the latest parts on it, yet still be completely fit and form compatible with the existing sockets of his product. Thank goodness the PCB house still honors old Gerber formats, and I can still print my schematics off with the old AutoCad .DXF.

          This was exactly the thing I groused a lot about when working in the aerospace industry when we constantly ditched what we had always chasing the latest thing. What happens when existing product in the field needs support? And how long do we expect product in the field to last? If our product only lasts a year or so, go ahead and design with tools that are only viable for a few months or so... but if we are designing a product that should last a hundred years, we better use tools and record-keeping instruments that will also be usable a hundred years from now. For hundreds of years, paper and ink worked fine as a storage medium. I can't say the same for digital storage - The physical media: optical CDROMS and flash drive, may make it through - especially if we have redundant file integrity and backup systems in place - but will we have the capability to read it with all the proprietary file formats, encryption, and IP law? Anything much beyond the standard public filetypes ( i.e. .TXT ), may go the way of ancient languages without even the benefit of a rosetta stone.

          Well, I guess I am about a quarter-way into my design of a 100 year support capability. I am quite confident my CAD system will last longer than I will, if anyone else sees fit to maintain it.

          The stuff I did for the Government during that same time frame is inaccessible, as the old CAD tools are now gone. I would have no idea how to resurrect the diagrams to those old RF modems that were done in the old special hardware machines. I guess it was a fortunate thing for me that when they "cleaned house", it was not only people like me that went, our old tools went too - and these were the old ones that would run under anything we could boot up into DOS.

          I was able to buy the CAD system I had used for five years at the company surplus store. The software has went from running on a '286, to '386, to '486, then Pentium, and now runs in a DOS box.... I figure that no matter how sophisticated our processors get, there will always be some DOS emulator floating around, just as no matter how sophisticated our technology becomes, I should always be able to find a pencil and pad of paper - because sometimes that's exactly what you need.

          ( Oh, incidentally, I'll run Eagle too. )
      • by mystikkman ( 1487801 ) on Wednesday September 26, 2012 @04:35PM (#41469835)

        Every version of MS Office from 2000 onward supports the new XML formats if the Compatibility Pack [microsoft.com] is installed

        Customers send doc files and expect you to read them since almost everyone else uses Office. Sending a reply back to your clients or people at other companies saying, "Hey, install this addon and send it back in DOCX format" will only make *you* seem to be incompetent and a waster of time compared to your competition using MS Office.

        You can convert the doc and xls files locally, but isn't the whole point of using Google Apps to avoid having to have a copy of Microsoft Office? If you need to purchase a copy of Office to read the old formats anyway, you might as well not go the Google Apps route at all.

        • Only isn't what's happening at all. You can read still the .doc they send you without any issues. You can even create a .doc on your computer and upload it to Docs and send it to someone. You just won't be able to take a file on Docs and then save it to your computer as a .doc which admittedly there are uses for but they're definitely a minority.
      • No everyone has compatibility packs installed. Even if one of my customers does not have it (or one of the key people in the organization do not have it), I have to stick with older formats.
         
        Hell, there is even a compatibility pack available for ODF file formats. Do you go ahead and assume everybody has it installed?

        • by mspohr ( 589790 )

          Do you mean that your customers can't read any docx or xlsx files they receive from anyone?
          I really find that hard to believe. For at least the last 5 years, everyone has been sending around these new file formats... your customers must be flying blind...

      • by mabhatter654 ( 561290 ) on Wednesday September 26, 2012 @04:51PM (#41470043)

        But many places use the docs with VB6. THAT is the problem. First, these are HUGE systems that automatically accept .doc files. Second, after VB6 Microsoft's tools went .net and working with the office formats got a lot harder... You're talking 90% rewrite.... Or buy into the mess that's Sharepoint and hope you can hire somebody to make that work.

        If somebody spun up a Distro with WINE at XP level, DOC and VB6 compatibility some companies would eat that up.

        • ??

          What?

          Document formats have precisely nothing to do with Visual Basic versions. Zero. If you're referring to reading and writing office formats by applications written in Visual Basic, they don't have any built in support for that at all - it's all third party code.

      • Are you or your customers still running Office 97?

        I'm using Ubuntu Oneric w/ Libre Office 3.4.4 (which is what was distributed with it). I'm in the middle of a distance learning course so there's no way I'm about to upgrade right now.

        I discovered, when attempting to modify a critical document, that this version of Libre Office could import it, edit it, and write it out. Once. But if I tried to import the modified document for another edit, Libre Office would hang. I worked around by converting the docum

    • Considering that you can still put microsoft docs into google docs, this isn't a change. They're just not sending it back out into those formats - which also means converting documents which weren't microsoft docs, into microsoft docs. The issue here is relying on Microsoft products, not a fault of google's.

      • by obarthelemy ( 160321 ) on Wednesday September 26, 2012 @04:30PM (#41469755)

        Indeed. Only that won't change because Google decide overnight to change the filters they support. What is changing is the trust we can have in online providers not swiping the carpet from under our feet overnight. See my .sig.

        • by icebike ( 68054 ) *

          Very Valid point.
          If I was paying for this, I'd be pretty upset. (I am paying for it, just not with money).

          The filters were in-hand already, and there was little point in dropping them.
          Warn agains incompatibilities where necessary, but why drop them all together.?

          They can still import these old formats, but can no longer turn around and export them in the same format.

          That might make sense if they were adding a ton of functionality to documents in Google Docs, but it has always
          seemed to me to be a pretty limi

    • ever heard of PDF?

    • by fm6 ( 162816 )

      What, none of your customers can read .docx, .xlsx, or .pptx? These have been the default since Office 2007. And earlier versions (back to Office 2000) can handle them with a simple filter upgrade.

    • Keep copies of your old software. I needed to recover some family history letters that was saved in Microsoft Works format for Windows 3.1 that was on floppy. To recover them, I built a Win 3.1 machine to run Star Office (legal copy saved with book and box) so I opened the files in Star Office with the import function to save formatting and then saved them in MS Word 97 format. From there I could transfer them off floppies. (Win3.1 does not support USB) Keep some older hardware handy.

      With the software c

  • And (Score:5, Interesting)

    by M0j0_j0j0 ( 1250800 ) on Wednesday September 26, 2012 @03:50PM (#41469205)

    This is the reason i didn't pick google for my business, what about the customers that have processes that rely on that functionality?

    • Re:And (Score:4, Insightful)

      by ThorGod ( 456163 ) on Wednesday September 26, 2012 @03:53PM (#41469229) Journal

      Yep! This just doesn't make sense. Google continues to be *the example* against anything and all things "cloud".

      • Never before have there been forced upgrades or features dropped from applications! Outrage!

        • Re:And (Score:5, Insightful)

          by M0j0_j0j0 ( 1250800 ) on Wednesday September 26, 2012 @04:06PM (#41469441)

          The problem is not the drop, is the time-frame. like i wrote below

          The problem is they announce a functionality drop 1st October on the 26th of September.

        • i think people would say the difference is that you aren't forced to upgrade a local app, but google docs can just change over night. there's no option to not upgrade.

        • Forcing updates is bad enough
          Dropping features is bad enough
          Combining the two is horrible behaviour

        • The problem is not that they are dropping a feature.. that's fine. The problem is the time frame. Here's the announcement on 9/25 announcing the change:
          http://googleappsupdates.blogspot.ca/2012/09/scheduled-release-track-features-update_26.html [blogspot.ca]

          They gave people 6 fucking days to fix any processes that rely on that functionality.

          I don't care that they have dropped support for it. But 6 days?!

          You really don't see a problem with that?

          • Sorry.. I got that wrong.. They scheduled it on 9/25, but then sat on their hands before actually making the announcement on 9/26. So make that 5 days.

            Too fucking lazy to give people a 6th day.

        • Never before have there been forced upgrades or features dropped from applications! Outrage!

          Yeah but at least in non-cloud environments you can keep running the software as-is.

        • by jimicus ( 737525 )

          It's actually remarkably rare.

          There are upgrades that rapidly become difficult to live without (eg. when Microsoft were changing their file format subtly with every version of Office up to '97), there are upgrades that you'd be well advised not to ignore (eg. when an old piece of software is a piece of chicken wire security wise and the developers decide they're not going to patch any more holes that show up in it), there are vertical markets where they don't force you to upgrade but they jack up the price

      • by geek ( 5680 )

        I know right? It's not like there is a free compatibility [microsoft.com] pack or anything

    • Re:And (Score:4, Interesting)

      by Capt.DrumkenBum ( 1173011 ) on Wednesday September 26, 2012 @04:41PM (#41469931)
      I have been saying for years that any company that runs their business on Google apps will end up either out of business, or as a division of Google.
      Any company that relies on an online office tool is not a company I will be dealing with.

      All this cloud crap is just the return of the mainframe.
      Remember when Sun advertized "The network is the computer."? Well, it wasn't then, it isn't now, and I doubt it will be in the future.
      • All this cloud crap is just the return of the mainframe.

        No, it's not. With a mainframe, it's your data on your disks attached to your mainframe managed by your software.

        In the cloud, it's your data on their servers, sometimes managed by their software, according to their Terms of Service and mined for their benefit.

        Not remotely close.

  • No need really (Score:5, Insightful)

    by goldgin ( 1218596 ) on Wednesday September 26, 2012 @03:54PM (#41469237)
    I make it a habit of installing the free compatibility pack on my office 2003 installations to open docx and similar "new gen" documents. Works like a charm on the majority of documents.
    • I am glad that it works "like a charm" for you on "the majority" of documents. Could you tell us what, exactly, it does for you on the minority?

      I downloaded the no-cost XML converter from Microsoft for my Mac some years ago, for the excellent reason that they hadn't produced a version of Word that supported .docx yet. My experience was that at least half the time, it would run for many minutes trying to convert a document and then crash. These were not long documents, and I was never able to characterize wh

  • Who cares? (Score:2, Informative)

    by rashire ( 1222070 )
    Am I the only one who found this post misleading. TFA specifically states .xlsx .docx .pptx etc are all still going to be available. Thus whats the big deal. See no issue dropping a format that was replaced over 5 years ago
    • Clickbait, in its more raw form. Worse, people voted it up to get here in the first place.

    • I save all my Office documents in the old format - .doc, .ppt, .xls. I do that for two reasons: backwards compatibility, which matters to some of my colleagues and international collaborators, and compatibility with the version of Office I have at home.

      I guess there are more people like me, that need to cooperate with people around the world, and cannot expect that everyone has paid the Microsoft tax recently.

      • by thsths ( 31372 )

        > I save all my Office documents in the old format - .doc, .ppt, .xls. I do that for two reasons: backwards compatibility, which matters to some of my colleagues and international collaborators, and compatibility with the version of Office I have at home.

        You can get converters for all supported Office versions. And obviously you should not run an unsupported Office version if you exchange documents.

        LibreOffice may be a better reason: it is ok with the old document format up to a point, but it really stru

  • by dkleinsc ( 563838 ) on Wednesday September 26, 2012 @03:56PM (#41469273) Homepage

    You never, ever, lose a feature. At worst, the feature requires you to keep a really old version of a package around.

  • by jandrese ( 485 ) <kensama@vt.edu> on Wednesday September 26, 2012 @03:58PM (#41469313) Homepage Journal
    Was it expensive to maintain this functionality? It seems like the .doc format shouldn't be changing much these days, making it fairly cheap to keep around. Was the difficulty that Google is adding a bunch of features that aren't supported by those formats (doesn't seem likely?). Did they have to pay a licensing fee to Microsoft to use them? There must be a reason to remove them, simply deleting them because they're old doesn't make much sense, especially if people are still using them.
    • by JDG1980 ( 2438906 ) on Wednesday September 26, 2012 @04:09PM (#41469465)

      Was it expensive to maintain this functionality? It seems like the .doc format shouldn't be changing much these days, making it fairly cheap to keep around. Was the difficulty that Google is adding a bunch of features that aren't supported by those formats (doesn't seem likely?). Did they have to pay a licensing fee to Microsoft to use them? There must be a reason to remove them, simply deleting them because they're old doesn't make much sense, especially if people are still using them.

      I don't think there's a license fee. If there was, MS would have tried to go after the open-source implementations at some point in the past. In fact, I believe that a couple years ago, the European Union required MS to release documentation on their legacy binary Office formats to the public.

      What this is about, I suspect, is QA costs. Having these export formats means that every time substantial changes are made, the legacy export features must be tested. And they have to be tested with a substantial variety of documents to make sure nothing breaks, if Google wants to provide a solid experience. (Businesses would be very unhappy if they exported a PPT and the slides were all messed up because, say, one particular type of vector image wasn't properly ported back to legacy mode.) So Google can't just leave it in, since it might break at any time in the future, and as long as it stays in, it will suck up time and effort that could be spent on more important things. They decided that with everything from Office 2000 on up supporting the XML formats, it was time to pull the plug on legacy export. (Legacy import, AFAIK, should continue unaffected.)

    • by MobileTatsu-NJG ( 946591 ) on Wednesday September 26, 2012 @04:13PM (#41469539)

      Was it expensive to maintain this functionality? It seems like the .doc format shouldn't be changing much these days, making it fairly cheap to keep around.

      Funny, this is the second time this week I've heard this question about Google. The answer is: Every time somebody makes a change to Docs, they have to test this format. Expensive? Who knows, but it is a cost.

      The real question is: Why is Google running around doing all this cost cutting?

  • Why? (Score:5, Interesting)

    by lilfields ( 961485 ) on Wednesday September 26, 2012 @03:58PM (#41469317) Homepage
    Is Google intentionally trying to get out of the Office business? Because this is a quick way out. Though I use Office 2013 beta, I still save documents in .doc often because a LOT of people save in the format for backwards compatibility. Then what about existing customers that have to have this function? What a stupid move. Apple botches maps and Nano, Google botches Office, Microsoft might have botched an OS. At least Apple and Microsoft can recover the business. Office software is a tough playing field with Microsoft's behemoth.
  • Google Docs is only dropping support for old formats (Office 97-2007). Old applications that haven't been patched in how long? No reasonable business that requires documents should still be running on those old versions anyways. You can only keep backwards compatibility for so long before things start to get bloated and buggy.

    • The problem is they announce a functionality drop 1st October on the 26th of September.

    • Office 2003, the last version that used .doc as the native format, will have extended support (security fixes) through till April 8, 2014.

  • by Qwavel ( 733416 ) on Wednesday September 26, 2012 @04:00PM (#41469345)

    A clarification has been posted: it is the Office 97-2003 (not 2003-2007) formats that are being dumped, and it is

    Gotta say, though, that Google takes as much care with their blog posts as they do with their products: everything is beta.

    Would be interested to know what the rationale is. Did they have to pay a licensing fee for these old proprietary formats? Or did they just want to stop supporting rather old, very proprietary formats of their competitor?

    Note that they also recently announced that they are dropping IE8 support soon, so they are generally being very ruthless about culling out technologies. I guess I can forgive them that - supporting lots of old MS technologies must be painful.

  • by RazorSharp ( 1418697 ) on Wednesday September 26, 2012 @04:16PM (#41469575)

    Now that MS Word utilizes OpenDocument, perhaps it can now begin to replace the .doc/.docx formats. I'm not really sure how many people use Google docs (I've heard quite a few do, I don't know how they do it), but if they have a sizable chunk of users it could work like the reverse of Microsoft's formats in the past. "Save that in .odt because everything reads .odt."

    It's kind of risky on Google's part, but if they succeed they'll break Microsoft's key stranglehold on the whole text editing market. Let's face it, it's ridiculous that such a basic piece of software as MS Office not only sells at the outrageous price they have it at, but is also considered mandatory by most computer users who use their computer for actual work.

    LibreOffice and its derivatives are bound to win eventually (it keeps improving and will always be free), but the process is extremely slow. It's nice to see Google attempt to cut off Word's life support, which is format lock. LibreOffice Writer is at the point where it could make Word irrelevant - LibreOffice just won't bury the Office suite until Calc catches up with Excel.

    • by jon3k ( 691256 )
      Google is just discontinuing exporting to XLS, DOC, etc (2003/XP and prior format). They still support exporting to XLSX/DOCX.
    • by clodney ( 778910 )

      It's kind of risky on Google's part, but if they succeed they'll break Microsoft's key stranglehold on the whole text editing market. Let's face it, it's ridiculous that such a basic piece of software as MS Office not only sells at the outrageous price they have it at, but is also considered mandatory by most computer users who use their computer for actual work.

      Reducing Office suites to text editing is ridiculous. For most people in an office setting, Word, Excel and PowerPoint are utterly core technologies, and spending a few hundred dollars per seat is a complete non-factor for any medium to large business.

      If Unix ran MS-Office, I that many businesses would find it easier to switch away from Windows but still keep Office.

  • As someone who follows corporate strategy a bit and who is enjoying watching Apple, Google, and to a lesser extent Microsoft slug it out, this is a move that makes sense. And I love to see anything that reduces the intoxication people have with Microsoft formats. Dependence on compatibility with Microsoft formats has set computing back by a decade - and the fight continues.

    On the other hand, as a consumer and someone who's very wary of getting locked in, I've gotta say, that's a Dick Move. (http://dicta [dictatorshandbook.net]

  • Peril (Score:2, Insightful)

    by fm6 ( 162816 )

    Not a peril of cloud computing. This is a peril of outsourced cloud-based applications. That leaves you at the mercy of the outsourcee. If you manage the cloud application yourself (license it and deploy it on your own private or public cloud) you still control it.

    Anyway, what's the big deal? Why would somebody on Google Docs need to import or export a .doc file? The .docx format has been the default since Word 2007, and MS provides filters for this format for all versions of Word back to Word 2000. So if y

  • So they announce on the 25th of September that they will kill exporting to $OLDFORMAT in the 1st of October?
    No matter what you think of the format as such, that is going to blindside a few users. I think changes like that should be announced at least two months ago, not five days.

  • The way I read the google decision, you can still import files in .doc format. Only you can't save it in the older version of the doc format. I am not sure what the older version is, pre 1997 or pre 2003.
  • When you use google doc or an online doc tool, importing documents would be called "uploading". The file on your disk is uploaded into google doc. Once it is in google, doc you could keep it in google doc format in the cloud. Or at some point you want to export it back to your disk. That will be downloading. Google is removing the ability to export google docs to pre 2003 (or pre1997 not very clear) versions of the doc file format. You can continue to import/upload doc files into google docs. The ability to
  • If I have people who do not have docx, xlsx, etc support, I just grant them read only access to the online doc.

    Everyone else can read the newer formats with whatever Office package environment they are in.

    Nonissue for me and my kin

  • I hate to say it. I ever have a certification in Google Apps. But Google the quality, and features, or everything except gmail, is just awful, and keeps getting worse.

"An idealist is one who, on noticing that a rose smells better than a cabbage, concludes that it will also make better soup." - H.L. Mencken

Working...