LWN.net Logo

OSV and Phase N Launch OpenOpenOffice (O3)

From:  Con Zymaris <conz-AT-cyber.com.au>
To:  lwn-AT-lwn.net
Subject:  [MEDIA RELEASE] OSV and Phase N Launch O3: Bringing Open Document Format to Microsoft Office.
Date:  Thu, 20 Oct 2005 13:40:59 +1000


- - - 

OSV and Phase N Launch O3: Bringing Open Document Format to Microsoft
Office.

Melbourne -- 20 October 2005

Open Source Victoria, Australia's government-funded open source industry
cluster, has formed an alliance with Phase N to develop an open source
solution to bring Open Document Format capabilities to Microsoft Office
users.

Called OpenOpenOffice or O3, it will allow Microsoft Office users to
read and write Open Document Format (ODF) files. ODF is the
next-generation standard for storing and interchanging office documents
such as word processor files, spreadsheets and slide-show presentations.
ODF is supported by many of the office productivity suites on the
market, including OpenOffice.org, Sun's StarOffice, Corel Office,
Abiword, KOffice and others.

"Through universal adoption, Open Document Format will bring, for the
first time in our industry's history, the reality of friction-free
interchange of office documents between different office suites," said
OSV convener Con Zymaris. "The major hold-out here is Microsoft, who
refuses to support ODF - a decision that seems based on self-serving
reasons, to protect the near-monopoly of their high-priced Office suite.
The ones who will suffer are the users."

"We believe that Microsoft Office users should have a choice as to which
format they store their documents in," continued Zymaris. "To that end, we
are partnering with software development firm Phase N to build a solution
which will indeed give Microsoft Office users that very choice that
Microsoft denies them. This is what open source is about - freedom from
the control of proprietary vendors and more options for users."

"The amazing thing about the O3 concept is how simple it is," said key
O3 developer Adam Kennedy. "Just take the Word-to-ODF filters from the
OpenOffice.org suite, and put them into Office in reverse. Microsoft has 
made it trivial to write plugins for Office using .NET, and the
OpenOffice.org team has put a huge effort into their document conversion
filters. So all that's left is to connect the two together via some
simple SOAP calls using C# and Perl, and then make sure it is easy for
people to install into Office."

"By not supporting ODF, Microsoft is placing its interests ahead of its
users, who will be barred from entering this new sphere of document
interoperability. This is another sign that the vendor cares little for
offering interoperability and choice to its customers. The open source
community equates such vendor stubbornness with damage, and much like
the Internet, we will route around it. If Microsoft won't offer choice
to its Office users, we will do it for them," concluded Zymaris.

More information on O3:

 http://www.phase-n.com/openopenoffice/


- - -

About Open Source Victoria

Open Source Victoria is an Industry Cluster consisting of over 100
Victorian firms and developers which provide services and technology
related to Free and Open Source Software (FOSS.) Open Source Victoria
offers marketing, advocacy and information referral services, and aims
to raise the profile of FOSS in Victoria and work with other similar
organisations across Australia.

http://www.osv.org.au/

Contact: Con Zymaris
Phone: 03 9621 2377
Fax: 03 9621 2477
Email: conz@cybersource.com.au
- - - END - - -

----- End forwarded message -----


(Log in to post comments)

What versions of MS Word?

Posted Oct 20, 2005 16:26 UTC (Thu) by ds2horner (subscriber, #13438) [Link]

The announcement and the website are not explicit.

Does anybody know?

or what is the earliest release of Word that can exploit this technique?

OSV and Phase N Launch OpenOpenOffice (O3)

Posted Oct 20, 2005 18:22 UTC (Thu) by dmh (guest, #14528) [Link]

I can't help but think OpenOpenDocument would be a better name. :o)

OSV and Phase N Launch OpenOpenOffice (O3)

Posted Oct 20, 2005 19:20 UTC (Thu) by kfiles (subscriber, #11628) [Link]

Am I the only one who thinks that Con's argument against local translation -- that installing OpenOffice.org or using some of its source code is too difficult -- is wrong?

He suggests that installing an OpenOffice.org translation server based upon a Perl SOAP server would be easier than a oofilter DLL? What about all those poor suckers who want to open ODF documents on the train?

And he dismisses out of hand the argument that companies would be uneasy using a public translation server? Really? I think that argument would apply to *all* companies I've ever worked at.

I think the general idea is brilliant, but would much rather see a completely local plugin using a downloadable OpenOffice.org import/export filter dll.

Thanks,
--kirby

OSV and Phase N Launch OpenOpenOffice (O3)

Posted Oct 21, 2005 3:58 UTC (Fri) by RMetz (guest, #27939) [Link]

"And he dismisses out of hand the argument that companies would be uneasy using a public translation server? Really? I think that argument would apply to *all* companies I've ever worked at."

You are absolutely right. I think the public translation server idea is DOA.

OSV and Phase N Launch OpenOpenOffice (O3)

Posted Oct 21, 2005 13:57 UTC (Fri) by dwheeler (subscriber, #1216) [Link]

Obviously, "on the train" you'd want another solution. But in an office LAN, this might be a reasonable solution.

Note that it could be "on a local LAN", so even if you have sensitive documents you don't want to just send over the Internet to a third party, that's okay... just send in on your LAN to a server with all the software. In environments where they hate to install ANY software, this might be a reasonable intermediate step.

OSV and Phase N Launch OpenOpenOffice (O3)

Posted Oct 21, 2005 16:23 UTC (Fri) by kfiles (subscriber, #11628) [Link]

"In environments where they hate to install ANY software, this might be a reasonable intermediate step."

Perhaps, but in such an environment, how would you install the ODF import plugin (the one required to do the SOAP exchange)? And if you can swing installing such a plugin, why not a plugin plus a translation DLL?

The problem with such an installation can't be a C++ vs. C# problem: the CLR supports object files from both languages. And I doubt it's a license problem: I can't imagine why Open Source Victoria wouldn't license their own code as LGPL (like OpenOffice).

I just don't see the benefit of having to install some software on all desktops, plus installing a translation server -- vs. installing just a little more software on all the desktops.

Thanks,
--kirby

Lather, rinse, repeat.

Posted Oct 21, 2005 0:06 UTC (Fri) by xoddam (subscriber, #2322) [Link]

if

> Microsoft has made it trivial to write plugins for Office using .NET

then what's with SOAP and Perl? I smell a laundry.

Copyright © 2005, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds