Using ox-bibtex for bibliography html export I always get the complete content
of my .bib file under the headline References. How can I achieve that the
bibliography contains only the references cited in the org file?
Johannes
You might checkout the function at the end of this org-ref issue:
https://github.com/jkitchin/org-ref/issues/176
It provides a way to extract all bibtex src blocks to a file and is a
bit different than using org-babel-tangle.
Ken Mankoff writes:
> On 2016-06-14 at 21:29, Ken Mankoff wrote:
>> I
On 2016-06-14 at 21:29, Ken Mankoff wrote:
> I don't know how to tell Org to tangle-on-export with an argument or a
> setting, but it can evaluate code blocks on export, and one of those
> can do the tangling for you. The following might work?
>
> #+begin_src emacs-lisp :exports none
> (org-bab
On 2016-06-13 at 13:28, Sharon Kimble wrote:
> Ken Mankoff writes:
>> On 2016-06-13 at 13:07, Sharon Kimble wrote:
>>> I'm trying to have all my information for a org-mode document
>>> exported to latex contained within the source document. Specifically
>>> having the bibliography within the so
Ken Mankoff writes:
> On 2016-06-13 at 13:07, Sharon Kimble wrote:
>> I'm trying to have all my information for a org-mode document exported
>> to latex contained within the source document. Specifically having the
>> bibliography within the source document.
>>
>> But how do I do it? I've tried
On 2016-06-13 at 13:07, Sharon Kimble wrote:
> I'm trying to have all my information for a org-mode document exported
> to latex contained within the source document. Specifically having the
> bibliography within the source document.
>
> But how do I do it? I've tried googling but haven't turned
I'm trying to have all my information for a org-mode document exported
to latex contained within the source document. Specifically having the
bibliography within the source document.
But how do I do it? I've tried googling but haven't turned up anything
useful. Can you help please?
Thanks
Sharon
I’m trying to use ox-pandoc to export files from org, I’ve installed pandoc and
pandoc-citeproc and copied nature.csl to the working directory, and added the
following scripts in the head of the org file
#+pandoc_options: csl:nature.csl
But when I save the org file, the feedback is
Error: (cl
How to config the bibliography style under ox-pandoc + org-ref to export docx?
I can not find citeproc in melpa.
Thank you!
Junxiang
Hi Johnny,
On 24 November 2014 at 08:08, wrote:
> I use
> #+BIBLIOGRAPHY mybibliographyfile plain
> which works, but
> #+BIBLIOGRAPHY myfirstbibliographyfile mysecondbibliographyfile plain
> does not.
Instead of #+BIBLIOGRAPHY I tend to use
#+LATEX: \bibliographystyle{plainnat}
#+LATEX: \bi
I am trying to figure out how to use multipe bibliography files in
org-mode. What I've used so far is the #+BIBLIOGRAPHY statement which
lets me enter one .bib file, but I have been unable to use more than one
file. How would one go about to achieve this?
I use
#+BIBLIOGRAPHY mybibliographyfile p
John.
Thank you for a most informative and useful post. Using your method
I've just created the "cat.org" with 14 bibliographic records! I've
amended it slightly, which I'll document in line.
John Hendy writes:
> On Mon, May 5, 2014 at 5:23 PM, Sharon Kimble
> wrote:
>> Eric S Fraga writes:
Ken Mankoff writes:
> On 2014-05-06 at 03:33, Rainer M Krug wrote:
>> Ken Mankoff writes:
>>> I've found "latexmk" to be the best tool for compiling LaTeX
>>> documents.
>>
>> This sounds very interesting. Could you please provide some details on
>> how you use latexmk? Do you use any special op
On 2014-05-06 at 03:33, Rainer M Krug wrote:
> Ken Mankoff writes:
>> I've found "latexmk" to be the best tool for compiling LaTeX
>> documents.
>
> This sounds very interesting. Could you please provide some details on
> how you use latexmk? Do you use any special options?
My ~/.latexmkrc file
Ken Mankoff writes:
> On 2014-05-05 at 19:39, John Hendy wrote:
>> If this works, someone can chime in regarding how to modify Org so
>> that it will run the necessary biber/biblatex commands so you don't
>> have to jump to a command line every time. Or perhaps that's a one
>> time thing -- maybe
On 2014-05-05 at 19:39, John Hendy wrote:
> If this works, someone can chime in regarding how to modify Org so
> that it will run the necessary biber/biblatex commands so you don't
> have to jump to a command line every time. Or perhaps that's a one
> time thing -- maybe as long as biber generates
Hi,
As Henry just noted, one of your main problem is your bibtex key. It
should not contain spaces, commas, backslashes, semicolons, or other
special characters that might mess up the syntax of the bibtex file. A
common convention is to use author:year or if you have many articles by
the same
Eric S Fraga writes:
> On Monday, 5 May 2014 at 18:08, Sharon Kimble wrote:
>
> [...]
>
>> How do I do it from the command-line please? Using what commands? I
>> can do it from inside org-mode, and I've created a test file and bib
>> references, details now.
>
> Sharon, have you not seen my oth
On Monday, 5 May 2014 at 18:08, Sharon Kimble wrote:
[...]
> How do I do it from the command-line please? Using what commands? I
> can do it from inside org-mode, and I've created a test file and bib
> references, details now.
Sharon, have you not seen my other email? Your problem is the actu
Vikas Rawal writes:
>
> Any ideas please folks, or some code to try please?
>
>
>
> I use
>
> #+LATEX_HEADER: \usepackage
> [citestyle=authoryear-icomp,bibstyle=authoryear,hyperref=true,backref=true,maxcitenames=3,url=true,backend=biber,natbib=true]{biblatex}
>
> Can you try th
Hi Sharon,
Your setup seems to only call bibtex once. I find that with biblatex
this is usually not enough to resolve references. I would call bibtex a
second time after the second run of biblatex.
All best,
Leonard
>
> Any ideas please folks, or some code to try please?
>
I use
#+LATEX_HEADER:
\usepackage[citestyle=authoryear-icomp,bibstyle=authoryear,hyperref=true,backref=true,maxcitenames=3,url=true,backend=biber,natbib=true]{biblatex}
Can you try this, and if it works, modify as you prefer.
Also, a
Leonard Avery Randall writes:
> Hi,
>
> Sharon Kimble wrote:
>
> But "page 3" of what? "input line 139" of what?
>
>
> Page 3 of the PDF and input line 139 of the .tex file.
>
> It all looks okay to me, except I cant see what the latex warnings
> relate to. Any ideas folks plea
Hi,
Sharon Kimble wrote:
But "page 3" of what? "input line 139" of what?
Page 3 of the PDF and input line 139 of the .tex file.
It all looks okay to me, except I cant see what the latex warnings
relate to. Any ideas folks please?
The most likely problem is that you have you have not c
> I'm having no success in getting the bibliography to display in my
> document, so these are my relevant settings -
> ╭
> │#+LaTeX_HEADER: \usepackage{biblatex}
> │#+LaTeX_HEADER:
> \bibliography{/home/boudiccas/.emacs.d/research/references.bib}
> │#+LaTeX_HEADER: \bibliography{references}
>
I'm having no success in getting the bibliography to display in my
document, so these are my relevant settings -
╭
│#+LaTeX_HEADER: \usepackage{biblatex}
│#+LaTeX_HEADER: \bibliography{/home/boudiccas/.emacs.d/research/references.bib}
│#+LaTeX_HEADER: \bibliography{references}
╰
and I'm usi
hello Christian,
On 07/14/2013 05:07 PM, Christian Moe wrote:
Hi,
What seems to work for most people is exporting to latex, running
bibtex, and using one of these tools to convert to ODT:
- TeX4ht (the usual recommendation)
- Pandoc
or to convert to a format that ODT imports reasonably well:
Hi,
What seems to work for most people is exporting to latex, running
bibtex, and using one of these tools to convert to ODT:
- TeX4ht (the usual recommendation)
- Pandoc
or to convert to a format that ODT imports reasonably well:
- LaTeX2RTF (and import RTF into LibreOffice)
- LaTeX2HTML (and
Hello,
I'm finishing a paper that will need to be submitted to the publisher as
MS Word. I use neither Word nor Libre/OpenOffice. I need to have a
bibliography with cross-references from the text and intended to export
from org to ODT then Word. My bibliography file is in bibtex format.
Aft
> > See, for example, http://www.indianstatistics.org/education.html.
> > \cite{vikaseducation2011} shows up as [vikaseducation2011] instead of
> > [1].
> >
> > Any idea why this is happening?
>
> Yes: code typo. Here's an update.
Thanks.
Vikas
Hello,
Fabrice Popineau writes:
> It defnitely helps a lot with Org->LaTeX files (scientific papers).
> There is one thing that is not taken into account and I wonder if there
> is an Org solution for it.
> In laTeX you can use \cite{foo1999, foo2002} . I don't think that
> current links in Org
Hello,
Vikas Rawal writes:
> I have been trying ox-bibtex.el. One problem I have is that the
> \cite{key} does not put a number with a link to the citation, but puts
> [key] in place of the number.
>
> I have tried different styles, but nothing seems to work.
>
> See, for example, http://www.ind
> > at the keyword please.
>
> Here's a new take on the problem. You need to use latest maint (or
> master) revision. What do you think?
I have been trying ox-bibtex.el. One problem I have is that the
\cite{key} does not put a number with a link to the citation, but puts
[key] in place of the nu
It defnitely helps a lot with Org->LaTeX files (scientific papers).
There is one thing that is not taken into account and I wonder if there
is an Org solution for it.
In laTeX you can use \cite{foo1999, foo2002} . I don't think that
current links in Org allow this and I don't see an easy way for i
> This works fine except that I can't place it at the keyword. How does
> one do it? I thought having a line say [BIBLIOGRAPHY] would work but
> it does not.
>
Figured it myself.
Placing the line '#+BIBLIOGRAPHY: blah blah...' at the right place did
it.
Thanks again,
Vikas
> >> By the way, where should the bibliography be inserted: at the keyword or
> >> at the end of the document (in both HTML and LaTeX)?
> >
> > at the keyword please.
>
> Here's a new take on the problem. You need to use latest maint (or
> master) revision. What do you think?
This works fine exc
Hello,
Vikas Rawal writes:
>> Actually, ox-html.el also tries to do something with bibliographies,
>> which introduces the duplication.
>>
>> We should decide if the code handling them should be in contrib/ or in
>> the various export back-ends. Since HTML handling requires external
>> programs
Vikas Rawal writes:
>> "Note for Mac OSX users:". I am using Ubuntu Precise, not OSX, and
>> TeXlive 2012, not 2010, and I got the "Executing bibtex2html failed"
>> when testing this also (even without limit:t). The only way I can
>> imagine to work around was to first run the recommended 'export
> "Note for Mac OSX users:". I am using Ubuntu Precise, not OSX, and
> TeXlive 2012, not 2010, and I got the "Executing bibtex2html failed"
> when testing this also (even without limit:t). The only way I can
> imagine to work around was to first run the recommended 'export
> TMPDIR=.' in a termina
>
>
> For this, maybe you are getting the error mentioned in the page
> https://www.lri.fr/~filliatr/bibtex2html/, in the paragraph starting
> "Note for Mac OSX users:". I am using Ubuntu Precise, not OSX, and
> TeXlive 2012, not 2010, and I got the "Executing bibtex2html failed"
> when testing
> Actually, ox-html.el also tries to do something with bibliographies,
> which introduces the duplication.
>
> We should decide if the code handling them should be in contrib/ or in
> the various export back-ends. Since HTML handling requires external
> programs, I lean towards the former.
I agr
Hi Nicolas,
Thanks a lot for taking quickly of this bib issue.
2013/5/9 Nicolas Goaziou
> Hello,
>
> Vikas Rawal writes:
>
>
> > 2. The bibliography is inserted in the exported html file above
> > the main body of org file as well as below the main body of the org
> > file. Am I doing somet
Hello,
Vikas Rawal writes:
> I am attaching my test files. I have following problems.
>
> 1. When I use limit:t, I get an error: if: Executing bibtex2html
> failed
OK, I'll have a look at it.
> 2. The bibliography is inserted in the exported html file above
> the main body of org file as well
Vikas Rawal writes:
>>
>> I attach a port of org-exp-bibtex.el (renamed ox-bibtex.el) for the new
>> export framework. Would you mind testing it?
>>
>
>
> I am attaching my test files. I have following problems.
>
> 1. When I use limit:t, I get an error: if: Executing bibtex2html failed
For t
>
> I attach a port of org-exp-bibtex.el (renamed ox-bibtex.el) for the new
> export framework. Would you mind testing it?
>
In the latex export, the bibliography is added before the main content
of the org file. The tex file shows following lines inserted before
the main content rather than aft
>
> I am attaching my test files. I have following problems.
>
Sorry, forgot to attach my files. Here they are.
Vikas
#+TITLE: Statistics on Indian Economy and Society
#+LINK_UP: data.html
#+LINK_HOME: index.html
#+OPTIONS: num:nil toc:nil
#+HTML_HEAD:
#+BIBLIOGRAPHY: bibliobase plain
*
> > I attach a port of org-exp-bibtex.el (renamed ox-bibtex.el) for the new
> > export framework. Would you mind testing it?
>
> A big thank you!
>
> Here is a quick comment. More to follow.
>
> If an org file, say temp.org, refers to a bibtex file called foo.bib,
> ox-bibtex creates two files:
>
> I attach a port of org-exp-bibtex.el (renamed ox-bibtex.el) for the new
> export framework. Would you mind testing it?
>
I am attaching my test files. I have following problems.
1. When I use limit:t, I get an error: if: Executing bibtex2html failed
2. The bibliography is inserted in the
> >
> > Yes please. I am waiting for something that will export bibtex to
> > html. With the old exporter, org-exp-bibtex used bibtex2html to
> > achieve it. But nothing similar is possible with the new exporter.
>
> I attach a port of org-exp-bibtex.el (renamed ox-bibtex.el) for the new
> export
Hello,
Vikas Rawal writes:
>> My only concern is about users expecting the keyword to be
>> recognized in other back-ends.
>
> Yes please. I am waiting for something that will export bibtex to
> html. With the old exporter, org-exp-bibtex used bibtex2html to
> achieve it. But nothing similar is
> My only concern is about users expecting the keyword to be
> recognized in other back-ends.
Yes please. I am waiting for something that will export bibtex to
html. With the old exporter, org-exp-bibtex used bibtex2html to
achieve it. But nothing similar is possible with the new exporter.
Vikas
Fabrice Popineau writes:
>> Since it is back-end dependent, why don't you use:
>>
>> #+latex: \bibliography{...}\bibilographystyle{...}
>>
>> instead?
>>
>>
> To avoid duplication.
>
> Org-bibtex/reftex need the line:
>
>
> #+bibliography: foo plain
OK. Then, it may indeed be wise to support #
> Since it is back-end dependent, why don't you use:
>
> #+latex: \bibliography{...}\bibilographystyle{...}
>
> instead?
>
>
To avoid duplication.
Org-bibtex/reftex need the line:
#+bibliography: foo plain
> You need to set `ad-return-value' somewhere, don't you?
>
>
:-) This is what I was lo
Hello,
Fabrice Popineau writes:
> Sure, I remember this thread and it is clear that the problem is very
> different when it is for LaTeX of for and HTML backend.
> However, Reftex is provided with Emacs, and it is also integrated to Org
> mode.
Since it is back-end dependent, why don't you use:
Sure, I remember this thread and it is clear that the problem is very
different when it is for LaTeX of for and HTML backend.
However, Reftex is provided with Emacs, and it is also integrated to Org
mode.
So I was trying to solve my simple problem about the bibliography keyword
this way:
(defadvi
On Mon, May 06, 2013 at 04:26:16PM +0200, Fabrice Popineau wrote:
> Is it me or is it normal that the:
>
> #+Bibliography: foo plain
>
> line is not exported by the LaTeX backend?
>
> I assume that:
> \bibliography{foo}
> \bibliographystyle{plain}
> is a decent way to handle it.
Sometime back t
Is it me or is it normal that the:
#+Bibliography: foo plain
line is not exported by the LaTeX backend?
I assume that:
\bibliography{foo}
\bibliographystyle{plain}
is a decent way to handle it.
Thanks for any comment.
--
Fabrice
57 matches
Mail list logo
