From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: emacs-orgmode@gnu.org
Subject: Re: on the fragility of export to ODT
Date: Tue, 17 Feb 2015 18:08:15 +0000 [thread overview]
Message-ID: <87a90c9zsg.fsf@delle7240.chemeng.ucl.ac.uk> (raw)
In-Reply-To: <87wq3hhalm.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Mon, 16 Feb 2015 21:20:37 +0100")
On Monday, 16 Feb 2015 at 21:20, Nicolas Goaziou wrote:
> Hello,
>
> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
>> At this point, I get very long data structures dumped to
>> *Messages*... difficult to figure out what is wrong. It's often my
>> mistake but tracking it down is difficult.
>
> You're using an internal link to target a paragraph (possibly a image or
> some such). This is apparently not supported yet by ox-odt (see
> `org-odt-link--infer-description').
>
> Could you try to find out the culprit and explain what you expected so
> I can fix it?
Hi Nicolas,
I have many internal references; in this document, all are to named
tables and figures.
I have tried but haven't managed to track down which one is causing
problems in this case.
I have tried extracting various bits into smaller org files but then the
problems disappear... :(
Part of the problem, I think (but please correct me if I'm wrong), is
that the positions indicated in the error messages are in the buffer
being exported after a certain amount of processing (including, I would
imagine, babel) and so it's difficult to find the actual location of the
problem.
If this is indeed the case, is there any way to retain the buffer that
is being processed at the point the error occurs?
>> However, more importantly, the failure is complete and nothing is
>> exported which does not help me at all. It would be great if offending
>> paragraphs (elements, objects, whatever) would be skipped over and the
>> rest of the document generated. Is this possible?
>
> At the moment, I think it is better to fix the errors than to ignore
> them. There are quite a few "FIXME" in ox-odt.
Okay, that's fine.
In any case, I'm in no panic as I have simply sent the PDF to my
co-author and that's good enough for now. Eventually, I may need to get
the DOC version but I can keep my fingers crossed and hope it doesn't
come to that...
thanks,
eric
--
: Eric S Fraga (0xFFFCF67D), Emacs 24.4.1, Org release_8.3beta-820-gd92ef9
next prev parent reply other threads:[~2015-02-17 18:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 17:29 on the fragility of export to ODT Eric S Fraga
2015-02-16 20:20 ` Nicolas Goaziou
2015-02-17 18:08 ` Eric S Fraga [this message]
2015-02-17 21:04 ` Nicolas Goaziou
2015-02-18 9:56 ` Eric S Fraga
2015-02-18 13:55 ` Nicolas Goaziou
2015-02-18 15:04 ` Eric S Fraga
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=87a90c9zsg.fsf@delle7240.chemeng.ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
/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).