On Saturday, 5 Jan 2019 at 16:59, Uwe Brauer wrote:
> Thanks, right now I am struggling to install the pandoc-citeproc
> filter.
On Debian, it's its own package so easy but I do know that, at least in
the past, the version on Debian was quite significantly behind
upstream. This may or may not ma
>>> "Eric" == Eric S Fraga writes:
> I use the following (attached) script to convert LaTeX files (usually
> generated by org) to docx. It sometimes works well, or at least well
> enough for my uses. Maybe you can adapt it to your needs.
Thanks, right now I am struggling to install th
I use the following (attached) script to convert LaTeX files (usually
generated by org) to docx. It sometimes works well, or at least well
enough for my uses. Maybe you can adapt it to your needs.
--
Eric S Fraga via Emacs 27.0.50, Org release_9.1.14-1035-gfeb442
#!/bin/sh -f
BASE=$(basename $1
> I have used pandoc a little a while ago. See
>
http://kitchingroup.cheme.cmu.edu/blog/2015/01/29/Export-org-mode-to-docx-with-citations-via-pandoc/
> If you search pandoc on my blog you may find some more.
Thanks for pointing that out I did visit your blog. The resulting docx
does
>>> "Ken" == Ken Mankoff writes:
> On 2019-01-04 at 22:37 +0100, Uwe Brauer 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 ca
On 2019-01-04 at 22:37 +0100, Uwe Brauer 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 mas
I have used pandoc a little a while ago. See
http://kitchingroup.cheme.cmu.edu/blog/2015/01/29/Export-org-mode-to-docx-with-citations-via-pandoc/
If you search pandoc on my blog you may find some more.
On Fri, Jan 4, 2019 at 5:28 PM Uwe Brauer wrote:
> >>> "Ken" == Ken Mankoff writes:
>
>
>>> "Ken" == Ken Mankoff writes:
> On 2019-01-04 at 18:08 +0100, Uwe Brauer wrote:
>> 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
On 2019-01-04 at 18:08 +0100, Uwe Brauer wrote:
> 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 t
It is identical to the html output, it just that odt doesn't render the
html tags. You can just customize that variable to get rid of the html
markers, and then it will look better. I don't know how to get bold/italics
in odt though.
John
---
Professor John Kitchin
>>> "John" == John Kitchin writes:
> 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.
Right.
> You can customize how these are formatted to some extent in the
> variable:
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 preprocess
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 kl
13 matches
Mail list logo
