Hi Matt,
Matt Price writes:
> I'm wondering what kind of work is required to make use of org-cite and
> org-citeproc at present. In particular, I'm wondering what kinds of changes
> I'll need to make to my current setup, and whether it's worthwhile to use
> my ultra-slow coding skills to create
On Mon, Apr 6, 2015 at 2:51 PM, Richard Lawrence <
richard.lawre...@berkeley.edu> wrote:
> Hi Aaron and all,
>
> Richard Lawrence writes:
>
> > Alright, I'll try to move to json.el, and possibly change to having
> > org-citeproc generate Org markup in the meantime.
>
> Just a heads up: I've pushe
Hi Aaron and all,
Richard Lawrence writes:
> Alright, I'll try to move to json.el, and possibly change to having
> org-citeproc generate Org markup in the meantime.
Just a heads up: I've pushed some changes to my branch of Org to make
org-cite use json.el, and to add a basic Org format writer t
Rasmus writes:
> Richard: do your FSF papers in order. Or do you plan to get them in
> order?
I haven't done them yet (never had a reason to!) but I have no problems
with it and I'll get started on it.
Best,
Richard
Hi,
Richard Lawrence writes:
> Hi Eric and all,
>
> Eric S Fraga writes:
>
>> On Wednesday, 1 Apr 2015 at 08:49, Andreas Leha wrote:
>>
>> [...]
>>
>>> I am a happy biblatex user for all my 'own' documents. But (as was
>>> mentioned previously) scientific journals that accept latex submissions
Hi,
Aaron Ecay writes:
> I went round and round with myself about this, and concluded that we
> ought to keep on working on the org-citeproc approach for now (drop
> citeproc-java). But I do think someone eventually ought to reimplement
> org-citeproc based on citeproc-js, to yield something th
Hi Aaron,
Thanks for your comments, and for looking over my code!
Aaron Ecay writes:
> I’ve been (barely) following this discussion, but have been too busy to
> do any actual coding. I sat down today to try to integrate Richard’s
> branch with my work, but didn’t get very far. I think it woul
Hi Richard,
Richard Lawrence writes:
> Hi Tom and all,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>>> OK, I see, that makes things clearer. Would it make sense to have two
>>> keywords, say LATEX_CITE_STYLE and CSL_FILE or similar, so that the
>>> style can vary independently when exporting t
Hi Tom and all,
t...@tsdye.com (Thomas S. Dye) writes:
>> OK, I see, that makes things clearer. Would it make sense to have two
>> keywords, say LATEX_CITE_STYLE and CSL_FILE or similar, so that the
>> style can vary independently when exporting to LaTeX vs. non-LaTeX? I'm
>> thinking it will b
Hi Richard, hi all,
First of all, thanks very much for your work!
I’ve been (barely) following this discussion, but have been too busy to
do any actual coding. I sat down today to try to integrate Richard’s
branch with my work, but didn’t get very far. I think it would be a
waste of effort to t
Hi Rasmus,
Thanks, this is helpful. I will try to fix these things soon.
Rasmus writes:
>
>> Hmm. But the citations are all just represented as
>> nodes...surely that doesn't have to be defined elsewhere?
>
> You are right. Also, oolatex inserts citations as plain text as well. As
> I recal
Hi Eric and all,
Eric S Fraga writes:
> On Wednesday, 1 Apr 2015 at 08:49, Andreas Leha wrote:
>
> [...]
>
>> I am a happy biblatex user for all my 'own' documents. But (as was
>> mentioned previously) scientific journals that accept latex submissions
>> will require bibtex and won't support b
On Wednesday, 1 Apr 2015 at 08:49, Andreas Leha wrote:
[...]
> I am a happy biblatex user for all my 'own' documents. But (as was
> mentioned previously) scientific journals that accept latex submissions
> will require bibtex and won't support biblatex. So, I'd say that one of
> the other meth
Hi,
Richard Lawrence writes:
>> That being said, my gut feeling is that you have to define the data
>> elsewhere.
>>
>> 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
Aloha Richard,
Richard Lawrence writes:
> Hi Tom and all,
>
> Thanks for answering my questions!
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> With natbib, it is possible to give a pre-note and a post-note to the
>> citation as a whole, but not to individual citations within it. In
>> order t
Hi Tom and all,
Thanks for answering my questions!
t...@tsdye.com (Thomas S. Dye) writes:
> With natbib, it is possible to give a pre-note and a post-note to the
> citation as a whole, but not to individual citations within it. In
> order to support your syntax fully, I think BibLaTeX is needed
Rasmus writes:
> Richard Lawrence 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 th
Hi,
Eric S Fraga writes:
> On Tuesday, 31 Mar 2015 at 12:13, Richard Lawrence wrote:
>> Hi Eric and all,
>>
>> Eric S Fraga writes:
>
> [...]
>
>>> However, for some reason, libreoffice doesn't display the citations in
>>> the ODT document you have included. I have had a look at the actual ODT
Richard Lawrence writes:
> Hi Tom and all,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>>> I know next to nothing about citations in general, so please bear with
>>> me: if multi-cite support means being able to condense citations (e.g.
>>> [1-3, 5, 9]), then bibtex can do at least some of that
Richard Lawrence 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 probl
Hi Tom and all,
t...@tsdye.com (Thomas S. Dye) writes:
>> I know next to nothing about citations in general, so please bear with
>> me: if multi-cite support means being able to condense citations (e.g.
>> [1-3, 5, 9]), then bibtex can do at least some of that
>> (e.g. http://texblog.org/2007/05/
On Tuesday, 31 Mar 2015 at 12:13, Richard Lawrence wrote:
> Hi Eric and all,
>
> Eric S Fraga writes:
[...]
>> However, for some reason, libreoffice doesn't display the citations in
>> the ODT document you have included. I have had a look at the actual ODT
>> file and it looks fine. Can you su
Aloha all,
Nick Dokos writes:
> Richard Lawrence writes:
>
>> However, there are a couple of other scenarios to think about:
>>
>> 1) Some people may still need to use plain BibTeX. Generating LaTeX
>> that is intended to be processed with BibTeX, as opposed to BibLaTeX, is
>> a little trickie
Richard Lawrence writes:
> However, there are a couple of other scenarios to think about:
>
> 1) Some people may still need to use plain BibTeX. Generating LaTeX
> that is intended to be processed with BibTeX, as opposed to BibLaTeX, is
> a little trickier, because (IIUC) BibTeX does not support
Hi Eric and all,
Eric S Fraga writes:
> On Saturday, 28 Mar 2015 at 10:53, Richard Lawrence wrote:
>> I thought I should send an update to let you know that org-citeproc [1],
>> the command-line citation processing tool I've been working on, now
>> supports multi-cites. I believe that means it
On Saturday, 28 Mar 2015 at 10:53, Richard Lawrence wrote:
> Hi everyone,
>
> I thought I should send an update to let you know that org-citeproc [1],
> the command-line citation processing tool I've been working on, now
> supports multi-cites. I believe that means it is now capable of
> processin
26 matches
Mail list logo
