incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis E. Hamilton" <orc...@apache.org>
Subject RE: Ask for advice:cloud office interoperability
Date Fri, 05 Oct 2012 04:51:06 GMT
I don't understand.

Microsoft began supporting ODF 1.0 in Office 2007 (SP2 I think).

They also support ODF 1.0 in Office 2010.

In Office 2013/365 there is support for ODF 1.2, including with support of OpenFormula in
Excel.

There are now three ways to consider interoperability among Office and OpenOffice users -
via Office Binary Formats, via OOXML, and via ODF 1.2.

Also, the support for ODF documents is now extending to the Web version of Word, Excel, and
PowerPoint in the SkyDrive cloud service.  That provides a more-limited but useful potential
for interchange, at least for the browsers that SkyDrive supports with Office Web access.

I assume that there is not full agreement of functionality.  

I think now is time to see how successful interchange can be.  Then learn where are the best
areas for improvement.

I agree that this interoperability is very important.  It is not easy.  Not even if everyone
is eager and willing.

 - Dennis 

-----Original Message-----
From: zhun guo [mailto:mike5guo@gmail.com] 
Sent: Thursday, October 04, 2012 19:30
To: ooo-dev@incubator.apache.org
Subject: Re: Ask for advice:cloud office interoperability

to Juergen, Microsoft will never support ODF. But Microsoft's market share
is 95%. We must cooperate with Microsoft.
Which all company support is HTML . So it is the only format ,with it all
the company can interoperate?

Zhun Guo

2012/10/4 Jürgen Schmidt <jogischmidt@gmail.com>

> On 10/4/12 4:06 PM, zhun guo wrote:
> > Hi,all,Joost not knew our means. We means ,how to solve the problem,the
> > difficult of ODF interoperate with OOXML ,which Ian Lynch had met. this
> is
> > for native office software.
> > *    The second , cloud office documents company also face the same
> > question,  *Google Docs,Microsoft Office 365,Zoho,苹果icloud,Adobe
> > Acrobat.com<https://www.acrobat.com/>
> > ,ThinkFree <http://thinkfree.com/>,Cisco WebEx
> > WebOffice<http://www.weboffice.com/>
> > ,IBM Docs  ,etc, use ODF,OOXML,PDF,HTML .  Then how to interoperate with
> > each other?
>
> by supporting one really open standard like ODF ;-) And work together on
> improvements or enhancements where necessary. Online editors are tools
> that work on docs in an cloud storage and desktop clients like AOO can
> access these docs as well. The question is more how collaborative
> editing on ODF can be managed in a way that online editors as well as
> desktop clients can use it. It probably don't have to be a completely
> new format.
>
> Juergen
>
>
> >
> > Zhun Guo
> >
> >
> > 2012/10/2 Joost Andrae <Joost.Andrae@gmx.de>
> >
> >> Hi,
> >>
> >> Am 02.10.2012 13:03, schrieb zhun guo:
> >>> Hi,Zhengfan and Ian Lynch,
> >>>      All format office documents' interoperability is important.
> >>> 1. ODF and OOXML, is more concerned about data storage. Microsoft, and
> >>> OpenOffice is the supporter。But we need ODF and OOXML to be  merged to
> a
> >>> new one format. And some wroking are doing 。Otherwise, we should face
> the
> >>> question,just like  Ian Lynch's problem.
> >>> 2. HTML, is more concerned about data revealing。 Google Docs,IBM
> >>> Docs,Microsoft Office 365,Zoho,Think Free,Adobe Acobat, Cisco WebEx
> ,all
> >>> these cloud office documents select the same format.  Maybe it is a new
> >> way
> >>> for office documents interoperability. As Rob Weir ,OASIS OpenDocument
> TC
> >>> chairman,says"
> >>> I find the topic of web editor interoperability very interesting.  It
> >>> is, in many ways, the continuation of the "office interop" battles we
> >>> have fought for the last decade.  But the new technology brings new
> >>> challenges and new opportunities, and perhaps even an opportunity to
> >>> avoid repeating the mistakes of the past!
> >>>    "
> >>>     ODF? OOXML?PDF?HTML?...I think it is better to choose one format
> for
> >>> documents interoperability,than choose two or three! It is important
> >> ,just
> >>> like ASCII which is the basic for  Information Interchange.
> >>>     Do you agree?
> >>
> >> ACSII compared to the characters within a GB18030 font ? This is just
> >> one example why ASCII doesn't work here. UNICODE characters within a XML
> >> based document format is much better for information exchange especially
> >> if you use an application that has been globalized and localized to a
> >> valuable number of languages. And as long as ODF and it's counterparts
> >> are comparable to other document formats then why should there be a new
> >> document format? ODF is ISO and OASIS approved, has been designed for
> >> this purpose and it can be used by everyone. And parts of your ideas
> >> have already been implemented as UOF in China.
> >> Using ODFDOM (http://incubator.apache.org/odftoolkit/) as a basis for
> >> such an application could serve very well as a container to proof
> >> interoperability between applications by using ODF as it's container.
> >>
> >> Kind regards, Joost
> >>
> >>
> >>
> >
>
>


Mime
View raw message