From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-ref exports nicely to html but not to odt
Date: Fri, 04 Jan 2019 14:27:07 -0500 [thread overview]
Message-ID: <m2h8eody0k.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <87tviouz88.fsf@mat.ucm.es>
Export to backends other than LaTeX have pretty limited support.
I assume by a lot of rubbish you mean there is a lot of html markers in
the bibliography.
You can customize how these are formatted to some extent in the
variable: org-ref-bibliography-entry-format
This is not a citation preprocessor though, so it will not do things
like numbered references, or handle markup in the bibtex entries.
You might check out https://github.com/andras-simonyi/citeproc-org, it
might have more capability along those lines.
Uwe Brauer <oub@mat.ucm.es> writes:
> Hi
>
> Please look at the following example
>
> #+begin_example
> * Bibliography
>
> citep:tao08:_global
>
> bibliographystyle:plain
> bibliography:test.bib
>
> #+end_example
>
> When I export it to html, the bibliography comes out nice.
> When I export it to odt, the resulting odt files contains a lot of
> rubbish.
>
> A kludge is to export it to html and then open it with LO/OO and copy
> it in an empty odt file, but is there any other solution?
>
> regards
>
> Uwe Brauer
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
next prev parent reply other threads:[~2019-01-04 19:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 17:08 org-ref exports nicely to html but not to odt Uwe Brauer
2019-01-04 19:27 ` John Kitchin [this message]
2019-01-04 20:42 ` Uwe Brauer
2019-01-04 20:50 ` John Kitchin
2019-01-04 21:00 ` Ken Mankoff
2019-01-04 21:37 ` Uwe Brauer
2019-01-04 21:52 ` Ken Mankoff
2019-01-04 22:06 ` Uwe Brauer
2019-01-04 22:34 ` John Kitchin
2019-01-05 8:48 ` Uwe Brauer
2019-01-05 10:21 ` Eric S Fraga
2019-01-05 15:59 ` Uwe Brauer
2019-01-05 16:48 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2h8eody0k.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=oub@mat.ucm.es \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.