emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: export to ODT fails strangely
Date: Sun, 2 Feb 2014 19:10:18 +0000	[thread overview]
Message-ID: <877g9ds545.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87mwiixv24.fsf@gmail.com> (Nicolas Goaziou's message of "Sun, 26 Jan 2014 23:00:35 +0100")

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
>
> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
>> I hope somebody can point me in the right direction.  I am trying to
>> export a large document to ODT to share with my
>> collaborators.  Exporting to LaTeX works like a charm.  However, with
>> ODT, the exporter fails with:
>>
>> ,----
>> | OpenDocument export failed: FIXME: Resolve (paragraph (:begin 23510 :end
>> | 23635 :contents-begin 23599 :contents-end 23629 :post-blank 1
>> | :post-affiliated 23599 :name "fig:graph" :caption (((#("Dependency graph
>> | of major tasks in the project." 0 47 (:parent #4))))) :results ("")
>> | [...]
>> `----
>
> I guess you are cross-referencing to a paragraph (probably a standalone
> image) named "fig:graph". You can probably get an ECM if you isolate
> both that paragraph and the link referring to it.

Well, you are partially correct in that the problem has to do with my
[[fig:graph]] type of links, which I assume are valid?  Does the "fig:"
maybe confuse something?  

In any case, I could get the document to export but only by removing all
similar links.  I have two figures and 6 references to these figures in
my large document.  I tried changing "fig:" to "fig-" in all cases but I
have the same problem.  Removing all the links (all I did was change
"[[fig" to "[fig") allows the file to be exported (without the links,
obviously).

This particular document is no longer needed.  It was a grant proposal
which was submitted on Thursday and will never need to be exported again
so the problem no longer affects me.  However, there is some problem
somewhere...

While I'm at it, thanks again to the org community: the process of
putting together a rather large proposal went so much better thanks to
org than it would have been had I had to use any alternative system!

Thanks,
eric

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 24.3.50.1, Org release_8.2.5h-585-g5f0ca0

next prev parent reply	other threads:[~2014-02-02 19:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-26 21:42 export to ODT fails strangely Eric S Fraga
2014-01-26 22:00 ` Nicolas Goaziou
2014-02-02 19:10   ` Eric S Fraga [this message]
2014-01-27 10:28 ` Bastien

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=877g9ds545.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@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

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