Group items tagged

The king of clicks returns!  No doubt there was a time when the mere mention of ODF and the now legendary XML "document" format wars with Microsoft could drive click counts into the statisphere.  Sorry to say though, those times are long gone. It's still a good story though.  Even if the fate of mankind and the future of the Internet no longer hinges on the outcome.  There is that question that continues defy answer; "Did Microsoft win or lose?"  So the mere announcement of supported formats in MSOffice XX is guaranteed to rev the clicks somewhat. Veteran ODF clickmeister SVN does make an interesting observation though: "The ironic thing is that, while this was as hotly debated am issue in the mid-2000s as are mobile patents and cloud implementation is today, this news was barely noticed. That's a mistake. Updegrove points out, "document interoperability and vendor neutrality matter more now than ever before as paper archives disappear and literally all of human knowledge is entrusted to electronic storage." He concluded, "Only if documents can be easily exchanged and reliably accessed on an ongoing basis will competition in the present be preserved, and the availability of knowledge down through the ages be assured. Without robust, universally adopted document formats, both of those goals will be impossible to attain." Updegrove's right of course. Don't believe me? Go into your office's archives and try to bring up documents your wrote in the 90s in WordPerfect or papers your staff created in the 80s with WordStar. If you don't want to lose your institutional memory, open document standards support is more important than ever. "....................................... Sorry but Updegrove is wrong.  Woefully wrong. The Web is the future.  Sure interoperability matters, but only as far as the Web and the future of Cloud Computing is concerned.  Sadly neither ODF or Open XML are Web ready.  The language of the Web is famously HTML, now HTML5+

Finally! Someone who gets it. For an office suite to be considered as an alternative to MSOffice, it must be designed with multiple levels of compatibility. It's not just that the "feature sets" that must be comparable. The guts of the suite must be compatible at both the file format level, and the environment level. Randall put's it this way; "It's the ecosystem stupid". The reason ODF failed in Massachusetts is that neither OpenOffice nor OpenOffice ODF are designed to be compatible with legacy and existing MSOffice applications, binary formats, and, the MSOffice productivity environment. Instead, OOo and OOo-ODF are designed to be competitively comparable. As an alternative to MSOffice, OpenOffice and OpenOffice ODF cannot fit into existing MSOffice workgroups and producitivity environments. Because it s was not designed to be compatible, OOo demands that the environment be replaced, rebuilt and re-engineered. Making OOo and OOo-ODF costly and disruptive to critical day-to-day business processes. The lesson of Massachusetts is simple; compatibility matters. Conversion of workgroup/workflow documents from the MSOffice productivity environment to OpenOffice ODF will break those documents at two levels: fidelity and embedded "ecosystem" logic. Fidelity is what most end-users point to since that's the aspect of the document conversion they can see. However, it's what they can't see that is the show stopper. The hidden side of workgroup/workflow documents is embedded logic that includes scripts, macros, formulas, OLE, data bindings, security settings, application specific settings, and productivity environment settings. Breaks these aspects of the document, and you stop important business processes bound to the MSOffice productivity environment. There is no such thing as an OpenOffice productivity environment designed to be a compatible alternative to the MSOffice productivity environment. Another lesson from Massach

While trying to help a friend understand the issues involved with exchanging MSOffice documnets between the many different versions of MSOffice, I stumbled on this oldy but goody ......... "A group of software developers have created a program to make Microsoft Office work with files in the OpenDocument format, a move that would bridge currently incompatible desktop applications. Gary Edwards, an engineer involved in the open-source OpenOffice.org project and founder of the OpenDocument Foundation, on Thursday discussed the software plug-in on the Web site Groklaw. The new program, which has been under development for about year and finished initial testing last week, is designed to let Microsoft Office manipulate OpenDocument format (ODF) files, Edwards said. "The ODF Plugin installs on the file menu as a natural and transparent part of the 'open,' 'save,' and 'save as' sequences. As far as end users and other application add-ons are concerned, ODF Plugin renders ODF documents as if (they) were native to MS Office," according to Edwards. If the software, which is not yet available, works as described, it will be a significant twist to an ongoing contest between Microsoft and the backers of OpenDocument, a document format gaining more interest lately, particularly among governments. Microsoft will not natively support OpenDocument in Office 2007, which will come out later this year. Company executives have said that there is not sufficient demand and OpenDocument is less functional that its own Office formats. Having a third-party product to save OpenDocument files from Office could give OpenDocument-based products a bump in the marketplace, said Stephen O'Grady, a RedMonk analyst. OpenDocument is the native format for the OpenOffice open-source desktop productivity suite and is supported in others, including KOffice, Sun Microsystems' StarOffice and IBM's Workplace. "To the extent that you get people authoring documents in a format that is natively compatible with

