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 540C8DBEC for ; Mon, 1 Oct 2012 08:35:49 +0000 (UTC) Received: (qmail 99044 invoked by uid 500); 1 Oct 2012 08:35:48 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 98973 invoked by uid 500); 1 Oct 2012 08:35:48 -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 98958 invoked by uid 99); 1 Oct 2012 08:35:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Oct 2012 08:35:48 +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 (nike.apache.org: domain of ianrlynch@gmail.com designates 209.85.216.54 as permitted sender) Received: from [209.85.216.54] (HELO mail-qa0-f54.google.com) (209.85.216.54) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Oct 2012 08:35:42 +0000 Received: by qady23 with SMTP id y23so1583815qad.6 for ; Mon, 01 Oct 2012 01:35:21 -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=Fcdxw2+KvgKYuzjOG2inEXca+ZFYHjkUA1kx6MirXkg=; b=swUqMbl+tZ96GR6KBUUEmOq3Nw7CyNLFzncYoKhXwLkUMU+/nbVHmjrezUq1c0lyXL O1aUg6byihP7dxUqDWhEcXEisXX9xmb4ANg5iqT/gupEptJ7e8QpMQR1QbCufmSpwYwG 9W3UgZXli5ioxoyU5Oo9rL5Y0aeqccYnyd0Wd/wMVcPxlOImIgC+MGt9yHGKtZEF1Rlv DDHBpk1UIk78VmraOFC8Hp/vH7Qn3kPT1bvNBcAN/3ix2vltJxEN7EiVVHPoU0UGUxBO tWCa4I6dMWDV82xDOmmLYVtPNolHxhWU1O69dXMQkjyFTg4ahbKrHF+tQm4RVmH8Qvt9 PvLw== MIME-Version: 1.0 Received: by 10.224.168.83 with SMTP id t19mr35439402qay.8.1349080521631; Mon, 01 Oct 2012 01:35:21 -0700 (PDT) Received: by 10.49.35.212 with HTTP; Mon, 1 Oct 2012 01:35:21 -0700 (PDT) In-Reply-To: References: Date: Mon, 1 Oct 2012 09:35:21 +0100 Message-ID: Subject: Re: Ask for advice:cloud office interoperability From: Ian Lynch To: ooo-dev@incubator.apache.org, "zheng.easyfan" Content-Type: multipart/alternative; boundary=20cf3074b5ce43e68504cafb4940 --20cf3074b5ce43e68504cafb4940 Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: quoted-printable On 1 October 2012 05:41, zheng.easyfan wrote: > > HI, Zhun Guo: > > In general, I agree with your second point in the mail that, we should > make better interoperability of office productions. And my opinion here = is > that, in the category of interoperability, we even should not trying to > separate the office applications as on line or off line ones. For whateve= r > the type of an office application it is, the exactly necessary function i= t > should supplied is to represent a document with specified file format > correctly. And to any document from any user of any office application, > there should be only one CORRECT representation result anyway. > And I guess, the interoperability topics are the most important ones for > each member of this community. For such kind of issues, as the most visib= le > ones, are always directly driven by users :( > So, what is your suggestion or idea for it? > My recent experience with docx to odt has been that for any document with tables it is not good enough. I get a lot of routine docs in docX format from UK government departments and very few can be used without a lot of work. I also don't know how well docs I send to them as exports will appear to them. Since Word processing documents are the most common and docX is now in much wider use I think the priority needs to be to get the docX odt filter to as good a standard as possible particularly with tables, headers, footers and page structures. Without this it is going to be very difficult for anyone that has to work with government departments to adopt AOO as an alternative to MSO. Google Docs does it better and so it means Google Docs is then a bigger competitor for AOO too. I also think that whichever of AOO or LibO implements these filters the best is likely to get adoption over the other. Zhengfan > > > > =D2=D1=B4=D3=C8=FD=D0=C7=CA=D6=BB=FA=B7=A2=CB=CDzhun guo =D0=B4=B5=C0=A3=BADear All: > It is necessary for all cloud office interoperability with each > other. Do you think so ? > What I want to do,is not to design a product for my own company. I > just want to , between all cloud office websites, it can send documents > quickly. Such as ,Google Docs can send documents to Microsoft Office 365 > quickly, and directly . But now , Google Docs can only send documents > using email (SMTP) to Hotmail. So i think HTTP(SPDY) is better than SM= TP > for transfer online office documents ? So we should suggest ,IBM Docs > and Office 365 ,Acobat.com use the same protocol. > The second thing I want to do ,all online office interoperability . > your know , for native office, an Microsoft Office 2010 document should > be open and reedit by an Openoffice.org user , it means native office > interoperability. Then for the cloud office, it also need > interoperability. > So let us do this thing together!As I know ,you all are great man and > warmhearted! ?Thanks ! > Please see more details in my email attachments! or via a web site: > http://online-office-interoperability.blogspot.com/ > Best Regards! > > Zhun Guo > Shanghai Biaoma IT Co. > www.mabaoo.com > mike5guo(at)gmail.com > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --=20 Ian Ofqual Accredited IT Qualifications (The Schools ITQ) www.theINGOTs.org +44 (0)1827 305940 The Learning Machine Limited, Reg Office, 36 Ashby Road, Tamworth, Staffordshire, B79 8AQ. Reg No: 05560797, Registered in England and Wales. --20cf3074b5ce43e68504cafb4940--