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
Date: Thu, 17 Nov 2011 15:36:11 +0530	[thread overview]
Message-ID: <81sjlnawrw.fsf@gmail.com> (raw)
In-Reply-To: <CAJ+TeocaaHfnQfQ3a=dFLZRf=-9u+dPHd=a0xPa4hi4Lb83Meg@mail.gmail.com> (Rustom Mody's message of "Thu, 17 Nov 2011 14:43:21 +0530")

Rustom Mody <rustompmody@gmail.com> writes:

> Here is a small file for org mode
> ----------------
> #+OPTIONS: toc:nil
> #+TITLE: Report
> * Tue 8th
>   - http://www.haskell.org/
> * hello
> ----------------
> If I export to odt and then upload the odt to google docs,
> google-docs says the file is corrupt.

On my local machine I am seeing that the exported file is valid and
opens fine with LibreOffice-3.4 without any issues.

I haven't experimented with Google docs.


> It seems to make a difference whether the EOF is immediately at the
> end of "hello" or after a newline -- though not sure.
>
> As far as I can see files made directly by/in libreoffice upload to
> google-docs without any problem
>
> org: 7.7
> emacs 23.3.1

Make sure that org-odt is new. Older versions of org-odt did have some
corruption issues.

> [And in case line-endings have anything to do with it: OS: Debian/
> testing]

Can anyone else reproduce this?
-- 

  parent reply	other threads:[~2011-11-17 10:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-17  9:13 odt export to google-docs problem Rustom Mody
2011-11-17  9:35 ` Jambunathan K
2011-11-17 10:06 ` Jambunathan K [this message]
2011-11-17 22:51   ` suvayu ali
2011-11-18  5:51     ` Jambunathan K
2011-11-18 10:11       ` suvayu ali
2011-11-18 12:06       ` Rustom Mody

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=81sjlnawrw.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).