From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jambunathan K Subject: Re: new exporter corrupts ODT Date: Sat, 02 Jun 2012 19:11:11 +0530 Message-ID: <81bol1rfuw.fsf@gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:50860) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SaoaI-00015L-Dx for emacs-orgmode@gnu.org; Sat, 02 Jun 2012 09:41:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SaoaG-0005m0-3Y for emacs-orgmode@gnu.org; Sat, 02 Jun 2012 09:41:37 -0400 Received: from mail-pz0-f41.google.com ([209.85.210.41]:42557) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SaoaF-0005jx-QT for emacs-orgmode@gnu.org; Sat, 02 Jun 2012 09:41:36 -0400 Received: by dakp5 with SMTP id p5so4170365dak.0 for ; Sat, 02 Jun 2012 06:41:33 -0700 (PDT) In-Reply-To: (Michael Brand's message of "Sat, 2 Jun 2012 11:20:06 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Michael Brand Cc: Org Mode Michael Brand writes: > Hi all > > If OpenOffice.org 3.2.0 is too old to count please tell me and forget. > > With an Org file containing only "* a\n" the old exporter is ok but the > new exporter release_7.8.10-633 on 23.3.1 makes an ODT reported as > "corrupt" by OOo. Attached are the Org and ODT exported as old, new > and new repaired by OOo 3.2.0. I am not able to reproduce this issue locally. My LibreOffice is fairly recent. (LibreOffice 3.5.2.2 Build ID: 281b639-6baa1d3-ef66a77-d866f25-f36d45f) If I pass the corrupted file through an online validator [1], I get the below error. The culprit is the mimetype file. Note the leading whitespace and the trailing newline. If I fix this extraneous whitespace by hand, then I see that the reported corruption goes away. ,---- | application/vnd.oasis.opendocument.text `---- I can confirm that ODT exporter, never creates the above leading and trailing whitespaces. Unless you hand-edited the ODT document, I think the error could be because of one of the customizations you have. (Do you have `org-e-odt-prettify-xml' set to t. If yes, what mode does mimetype file open for you. For me, mimetype opens in Fundamental mode.) ,---- | ODF Validator Result Page | Result for release_7.8.10-633.org.new.odt | | The document is NOT conformant ODF1.2! | Details: | release_7.8.10-633.org.new.odt: Info: ODF version of root document: 1.2 | release_7.8.10-633.org.new.odt/mimetype: Error: The ODF package 'release_7.8.10-633.org.new.odt' contains a 'mimetype' file containing ' application/vnd.oasis.opendocument.text', which differs from the mediatype of the root document 'application/vnd.oasis.opendocument.text'! | release_7.8.10-633.org.new.odt: Error: The ODF mimetype ' application/vnd.oasis.opendocument.text' is invalid for the ODF XML Schema document! | release_7.8.10-633.org.new.odt/mimetype: Info: mimetype is not an ODFMediaTypes mimetype. | internal:/schema/odf1.2/OpenDocument-v1.2-cos01-manifest-schema.rng: Info: parsed. | release_7.8.10-633.org.new.odt/META-INF/manifest.xml: Info: no errors, no warnings | release_7.8.10-633.org.new.odt/mimetype: Info: 1 errors, no warnings | release_7.8.10-633.org.new.odt: Info: Media Type: application/vnd.oasis.opendocument.text | internal:/schema/odf1.2/OpenDocument-v1.2-cos01-schema.rng: Info: parsed. | release_7.8.10-633.org.new.odt/meta.xml: Info: Generator: Generated by Org mode 7.8.10 in Emacs 23.3.1. | release_7.8.10-633.org.new.odt/meta.xml: Info: no errors, no warnings | release_7.8.10-633.org.new.odt/styles.xml: Info: no errors, no warnings | release_7.8.10-633.org.new.odt/content.xml: Info: no errors, no warnings | internal:/schema/odf1.2/OpenDocument-v1.2-cos01-dsig-schema.rng: Info: parsed. | release_7.8.10-633.org.new.odt: Info: 2 errors, no warnings `---- Footnotes: [1] http://odf-validator.rhcloud.com/ --