From ooo-dev-return-27189-apmail-incubator-ooo-dev-archive=incubator.apache.org@incubator.apache.org Fri Oct 5 02:30:00 2012 Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E9596D712 for ; Fri, 5 Oct 2012 02:30:00 +0000 (UTC) Received: (qmail 65110 invoked by uid 500); 5 Oct 2012 02:30:00 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 65033 invoked by uid 500); 5 Oct 2012 02:30:00 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 65022 invoked by uid 99); 5 Oct 2012 02:30:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Oct 2012 02:30:00 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mike5guo@gmail.com designates 209.85.215.47 as permitted sender) Received: from [209.85.215.47] (HELO mail-la0-f47.google.com) (209.85.215.47) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Oct 2012 02:29:56 +0000 Received: by mail-la0-f47.google.com with SMTP id h5so565361lam.6 for ; Thu, 04 Oct 2012 19:29:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=r1nJBJFfNc+Z51Kf8x1UU2r/sLvrL12tj7M0nBcSM4k=; b=VKRmBaVe2QRJ48XPMVPbrIG8JhDCOPdhLDpQjDDQGwWldRjCniQdWbIn3jDc9nDl7X Bz/wsi7pExZibwTpZOAtSlL2Czx1wU+ZokiUp4a8UDz1dDwKUS8OjeyctnrHRqAqFh7B D4D36LNK7jqicsVAYVD8BmtuzrCbJ9xjvBs+ziJ9ExjjxcU9nqXFmfa90Gjzd1e7BcMa Nco7UTBuSYGdKnIu3rtfsprsutWqx3/mdWbAZHQUMmX5DbDkqnKHTOJGf0Ssx2/pXdHr nLDwZRRzr2vDCf5+neI2uVp8jWvKG4sGTttVfoSi+Wj0DviCAlPzeMxFeJGZ99T975ja 19fg== MIME-Version: 1.0 Received: by 10.152.148.195 with SMTP id tu3mr5710564lab.16.1349404174662; Thu, 04 Oct 2012 19:29:34 -0700 (PDT) Received: by 10.112.37.42 with HTTP; Thu, 4 Oct 2012 19:29:34 -0700 (PDT) In-Reply-To: <506D9E79.7060207@gmail.com> References: <506D9E79.7060207@gmail.com> Date: Fri, 5 Oct 2012 10:29:34 +0800 Message-ID: Subject: Re: Ask for advice:cloud office interoperability From: zhun guo To: ooo-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=e89a8f2348557d3adb04cb46a479 X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f2348557d3adb04cb46a479 Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: quoted-printable 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=A8=B9rgen Schmidt > 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=A3=ACMicrosoft Office 365=A3=ACZoho=A3=AC=C6=BB= =B9=FBicloud=A3=ACAdobe > > Acrobat.com > > =A3=ACThinkFree =A3=ACCisco WebEx > > WebOffice > > =A3=ACIBM Docs ,etc, use ODF,OOXML,PDF,HTML . Then how to interoperat= e 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 > > > >> 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, an= d > >>> OpenOffice is the supporter=A1=A3But we need ODF and OOXML to be mer= ged to > a > >>> new one format. And some wroking are doing =A1=A3Otherwise=A3=AC we s= hould face > the > >>> question,just like Ian Lynch's problem. > >>> 2. HTML, is more concerned about data revealing=A1=A3 Google Docs=A3= =ACIBM > >>> Docs=A3=ACMicrosoft Office 365,Zoho,Think Free,Adobe Acobat, Cisco We= bEx > ,all > >>> these cloud office documents select the same format. Maybe it is a n= ew > >> way > >>> for office documents interoperability. As Rob Weir ,OASIS OpenDocumen= t > 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 X= ML > >> based document format is much better for information exchange especial= ly > >> 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 ne= w > >> 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 > >> > >> > >> > > > > --e89a8f2348557d3adb04cb46a479--