excerpt: The trend in Office development is the migration of solutions away from in-application scripted processing toward more data-centric development. Of course this is a primary purpose of Open XML, and it is great to see the amount of activity in this area. We've seen customers scripting Word in a server environment to batch process / print documents or for other automation tasks. In reality Word isn't built to do that on a large scale, it is better to work directly against the document rather than via the application whenever possible. The Open XML SDK unlocks a "whole nuther" environment for document processing, and gets you out of the business of scripting client apps on servers to do the work of a true server application (not to mention the licensing problems created by installing Office on a server). comment:  Gray makes a very important point here.  The dominance of the desktop based MSOffice Productivity Environment was largely based the embedded logic driving "in-process" documents that was application and platform (Win32 API) specific.  Tear open any of these workgroup-workflow oriented compound documents and you find application specific scripts, macros, OLE, data bindings, security settings and other application specific settings.  These internal components are certain to break whenever these highly interactive and "live" compound documents are converted to another format, or application use.  This is how MSOffice documents and the business processes they represent become "bound" to the MSOffice Productivity Environment. What Gray is pointing to here is that Microsoft is moving the legacy Productivity Environment to an MSWeb based center where OpenXML, Silverlight, CAML, XAML and a number of other .NET-WPF technologies become the workgroup drivers.  The key applications for the MS WebStack are Exchange/SharePoint/SQL Server.  To make this move, documents had to be separated from the legacy desktop Productivity Environment settings. Note th

Interesting stats coming out from the recent Forrester study on Office Productivity.  The study was conducted by Philipp Karcher, and it shows a fcoming collision of two interesting phenomenon that cannot continue to "coexist".  Something has to give. The two phenom are the continuing dominance and use of client/server desktop productivity application anchor, MSOffice, and, the continuing push of all business productivity application to highly mobile cloud-computing platforms.   It seems we are stuck in this truly odd dichotomy where the desktop MSOffice compound document model continues to dominate business productivity processes, yet those same users are spending ever more time mobile and in the cloud.  Something has got to give. And yes, I am very concerned about the fact that neither of the native XML document formats {used by MSOffice (OXML), OpenOffice and LibreOffice (ODF)} are designed for highly mobile cloud-computing.   It's been said before, the Web is the future of computing.  And HTML5 is the language of the Web.  HTML is also the most prolific compound-document format ever.  One of the key problems for cloud-computing is the lack of HTML5 ready Office Productivity Suites that can also manage the complexities of integrating cloud-ready data streams. Sadly, when Office Productivity formats went down the rat hole of a 1995 client/server compound document model, the productivity suites went right with them.  Very sad.  But the gaping hole in cloud-computing is going to be filled.  One way or the other.

Gary Edwards's List: Compatibility matters - The lessons of Massachusetts are many. Application level "compatibility" with existing MSOffice desktops and workgroups is vital. Format level "compatibility" with the legacy of billions of binary documents is vital. And "ecosystem" compatibility with the MSOffice productivity environment.

