From: Jambunathan K <kjambunathan@gmail.com>
To: suvayu ali <fatkasuvayu+linux@gmail.com>
Cc: Rustom Mody <rustompmody@gmail.com>,
emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: odt export to google-docs problem
Date: Fri, 18 Nov 2011 11:21:53 +0530 [thread overview]
Message-ID: <817h2y0yh2.fsf@gmail.com> (raw)
In-Reply-To: <CAMXnza3s92Q4cnEw4S7zJt4YHPQBeen61xe0aOLPRtovQJy-OA@mail.gmail.com> (suvayu ali's message of "Thu, 17 Nov 2011 23:51:10 +0100")
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)
`----
and it was preventing me to "see" the problem in the first place.
The above variable is a custom variable and when it is true, the
exporter runs indent-region on all xml files that is part of the final
odt file. The default setting of this variable if off, btw, (as
otherwise it could slow things down for large exported files.)
Since I often have to examine the xml, I have this variable on.
This setting helps exporting to google directly i.e., I don't have to
edit and resave the file for succesful loading, as Suvayu is suggesting.
Indentation only makes whitespace changes and it shouldn't affect how
XML files are read in. So, I am unable to explain why Google accepts the
indented XML file and not the original one.
Anyways turn that variable on and let me know what you see.
ps: It seems like there is a bug on Google side of things. Since it only
says the file is corrupt and not what the *actual* corruption is I am
out of my wits. So basically I am shooting in the dark ...
Thanks for helping out here. May be as time progresses an understanding
will emerge.
> I have attached both odt files along with the org file.
>
> PS: tested with minimal Emacs 24 and org release_7.7-543-g176ddba
--
next prev parent reply other threads:[~2011-11-18 5:52 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
2011-11-17 22:51 ` suvayu ali
2011-11-18 5:51 ` Jambunathan K [this message]
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=817h2y0yh2.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=fatkasuvayu+linux@gmail.com \
--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).