emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: Rainer@krugs.de
Cc: Emacs-orgmode@gnu.org
Subject: Re: Error in export to odt
Date: Wed, 14 Nov 2012 18:16:51 +0530	[thread overview]
Message-ID: <87ehjwgxms.fsf@gmail.com> (raw)
In-Reply-To: <50A37BAE.5000609@gmail.com> (Rainer M. Krug's message of "Wed, 14 Nov 2012 12:08:30 +0100")

Rainer M Krug <r.m.krug@gmail.com> writes:

> Hi
> I am exporting a document to odt (Org-mode version 7.9.2
> (release_7.9.2-459-g6f7e92 @
> /home/rkrug/.emacs.d/org-mode/lisp/) and the odt generates fine, but
> it is corrupt. The simple org
> document looks like followed:
> ####
> * Required data / field work
> 100m^2--1000m2
> ####
> This results in a "Format error discovered in the file in sub-document
> content.xml at 353,50(row,col)"
> simply adding spaces around the "--" solves the problem.

Above example works fine with the new exporter.

Old exporter is pretty much on the way out and I would strongly
recommend that you use the new exporter as much as possible.

    (require 'org-e-odt)
    M-x org-export-dispatch RET

That said, this is what happens.  I will accept any suggestions for
possible fix or blindly apply a patch if one would circulate that to me.

Step 1. 100m^2--1000m2
Step 2. 100m^2&#x2013;1000m2
Step 3. 100m<text:span text:style-name="OrgSuperscript">2&</text:span>#x2013;1000m2

Step 1 to Step 2 sounds good.  This happens as part of

Step 2 to Step is not OK.  Note that the "&" that introduces the `ndash'
gets pulled in as part of subscript.  This happens as part of

Now `org-match-substring-regexp' which goes something like 

    "\\([^\\]\\|^\\)\\([_^]\\)\\(\\({\\([^{}]*?\\|\\(?:[^{}]*?{[^{}]*?}\\)+[^{}]*?\\|\\(?:[^{}]*?{\\(?:[^{}]*?{[^{}]*?}\\)+[^{}]*?}\\)+[^{}]*?\\)}\\)\\|\\((\\([^()]*?\\|\\(?:[^()]*?([^()]*?)\\)+[^()]*?\\|\\(?:[^()]*?(\\(?:[^()]*?([^()]*?)\\)+[^()]*?)\\)+[^()]*?\\))\\)\\|\\(\\(?:\\*\\|[-+]?[^-+*!@#$%^_ 	\n,:\"?<>~;./{}=()]+\\)\\)\\)"

looks like a swear word to me :-).  Frankly, I don't know or care about

I am not sure whether there is a bug in that regexp or the regexp is
doing the right thing but that a `org-protected' property should be
applied to some part of the string that is undergoing transformation.

If someone can make sense out of what is happening and if I happen to
trust the other person's judgment, then this bug has some hope of
getting addressed.  Otherwise, this bug will remain un-fixed.

But, I am sure what a ndash is doing in a Math expression.  May be it is
a minus-that-is-aspiring-to-be-a-ndash, I don't know.

Anyways, try the new exporter.  

One warning though:

Make sure that you require ONLY ONE of org-odt and org-e-odt in your
.emacs.  If you require them simulatneously org-odt will not be usable.
There is some error which I haven't had time to investigate.

> I attach the tmp.odt with the error.
> Libre Office - Version (Build ID: 360m1(Build:2))
> Ubuntu Quantal
> Cheers,
> Rainer


  reply	other threads:[~2012-11-14 12:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14 11:08 Error in export to odt Rainer M Krug
2012-11-14 12:46 ` Jambunathan K [this message]
2012-11-14 13:08   ` Rainer M Krug

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:

  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=87ehjwgxms.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --cc=Emacs-orgmode@gnu.org \
    --cc=Rainer@krugs.de \


* 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


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).