From: Richard Lawrence <email@example.com>
Subject: Re: org-cite and org-citeproc
Date: Wed, 01 Apr 2015 07:39:22 -0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Rasmus <email@example.com> writes:
> Richard Lawrence <firstname.lastname@example.org> writes:
>> I don't really know anything about the ODT format, though. My code
>> more-or-less blindly pastes Pandoc-generated XML into the document
>> during Org ODT export. Can someone who knows more about the format take
>> a look at the file and see if there is some subtle problem I'm not
> I can't test your code 'cause I, for personal/silly reasons, refuse to
> spend any more dealing with compiling Haskell.
Fair enough. :)
> That being said, my gut feeling is that you have to define the data
> For example, to add a (sub)title to a odt document the field/keyword is
> defined in a file different from contents.xml and will just not be printed
> if used in contents.xml only.
Hmm. But the citations are all just represented as <text:p>
nodes...surely that doesn't have to be defined elsewhere?
I am now guessing that the problem is that you can't have one <text:p>
inside another. Each paragraph is wrapped in a <text:p>, but so are the
citations within it...maybe that is not correct and so LibreOffice
doesn't like it.
> Also, the bibliography is not "correct" in the sense that if it was setup
> in the right semantic way, it would be gray in LO, like the TOC.
Do you know what other markup is required in this case? It looks like
maybe the TOC is gray because it is marked with a "text:protected"
attribute, or maybe because it has an associated "OrgIndexSection"
next prev parent reply other threads:[~2015-04-01 14:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 18:53 Richard Lawrence
2015-03-31 8:16 ` Eric S Fraga
2015-03-31 19:13 ` Richard Lawrence
2015-03-31 19:34 ` Nick Dokos
2015-03-31 20:29 ` Thomas S. Dye
2015-03-31 21:57 ` Richard Lawrence
2015-04-01 0:41 ` Thomas S. Dye
2015-04-01 15:42 ` Richard Lawrence
2015-04-01 19:41 ` Thomas S. Dye
2015-04-02 15:57 ` Richard Lawrence
2015-04-02 16:45 ` Thomas S. Dye
2015-03-31 21:12 ` Eric S Fraga
2015-04-01 7:49 ` Andreas Leha
2015-04-02 14:29 ` Eric S Fraga
2015-04-02 15:11 ` Richard Lawrence
2015-04-02 19:26 ` Andreas Leha
2015-03-31 22:03 ` Rasmus
2015-04-01 14:39 ` Richard Lawrence [this message]
2015-04-02 0:08 ` Rasmus
2015-04-02 15:26 ` Richard Lawrence
2015-04-02 15:51 ` Aaron Ecay
2015-04-02 17:38 ` Richard Lawrence
2015-04-06 18:51 ` Richard Lawrence
2015-06-16 19:36 ` Matt Price
2015-06-18 22:44 ` Richard Lawrence
2015-04-02 19:17 ` Rasmus
2015-04-03 2:56 ` Richard Lawrence
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 \
* 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).