From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rustom Mody Subject: odt export to google-docs problem continues Date: Mon, 21 Nov 2011 18:18:13 +0530 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=00151774156e93e2e104b23e19e6 Return-path: Received: from eggs.gnu.org ([140.186.70.92]:50068) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RSTIM-0007h4-7h for emacs-orgmode@gnu.org; Mon, 21 Nov 2011 07:48:22 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RSTIF-0007Un-5x for emacs-orgmode@gnu.org; Mon, 21 Nov 2011 07:48:22 -0500 Received: from mail-iy0-f169.google.com ([209.85.210.169]:39138) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RSTIF-0007Uf-2k for emacs-orgmode@gnu.org; Mon, 21 Nov 2011 07:48:15 -0500 Received: by iaek3 with SMTP id k3so10503522iae.0 for ; Mon, 21 Nov 2011 04:48:13 -0800 (PST) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Jambunathan K Cc: emacs-orgmode --00151774156e93e2e104b23e19e6 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Nov 18, 2011 at 11:21 AM, Jambunathan K wrote: > Suvayu/Rustom > > suvayu ali writes: > > > Hi Jambunathan, > > > > On Thu, Nov 17, 2011 at 11:06, Jambunathan K > wrote: > >> Can anyone else reproduce this? > > > > I can replicate this. The odt file exported by org-odt is not accepted > > by google docs even though libreoffice opens it without problems. > > However it I open it with libreoffice and say edit and save, google > > docs then accepts the new file. > > With my some experimentation, I am able to reproduce it now. I have this > in my .emacs. > > ,---- > | (setq org-export-odt-prettify-xml t) > Well now google docs accepts but libreoffice itself says "file is corrupt shall I repair?" If I take the odt file directly made by exporter direcly in googledocs there are lots of spurious spaces eg between bullets and the first word. If I push it through libreoffice and resave then googledocs does a better job of displaying --00151774156e93e2e104b23e19e6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Fri, Nov 18, 2011 at 11:21 AM, Jambun= athan K <kja= mbunathan@gmail.com> wrote:

suvayu ali <fatkasuvayu= +linux@gmail.com> writes:

> Hi Jambunathan,
>
> On Thu, Nov 17, 2011 at 11:06, Jambunathan K <kjambunathan@gmail.com> wrote:
>> Can anyone else reproduce this?
>
> I can replicate this. The odt file exported by org-odt is not accepted=
> by google docs even though libreoffice opens it without problems.
> However it I open it with libreoffice and say edit and save, google > docs then accepts the new file.

With my some experimentation, I am able to reproduce it now. I have t= his
in my .emacs.

,----
| (setq org-export-odt-prettify-xml t)

Well now g= oogle docs accepts but libreoffice itself says "file is corrupt shall = I repair?"
If I take the odt file directly made by exporter direcly= in googledocs there are lots of spurious spaces eg between bullets and the= first word.

If I push it through libreoffice and resave then googledocs does a bett= er job of displaying
--00151774156e93e2e104b23e19e6--