Quick review of different sync-share-store services, starting with DropBox and ending with three Open Source services. Very interesting. Things have progressed since I last worked on the SurDocs project for Sursen. No mention in this review of file formats, conversion or viewing issues. I do know that CrocoDoc is used by near every sync-share-store service to convert documents to either pdf or html formats for viewing. No servie however has been able to hit the "native document" sweet spot. Not even SurDocs - which was the whole purpose behind the project!!! "Native Documents" means that the document is in it's native / original application format. That format is needed for the round tripping and reloading of the document. Although most sync-share-store services work with MSOffice OXML formatted documents, only Microsoft provides a true "native" format viewer (Office 365). Office 365 enables direct edit, view and collaboration on native documents. Which is an enormous advantage given that conversion of any sort is guaranteed to "break" a native document and disrupt any related business processes or round tripping need. It was here that SurDoc was to provide a break-through technology. Sadly, we're still waiting :( excerpt: The availability of cheap, easy-to-use and accessible cloud file-sharing services means users have more freedom and choice than ever before. Dropbox pioneered simplicity and ease of use, and so quickly picked up users inside the enterprise. Similar services have followed Dropbox's lead and now there are dozens, including well-known ones such as Google Drive, SkyDrive and Ubuntu One. cloud.jpg Valdis Filks , research director at analyst firm Gartner explained the appeal of cloud file-sharing services. Filks said: "Enterprise employees use Dropbox and Google because they are consumer products that are simple to use, can be purchased without officially requesting new infrastructure or budget expenditure, and can be installed qu

Odd that the reporter mentions the importance of security near the top of the article but gives that topic such short shrift in his evaluation of the services. For example, "secured by 256-bit AES encryption" is meaningless without discussing other factors such as: [i] who creates the encryption keys and on which side of the server/client divide; and [ii] the service's ability to decrypt the customer's content. Encrypt/decryt must be done on the client side using unique keys that are unknown to the service, else security is broken and if the service does business in the U.S. or any of its territories or possessions, it is subject to gagged orders to turn over the decrypted customer information. My wisdom so far is to avoid file sync services to the extent you can, boycott U.S. services until the spy agencies are encaged, and reward services that provide good security from nations with more respect for digital privacy, to give U.S.-based services an incentive to lobby *effectively* on behalf of their customer's privacy in Congress. The proof that they are not doing so is the complete absence of bills in Congress that would deal effectively with the abuse by U.S. spy agencies. From that standpoint, the Switzerland-based http://wuala.com/ file sync service is looking pretty good so far. I'm using it.

Excellent explanation and review from the Tim Anderson. I wonder how i missed this? Here is the summary statement: "..... You can also extend XAML with custom objects. The main requirement is that classes used in XAML must have a parameterless constructor. The procedure is straightforward. Define a class; make sure your application has a reference to the assembly containing the class; then add a namespace declaration for the assembly. You can then define elements in XAML that map to your class, and at runtime these will become object instances. XAML has a curious story when it comes to formatted text, especially in Silverlight. In one sense it is rather limited. XAML has no understanding of common formats such as HTML, CSS or RTF, let alone the fancy new OOXML. Silverlight developers have to interact with the browser DOM in order to display HTML." "... No escaping it: Silverlight .XAP bundle preserves the original XAML. That said, XAML with WPF actually is a document format. The full WPF has an element called FlowDocument and rich formatting capabilities. Silverlight lacks FlowDocument, but does have a TextBlock with basic formatting options via the inline object. It also supports the Glyph element. This is interesting because it is the core element in XPS, Microsoft's invented-here alternative to Adobe's PDF." ".... XPS uses a subset of XAML to describe fixed layouts. In consequence, and with some compromises, you can use Silverlight to display XPS." "..... The bottom line is that XAML is a way of programming .NET declaratively. Its more intricate features improve the mapping between XAML and .NET. The result is we have design tools like Microsoft's Expression Blend and a clean separation between UI objects and program code, which is a considerable achievement." ".... As ever there's a downside, and with Microsoft it's the classic: this is thoroughly proprietary, and the schema issues make it difficult to validate with standard XML tools." No

The free CloudON app for iPAD provides a very nice ribbon interface for viewing and editing MSOffice XML documents.  Supports important workgroup features like "change tracking", show or hide markup, make and view comments, restrict editing, and compare and combine versions.  Very cool. Lacks support for custom add-ons, templates, auto-correct settings, and other advanced features may limit the program's usefulness.  Time to do some testing.  Hope Florian catches this post :) excerpt: Support for Office XML file types, and a ribbon to boot ...... Speculation continues as to whether -- most say when -- Microsoft will release a version of Office for the iPad. (CNET blogger Zack Whittaker cites sources predicting a November arrival.) It's not like you have to wait months to create and edit Word, Excel, and PowerPoint files on your iPad. Last June I described how to use Google Docs and Google Cloud Connect to edit Word and Excel files on an iPad for free. The end of that story noted the likely arrival of iPad apps supporting Office file formats. One of the most popular of these is the $15 Quickoffice, a program that was recently acquired by Google. But before you shell out for an Office alternative, check out the free CloudOn app, which now connects to Google Drive and Box accounts as well as Dropbox accounts. Other new features in the latest release let you send files as e-mail attachments and open PDFs. (See Lance Whitney's post on the Internet & Media blog for more on the program's PDF features.) CloudOn's ribbon is a big departure from the Quickoffice interface, which look nothing like Office. (Of course, many people will prefer the clean, clutter-free look of Quickoffice.) None of the Office extras, but all the essentials: In a group setting CloudOn's lack of support for custom add-ons, templates, auto-correct settings, and other advanced features may limit the program's usefulness. Still, the word processor lets you track and accept changes, show or

For most of this decade, web developers have been suffering the shortcomings of Internet Explorer. Like 1998 limited HTML-CSS support.  And nothing for the language of the Web - HTML+ :: HTML5, CSS3, SVG/Canvas and advanced JavaScript.  That hasn't bothered Microsoft (NSDQ: MSFT) too much, because the company has historically focused on developing "real" applications that run only on Windows and don't use the browser as a platform. With the new Office web apps, many thought that Microsoft might actually have to experience the living nightmare that web app development can be. Yet the company has figured out a way to make things easier: cheat.   MIcrosof thas figured out how to provide MSOffice as Web Apps, without having to use the language of the Web: HTML+.  Instead, they use protpietary formats, protocols and interfaces to create an interesting dichotomy - a rich MS-Web, and a poor, 1998 Open-Web.

Aspose.Words Product Family Save any Document from Microsoft Word 2007 to EPUB using a Free Add-in from Aspose We are happy to announce the first release of a free add-in that allows you to convert any document opened in Microsoft Word 2007 to EPUB. To download goto http://www.aspose.com/community/files/69/free-microsoft-office-add-ins/aspose.words-for-microsoft-word/default.aspx. Below are excerpts from the user's guide that is included in the installer. Introduction Aspose.Words for Microsoft Word is a free utility that allows converting any document opened in Microsoft Word 2007 to the EPUB format. Microsoft Word 2007 can load documents in many formats including DOC, DOCX, RTF, HTML, ODT etc and you can now easily convert them all to EPUB using Aspose.Words for Microsoft Word. About the EPUB format EPUB is an XML-based distribution format for eBooks that is rapidly gaining adoption by publishers and distributors. EPUB is an open standard supported by the International Digital Publishing Forum (IDPF) organization. See also the Wikipedia article. To Save as EPUB After you install Aspose.Words for Microsoft Word, the EPUB format will be listed in the Save As dialog. Saving to EPUB is just as simple as saving to any other file format available in Microsoft Word. 1.      Open any document in Microsoft Word. 2.      From the Save As menu select "Aspose.Words - EPUB (*.epub)", and then click Save. You can save any document from Microsoft Word to EPUB using Aspose.Words for Microsoft Word.

One of the "Lessons of Massachusetts" is that the key lock-in point for Microsoft's monopoly is their iron fisted control of the productivity environment, anchored by MSOffice and the Windows local workgroup client/server system.  Key to office productivity is the compound document model that fuels every business process and business productivity system.  It's the embedded logic and database connectivity (OLE, ODBC, MAPI and COM ActiveX controls) that juice the compound document model.   Convert a compound document to another format (or PDF), and you BREAK the both the document, AND THE BUSINESS PROCESS!!!! It was the breaking of the business process that stopped Massachusetts from moving to the Open Document Format !!!! So now comes a story with consumer sales vs enterprise sales numbers that seemingly shatter the Lessons of Massachusetts.  How is that? My take is that the numbers Microsoft touts are true.  Consumers are making new purchases - NOT enterprises.  The simple truth is that, as Microsoft introduces new OS and Application Services geared to Mobile / Cloud Computing, these new systems BREAK legacy business systems.  It's still way too costly for businesses to transition to the new models. Eventually though, businesses will replace those legacy business productivity systems with Mobile / Cloud Computing systems.  And it will be a rip-out-and-replace transition; not the gradual "value-added" transition everyone hopes Microsoft will provide.   Interesting stuff. excerpt: "If Microsoft is an enterprise company, then why is it spending so much time and money on stuff like Bing, Xbox, Windows Phone, and the Surface RT? It should be going all-in on cloud computing and services. If you were to ask Microsoft's CEO Steve Ballmer, his answer would probably be: It's a dumb question, we're both. In an interview with Jason Pontin at MIT Technology Review, he said: ""Our number-one thing is supplying products to consumers. That's kind of what we do.

Note that rip-out-and-replace to get to the cloud is a very risky strategy for MSFT because the company forfeits its vendor lock-in advantage; the question for the enterprise then becomes "replace with what?" The answer in many cases will be non-Microsoft services. And traditionally, what the enterprise uses has driven what enterprise workers use at home far more than vice versa.

Excellent report on Crocodoc and their ability to convert MANY different document file types to HTML5.  Including all MSOffice formats - OOXML, ODF, and PDF. " Crocodoc, and took on the much larger problem of allowing groups to collaborate on editing a document online, no matter what the document type: PowerPoint, PDF, Word, Photoshop, JPEG, or PNG. In the process, they had to build an embeddable viewer that could take apart any document and reassemble it accurately within a Web browser. And as soon as they'd finished that, they had to tear their own system apart and rebuild it around HTML5 rather than Flash, the Adobe multimedia format that's edging closer and closer to extinction. The result of all that iterating is what's probably the world's most flexible and faithful HTML5-based document viewer: when you open a PDF, PowerPoint, or Word document in Crocodoc, the Web version looks exactly like the native version, even though it's basically been stripped down and re-rendered from scratch. When I talked with Damico in February of 2011, the startup had visions of building on this technology to become a kind of central, Web-based clearinghouse for everyone's documents-a cross between Scribd, Dropbox, and Google Docs, but with a focus on consumers, and with prettier viewing tools. In the last year, though, Crocodoc's direction has changed dramatically. Damico and his colleagues realized that it would be smarter to partner with the fastest growing providers of document-sharing services and social business-tool providers than to try to compete with them. "The massive, seismic change for us is that we had a huge opportunity to partner with Dropbox and LinkedIn and SAP and Yammer, and let them build on top of Crocodoc and make it into a core piece of their own products," Damico says. In other words, every time an office worker opens a document from within a Web app like Dropbox or Yammer, they're activating a white-label version

With Documents To Go for the Google Android platform you get read, write, create and sync support for Word and Excel 2007 (OpenXML formatted) documents, support for receiving and sending attachments through Gmail and other applications (including the free RoadSync Exchange beta client, open password protected files, and view Word documents with track changes so you can see what others have done to your document. ZDNet reviewer Mathew Miller also recommends that people check out the details of the DataViz Intact Technology to see how documents will be handled to maintain file formatting and structure throughout the process of editing. There are two YouTube Video demonstations of "Documents to Go" running on an Android. ........ No collaborative editing with MSOffice desktops, but this is outstanding stuff.

Fascinating conversation between Douglas Crockford and Jeremy Geelan. The issue is that XSS - the Cross Site Scripting capabilities of HTML. and "the painful gap" in the HTML5 specification of the itnerface between JavaScript and the browser. I had to use the Evernote Clearly Chrome extension to read this page. Microsoft is running a huge JavaScript advertisement/pointer that totally blocks the page with no way of closing or escaping. Incredible. Clearly was able to knock it out though. Nicely done! The HTML5-XSS problem is very important, especially if your someone like me that sees the HTML+ format (HTML5-CSS3-JSON-JavaScript-SVG/Canvas) as the undisputed Cloud Productivity Platform "compound document" model. The XSS discussion goes right to the heart of matter of creating an HTML compound document in much the same way that a MSOffice Productivity Compound Document worked. The XSS mimics the functionality of of embedded compound document components such as OLE, DDE, ODBC and Scripting. Crack open any client/server business document and it will be found to be loaded with these embeded components. It seems to me that any one of the Cloud Productivity Platform contenders could solve the HTML-XSS problem. I'm thinking Google Apps, Zoho, SalesForce.com, RackSpace and Amazon - with gApps and Zoho clearly leading the charge. Also let me add that RSS and XMP (Jabber), while not normally mentioned with JSON, ought to be considered. Twitter uses RSS to transport and connect data. Jabber is of course a long time favorite of mine. excerpt: The fundamental mistake in HTML5 was one of prioritization. It should have tackled the browser's most important problem first. Once the platform was secured, then shiny new features could be carefully added. There is much that is attractive about HTML5. But ultimately the thing that made the browser into a credible application delivery system was JavaScript, the ultimate workaround tool. There is a painful gap

Viewing and printing of documents.  Support for PDF, RTF, RTFD, iWork, MSOffice (subject to iOS compatibility), Web archives, HTML, text, source code, and standard iOS multi media.  No discussion yet as tho whether or not Avatron can support Visual fixed/flow viewing of these supported formats. Some interesting support for mounting remote file servers - cloud storage systems like DropBox, Box.net , FTP and secure HTTPS. No WebDav.   Seems to be struggling to make that cross-over from iOS device to desktop to cloud-computing connectivity.

Good article on the increasing use of HTML5 for business apps.  The focus is on mobile devices, even though HTML5 clearly targets anything capable of running a WebKit class browser.  The article also demonstrates, albeit unwittingly, the use of HTML5 as a cloud platform "Compound Document" model.  Something far more important than the comparatively limited focus of BI and CRM mobility apps.   A Cloud Producitvity Platform will replace the legacy Desktop Productivity Platform anchored on Microsoft's Windows-MSOffice workgroup networking.  Just as Compound Documents were the fuel of desktop productivity apps and services, a new breed of compound documents will fuel cloud productivity based workgroups.  The article even demonstrates the basics of embedding charts, interactive feeds, media  and database streams in HTML5 document interfaces.  Still missing real time messaging between apps, but clearly the HTML5 cloud compound document model has arrived. excerpt: HTML5 will lead to richer mobile BI and CRM apps that can be used across browsers and devices. HTML has evolved considerably since it was first mapped out by Tim Berners-Lee more than 20 years ago. Now we're up to HTML 5.0, which could have a significant effect on the business intelligence and CRM landscape.

Bingo!  Took five years, but finally someone gets it: excerpt:  Great question. After 10 years, OpenOffice hasn't had much traction in the enterprise - supported by under 10% of firms, and today it's facing more competition from online apps from Google and Zoho. I'm not counting OpenOffice completely out yet, however, since IBM has been making good progress on features with Symphony and Oracle is positioning OpenOffice for the web, desktop and mobile - a first. But barriers to OpenOffice and Web-based tools persist, and not just on a feature/function basis. Common barriers include: Third-party integration requirements. Some applications only work with Office. For example, one financial services firm I spoke with was forced to retain Office because its employees needed to work with Fiserv, a proprietary data center that is very Microsoft centric. "What was working pretty well was karate chopped." Another firm rolled out OpenOffice.org to 7,00 users and had to revert back 5,00 of them when they discovered one of the main apps they work with only supported Microsoft. User acceptance. Many firms say that they can overcome pretty much all of the technical issues but face challenges around user acceptance. One firm I spoke with went so far as to "customize" their OpenOffice solution with a Microsoft logo and told employees it was a version of Office. The implementation went smoothly. Others have said that they have met resistance from business users who didn't want Office taken off their desktop. Other strategies include providing OpenOffice to only new employees and to transition through attrition. But this can cause compatibility issues. Lack of seamless interoperability with Office. Just like third-party apps may only work with Office, many collaborative activities force use of particular versions of Office. Today's Web-based and OpenOffice solutions do not provide seamless round tripping between Office and their applications. Corel, with its

This week Microsoft will take its Office 2010 suite out of beta. If you're considering upgrading Office with Office, we'd encourage you to consider an alternative: upgrading Office with Google Docs. If you choose this path, upgrade means what it's supposed to mean: effortless, affordable, and delivering a remarkable increase in employee productivity. This is a refreshing alternative to the expensive and laborious upgrades to which IT professionals have become accustomed. Google Docs has been providing rich real-time collaboration to millions of users for nearly four years. It lets employees edit and share documents, spreadsheets, and presentations in the browser from anywhere in the world. We recently made tremendous strides in improving Google Docs formatting, speed and functionality, and a growing number of companies are now using it as their primary productivity software. Of course, you probably already own Office 2003 or 2007 (or maybe Office 2000?), and there's no need to uninstall them. Fortunately, Google Docs also makes Office 2003 and 2007 better. For example, you can store any file - including Microsoft Office documents - in Google's cloud and share them in their original format (protected, naturally by Google's synchronous replication across datacenters). Plus, in the coming months, Google will enable real-time collaboration directly in Office 2003 and 2007, as you can see here. Google Docs represents a real alternative for companies: a chance to get the collaboration features you need today and end the endless cycle of "upgrades". For more information on the choices available to you, check out the summary below. But don't take our word for it - you can try Google Docs and the rest of the Google Apps suite for free. The only thing you have to lose is a server or two.

"GroupDocs Viewer is an online document viewer that lets you read documents in your browser, regardless of whether you have the software that they were created in. You can view many types to word processing documents (DOC, DOCX, TXT, RTF, ODT), presentations (PPT, PPTX), spreadsheets (XLS, XLSX), portable files (PDF), and image files (JPG, BMP, GIF, TIFF). For each file, you get a high-fidelity rendering, showing the document just as it would if you opened it in the software it was created in. Layout and formatting is retained and you see an exact copy of the original. GroupDocs Viewer lets you really read the document. You can search text documents, copy text and even embed the document - GroupDocs Viewer and all - in a web page. You can print or download the file from GroupDocs Viewer if you need to work with it offline."