emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: Rustom Mody <rustompmody@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: odt export to google-docs problem continues
Date: Thu, 24 Nov 2011 22:05:47 +0530	[thread overview]
Message-ID: <81obw1lbq4.fsf@gmail.com> (raw)
In-Reply-To: <CAJ+TeocufKkndqY3Ab=WvNpPQJuYarT15AJTCmTxYjbsiUD7Hg@mail.gmail.com> (Rustom Mody's message of "Mon, 21 Nov 2011 18:18:13 +0530")

Rustom Mody <rustompmody@gmail.com> writes:

> On Fri, Nov 18, 2011 at 11:21 AM, Jambunathan K <
> kjambunathan@gmail.com> wrote:
>
>     Suvayu/Rustom
>    
>     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 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

I am not sure what the issue could be. I will have the issue in the
background for now. 

The good thing is atleast a workaround is available.

Jambunathan K.

      reply	other threads:[~2011-11-24 16:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21 12:48 odt export to google-docs problem continues Rustom Mody
2011-11-24 16:35 ` Jambunathan K [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=81obw1lbq4.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rustompmody@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).