emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: Jambunathan K <kjambunathan@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:11:50 +0100	[thread overview]
Message-ID: <CAMXnza37x9+E7wZCSCPKXZGSAFJ1ORi3dRme=UOZvfYBd-iSmg@mail.gmail.com> (raw)
In-Reply-To: <817h2y0yh2.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 799 bytes --]

Hi Jambunathan,

On Fri, Nov 18, 2011 at 06:51, Jambunathan K <kjambunathan@gmail.com> wrote:
> ,----
> | (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.
>

I can confirm, using this setting generates an odt file which google
docs can read without any need for "editing and saving". The file is
attached in case you wanted to see it.

-- 
Suvayu

Open source is the future. It sets us free.

[-- Attachment #2: odt-test-prettify.odt --]
[-- Type: application/vnd.oasis.opendocument.text, Size: 8662 bytes --]

  reply	other threads:[~2011-11-18 10:12 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
2011-11-18 10:11       ` suvayu ali [this message]
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='CAMXnza37x9+E7wZCSCPKXZGSAFJ1ORi3dRme=UOZvfYBd-iSmg@mail.gmail.com' \
    --to=fatkasuvayu+linux@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kjambunathan@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).