From: Ken Mankoff <mankoff@gmail.com>
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 22:52:05 +0100 [thread overview]
Message-ID: <87tvioyttm.fsf@geus3064linuxwsm.geus.dk> (raw)
In-Reply-To: <87zhsgf6ju.fsf@mat.ucm.es>
On 2019-01-04 at 22:37 +0100, Uwe Brauer <oub@mat.ucm.es> wrote:
> I exported the org file in question to latex (I could also start
> directly with latex for that matter.)
Yes.
> Could I stick with bibtex?
Yes. No need to use biber + biblatex, you can stick with bibtex.
I only run that command because my massive 3000+ bib file contains things that pandoc has trouble with (accents? Not sure). That command extracts the bibtex entries used in the current document.
As I write this I realize this means you don't even need to compile the PDF and/or run bibtex. If you have a TeX file and an appropriate accompanying BiBTeX file, that should work.
> pandoc -f latex -t docx -o test.docx --bibliography /home/oub/texmf/bibtex/bib/bibgraf.bib test.tex
>
> /home/oub/texmf/bibtex/bib/bibgraf.bib is my main bibtex date base.
>
> But this did not work pandoc gets frozen.
>
> What do I miss.
I don't know. Try with a small bib file with 1 entry (and a TeX file that only cites that one entry). Does that work? Then maybe your bibgraf.bib has the same problem mine does (although I recall pandoc issuing an error and crashing, not just freezing).
If this method works with a MWE, then the issue my be your full bib file. In this case you need to extract the entries used in this document (e.g. my method). Presumably this subset does not cause the pandoc issue. I also find extracting the entries useful for archiving a project.
You can extract entries as I showed, or "bibexport <file>.aux" (requires a compiled PDF), or http://korrekt.org/page/Note:How_to_Extract_Used_Entries_From_BibTeX_Files or other methods...
-k.
next prev parent reply other threads:[~2019-01-04 21:52 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
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 [this message]
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
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=87tvioyttm.fsf@geus3064linuxwsm.geus.dk \
--to=mankoff@gmail.com \
--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 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).