Re: [O] odt export to google-docs problem

[Jambunathan K]

Rustom

Can you send me this odt file either on or off the list?

Please make sure that the document is not resaved from Libreoffice -
this is because LibreOffice rewrites XML if resaved. So send the file as
soon as it is exported out of org-odt.

What is the org-version?  Are you exporting with a minimal emacs? Just
to be sure it has nothing to do with your local configuration.

You may want to check for corruption using the instructions here.  (I
think the ODF validator has moved elsewhere lately)

,----
|    LibreOffice reports corrupt documents when the XML emitted by the
|    exporter is not well-formed according to OpenDocument schema. To
|    identify the root cause of corruption use one of the following
|    methods:
|    1. Use an Online validator
|       Pass the exported document through the 
[[http://tools.services.openoffice.org/odfvalidator/][ODF Validator]] and note
|       down the errors.
| 
|    2. Use Emacs' in-built validator. Immediately after exporting
|       1) C-x b test.odt
|       2) Open the `content.xml' file by hitting RET on it
|       3) Do M-x rng-first-error
|       4) Note the error message, the XML markup at the point of error
|          and the surrounding context.
`----


Jambunathan K.


Rustom Mody <address@hidden> 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.
>
> 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
>
> [And in case line-endings have anything to do with it: OS: Debian/
> testing]
>
>

--