Hi Marcin,
Marcin Borkowski mb...@mbork.pl writes:
as I mentioned, I'm writing a simple exporter. However, I stumbled on
something apparently simple. How to get the current list level within
org-whatever-item transcoder?
I ran into this problem once; the solution I found was to just walk
Hi Marcin and all,
Marcin Borkowski mb...@mbork.pl writes:
after a short discussion in a recent thread, I have a serious technical
question.
Assume that (for some reason) I want to write an Org-mode exporter which
won't be GPL'd. (Use-case: having written a few custom exporters, I'm
Hi Edward,
Edward Guyatt edwardguy...@gmx.co.uk writes:
I like to be reminded to check my post on Mondays and Thursdays, every
week. When I've done it on Monday, I mark it 'DONE' so that I can stop
org-mode reminding me until Thursday. Here's how I used to achieve
this:
*** URGENT [#A]
Hi Matt,
Matt Price mopto...@gmail.com 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
Hi David,
David Dynerman da...@block-party.net writes:
Sorry in advance, this might be more of a git question than an org-mode
question, but I thought someone on this list might know the answer.
Is it possible to conditionally gitignore certain files based on files
that are being tracked?
Hi Aaron and all,
Richard Lawrence richard.lawre...@berkeley.edu 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
Hi Jude,
Jude DaShiell jdash...@panix.com writes:
Do those files by default conform to screen reader accessibility
standards or can such files be made to conform to screen reader
accessibility standards?
I don't actually know anything about this, but the quick answer is: Org
uses LaTeX to
Rasmus ras...@gmx.us 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 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 be
Hi Rasmus,
Thanks, this is helpful. I will try to fix these things soon.
Rasmus ras...@gmx.us writes:
Hmm. But the citations are all just represented as text:p
nodes...surely that doesn't have to be defined elsewhere?
You are right. Also, oolatex inserts citations as plain text as well.
Hi Eric and all,
Eric S Fraga e.fr...@ucl.ac.uk 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
Hi Aaron,
Thanks for your comments, and for looking over my code!
Aaron Ecay aarone...@gmail.com 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.
Rasmus ras...@gmx.us writes:
Richard Lawrence richard.lawre...@berkeley.edu 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
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.
Hi Eric and all,
Eric S Fraga e.fr...@ucl.ac.uk 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
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.
}
}
ORG-CITEPROC TESTS
Richard Lawrence
Table of Contents
─
1 Org markup
.. 1.1 Simple citations
. 1.1.1 Parenthetical
. 1.1.2 In-text
. 1.1.3 With prefix and suffix
Hi Randomcoder,
Randomcoder randomcod...@gmail.com writes:
Is there an easier solution to hiding the :PROPERTIES: drawer by default ?
I'm not sure that a solution is needed. In my setup (Org master branch,
Emacs 23), the PROPERTIES drawer is always folded by default. I've
never done anything
Marcin Borkowski mb...@wmi.amu.edu.pl writes:
1. Did you know about the savetrees package by Scott Pakin
(http://www.ctan.org/pkg/savetrees)? From the description:
Only vaguely.
2. Would you find it useful when producing PDF files other that
scientific articles (using Org-mode or not)?
Hi Rainer,
Rainer M Krug rai...@krugs.de writes:
I figured out that I can not search for text in the link.
Thins is quite annoying, especially as I even thought of opening the
file in another texteditor, search for the string, and save it again.
As an example: if this link is in an
Hi Matt,
Matt Price mopto...@gmail.com writes:
Just a note about Zotero: I think for most of us, the reason to export
into ODT and/or DOC is to circulate a paper either for review or
collaboration. Either case will likely involve some revision to citations,
which would ideally be handled
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
I ask because in that kind of context, I think it is generally going to
be more useful to deal with citation objects as a whole. I am not sure
we will want to treat citation-references as individual objects which
are themselves exported;
Hi Andreas,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
2. The non-LaTeX exports
These are all treated the same and will contain just text, that is
produced to mimic LaTeX's output to some extent?
Well, that depends on what you mean by `just' text. Citations can still
contain
Hi Nicolas,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
`org-element-context' never returns contents of objects or elements.
I'm sure there is something simple I am misunderstanding here about how
nested objects work...can you enlighten me?
You could do the following
(let ((citation
#+OPTIONS: toc:nil todo:t |:t
#+TITLE: Org-Citeproc Test
#+AUTHOR: Richard Lawrence
#+LANGUAGE: en
#+BIBDB: bibtex ~/Documents/philosophy/dissertation/build/dissertation.bib
#+CSL_FILE: /tmp/chicago-author-date.csl
Citations and Bibliography are supported using org-citeproc
Hi Aaron and all,
Richard Lawrence richard.lawre...@berkeley.edu writes:
I'll take some time this weekend to see if I can wire this together with
the Elisp Aaron wrote for the Org exporter side.
I've had some success with this. I would not say that my efforts are
complete yet, but I thought
Hi Nicolas,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Agreed. I introduced yet another syntax change in wip-cite branch.
Now there are two separate objects citation and citation-reference.
So the following multicite
[cite:prefix; pre @a post; @b]
is parsed like
(citation
Hi Aaron and all,
Richard Lawrence richard.lawre...@berkeley.edu writes:
What version of citeproc-hs are you using? The version under that
name is no longer maintained, and I had some trouble getting it to
build.
I am in fact using the version under that name (I have not had trouble
a browser) installed
2015ko martxoak 10an, Richard Lawrence-ek idatzi zuen:
I have actually been working on the same problem, using citeproc-hs as
the CSL processor instead of citeproc-java.
This is an interesting approach. What version of citeproc-hs are you
using? The version under
Hi Vaidheeswaran,
Vaidheeswaran C vaidheeswaran.chinnar...@gmail.com writes:
JabRef exporter now supports:
a) Multicites
b) Prefixes and Suffixes
c) Textual and Parenthetical styles.
d) Numeric and Footnote type styles.
Thanks very much for your work on this! It's great to see the
Hi Aaron and all,
Aaron Ecay aarone...@gmail.com writes:
I’ve pushed an update to my branch. The major change is to use
citeproc-java for the generation of the bibliography and the parsing of
names.
That is awesome! Thank you for your work.
The former is straightforward. For the latter,
Eric S Fraga e.fr...@ucl.ac.uk writes:
On Tuesday, 10 Mar 2015 at 09:50, Rasmus wrote:
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Since this one is not much more intrusive than the previous one, we
could as well drop @key in favor of @{key}.
It seems like a moderately dear price to pay
Hi Rasmus,
Thanks, your post was very informative.
Rasmus ras...@gmx.us writes:
...
Can you turn off the automatic addition of commas in BibLaTeX by setting
something in the preamble?
Preamble or using \AtNextCite
If so, would that be the right solution here? It might be easier to
Hi Tom and all,
Thomas S. Dye t...@tsdye.com writes:
Richard Lawrence richard.lawre...@berkeley.edu writes:
But my opinion probably shouldn't count for much on this
point, because I don't use a citation manager myself (I use org-bibtex),
and I write my own keys.
Oh my. This is a lot
Hi Tom and all,
Thomas S. Dye t...@tsdye.com writes:
The problem is limited to the shortcut citations and doesn't affect the
[cite: ...] form, which can be expected to work without modification
wherever it is placed IIUC.
Actually, it occurs to me now that this might even affect the [cite:
Rasmus ras...@gmx.us writes:
Richard Lawrence richard.lawre...@berkeley.edu writes:
Suppose you often write citations like:
[cite: See @Doe99, and references therein, for more.]
[...] and rendered like:
See Doe (1999), and references therein, for more.
This is slightly OT
Hi Eric and all,
Eric S Fraga e.fr...@ucl.ac.uk writes:
On Monday, 9 Mar 2015 at 09:05, Richard Lawrence wrote:
Another option would be to allow clause-ending punctuation in all keys,
but introduce some kind of optional syntax to express `this key ends
No, please no! I would say
Hi Tom and all,
t...@tsdye.com (Thomas S. Dye) writes:
As I see it, the choice boils down to the relative benefit of citation
shortcuts vs. the limitation of requiring authors to configure the
citation manager so it doesn't produce a key ending in punctuation (or
your solution that uses
Vaidheeswaran C vaidheeswaran.chinnar...@gmail.com writes:
On Friday 06 March 2015 11:51 PM, Richard Lawrence wrote:
Vaidheeswaran C vaidheeswaran.chinnar...@gmail.com writes:
I got the subject and also text wrong. (But I hope my intention was
clear.) I am really looking for EXISTING
Vaidheeswaran C vaidheeswaran.chinnar...@gmail.com writes:
On Friday 06 March 2015 11:39 PM, Richard Lawrence wrote:
Hi Vaidheeswaran,
Vaidheeswaran C vaidheeswaran.chinnar...@gmail.com writes:
The following combination works when passed through the LaTeX/PDF
exporter. It doesn't work
Hi Vaidheeswaran,
Vaidheeswaran C vaidheeswaran.chinnar...@gmail.com writes:
The following combination works when passed through the LaTeX/PDF
exporter. It doesn't work when the cite syntax is switched to the new
one.
\cite{center_for_history_and_new_media_zotero_}
Is that a realistic
Hi Vaidheeswaran,
Vaidheeswaran C vaidheeswaran.chinnar...@gmail.com writes:
I got the subject and also text wrong. (But I hope my intention was
clear.) I am really looking for EXISTING in-text CSL styles.
Rasmus pointed you to a relevant style:
Avram Lyon ajl...@gmail.com writes:
I know that citeproc-js has tried to be engine-agnostic, so perhaps it can
work with Guile.
It looks like I was too quick. Although the homepage makes it seem like
Guile supports JS, the manual says:
ECMAScript was not the first non-Schemey language
Hi Rainer,
Rainer Stengele rainer.steng...@online.de writes:
Opening the TODO shows all the CLOCK lines shown, but my focus is on
text below the CLOCK lines. ...
Anybody else uses multiple LOGBOOK blocks that way? Other ideas how to work?
Any chance to get this regarded as an enhancement
Hi Rasmus and all,
Rasmus ras...@gmx.us writes:
Vaidheeswaran C vaidheeswaran.chinnar...@gmail.com writes:
I am complaining about how org-element.el behaves.
Oh, you are right. _ is only allowed as the first character, as you
probably saw. See
Rasmus ras...@gmx.us writes:
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Richard Lawrence richard.lawre...@berkeley.edu writes:
Sorry, I may not have emphasized this enough, but in the grammar, I wrote:
- A KEY optionally begins with `-', and obligatorily contains
Hi Nicolas,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Oh, I did not realize there were outstanding issues with this. I
remember Rasmus not liking `'. I'm fine with changing it, though I
cannot think of a better symbol. Does someone think we should not have
a way of indicating that a
Hi Avram,
Avram Lyon ajl...@gmail.com writes:
On Mon, Mar 2, 2015 at 7:16 PM Richard Lawrence
richard.lawre...@berkeley.edu wrote:
Is there any reason to go with citeproc-java over a different CSL
implementation, like citeproc-js or pandoc-citeproc? I am a little
nervous about shelling
Hi Aaron,
Aaron Ecay aarone...@gmail.com writes:
Another tangentially related issue is what does (org-element-context)
return when point is in a multi-citation. It would be nice if it
returned the citation daughter, rather than the wrapping citations
element. This would make implementing
Hi Nicolas,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
To support multi cites, we must first decide how the parsed will present
information, i.e., what are the properties in the following case
[cite:pre; pre1 @k1 post1; pre2 @k2 post2; post]
I was thinking that this should yield a
Aaron Ecay aarone...@gmail.com writes:
It would also be possible to just use an external program like
citeproc-java. WDYT?
I agree with Rasmus that using an external tool is the preferred way to
go here. I don't think introducing a dependency is really a problem, so
long as we choose the
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
The first issue is that the parser includes trailing punctuation in
“bare” @key citations. So the following does not work as expected (the
:key includes the period): “This was demonstrated most recently by
@Smith2015.” I’m not sure what the
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Richard Lawrence richard.lawre...@berkeley.edu writes:
That would be wonderful! Will you publish a patch or, better, a branch
somewhere, even if it's not ready for master?
I created a new branch: wip-cite. It introduces support for @key
[@key
Hi Stefan,
Stefan Nobis stefan...@snobis.de writes:
Aaron Ecay aarone...@gmail.com writes:
I count roughly 50 commands in sections 3.7.1 – 3.7.6 of the
biblatex user’s manual (version 2.9a of 24/06/2014). Some of these
are quite esoteric, of course, but they are all provided.
There are
Vaidheeswaran C vaidheeswaran.chinnar...@gmail.com writes:
If you need help with ODT/JabRef integration, I am willing to lend a
hand. (Only thing is) I would expect that someone hand-hold me wrt
what one wants in the final exporter on a case-by-case basis. I would
rather build bottom-up,
Vaidheeswaran kjambunat...@gmail.com writes:
We haven't really discussed how styles should be specified (yet), or the
formatting of bibliographies. But we have been discussing a syntax that
lets you specify those formatting properties which commonly differ
between individual citations.
Vaidheeswaran C vaidheeswaran.chinnar...@gmail.com writes:
But whatever style is chosen, I would still think that the fact that the
citation is in-text rather than parenthetical, and that it has a prefix
and suffix, should be represented in the output.
1. When you choose 'style' (Chicago
Hi Vaidheeswaran,
Thanks for your input about citations!
Vaidheeswaran vaidheeswaran.chinnar...@gmail.com writes:
Those working on the citation syntax should make it clear that the
lowest common cite syntax does NOT also IMPOSE (or GUARANTEE) a
specific style on the produced document.
When
Garrett Fuller garrett...@gmail.com writes:
I am still learning how to use emacs. When I was learned about org mode, I
was really excited. I found it very difficult to extract the basic usage of
org mode from the resources available on the website. The resources
available are both plentiful
Hi Samuel,
Samuel Wales samolog...@gmail.com writes:
basically, i am concerned about syntax creep in the big picture and
its downstream consequences. for example, it's more efficient to
support, and for the user to remember, a single general syntax than a
whole bunch of special syntaxes.
Hi Melanie,
Melanie Bacou m...@mbacou.com writes:
Just want to point out RMarkdown/Pandoc implementation of
bibliographies and citations here
http://rmarkdown.rstudio.com/authoring_bibliographies_and_citations.html
Thanks for joining the discussion! Actually, the Pandoc/RMarkdown
syntax was
Hi Nicolas,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
AFAICT, the most advanced use of citations is Thomas', and he is
basically only using subtype. So I'm pretty confident that 99.9% of
users will be fine with only these subtypes.
...
Again, I don't think we need {:key val} at the
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
I wasn't clear. Subtype should be interpreted by back-ends means it has
no impact on syntax. However a user should be able to dictate what the
back-end should do with it, much like `org-add-link-type'.
A new library, e.g. org-cite.el would
Hi Nicolas and all,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Richard Lawrence richard.lawre...@berkeley.edu writes:
Actually, your post has convinced me that it may be worth allowing some
explicit name for a type in the [cite: ...] part of the syntax, although
I am still leery about
Hi Tom,
t...@tsdye.com (Thomas S. Dye) writes:
Thanks for your thoughtful responses and your work on the citation
syntax. My author concerns have been addressed in this thread and I
look forward to development now. I'm +1 and optimistic about the switch
from home-brew links to citations in
Hi Rasmus,
Rasmus ras...@gmx.us writes:
Richard Lawrence richard.lawre...@berkeley.edu writes:
Basically, I think you could ignore the distinctions that the [cite:
...] syntax is capable of expressing, and just write all your citations
like:
[cite: See @Doe99 for more on this point
Hi Tom,
t...@tsdye.com (Thomas S. Dye) writes:
I want a syntax that recognizes arbitrary citation commands because I
write in Org mode for publication. You want a syntax that recognizes a
few commands that it might be possible to support in Org mode backends,
some of which are tied loosely,
Hi Eric,
Eric S Fraga e.fr...@ucl.ac.uk writes:
+1 emphatically.
Thanks!
With respect to the bibliography database, for completeness, I would
like to see linking with org-bibtex data instead of bibtex etc.
Me too, as I keep all my reference data in org-bibtex. I suggest we
discuss the
Hi John,
I don't have time for a long reply but I wanted to express a couple
points of agreement:
John Kitchin jkitc...@andrew.cmu.edu writes:
I think the usual suspects reftex, helm-bibtex, and probably ebib
could be taught to output most of this syntax for whatever type, and
they could
Hi Nicolas,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Time for another crazy idea. Last one on my side for today
[cite ...] [(cite) ...] [Cite ...] [(Cite) ...]
It should solve the :capitalize issue.
I am OK with this if it is important, though I am a little hesitant.
In the last
Hi Tom,
t...@tsdye.com (Thomas S. Dye) writes:
0
A syntax that relegates citation commands to an extension that might not
export properly in future versions of Org mode isn't useful in my work.
Sorry to disappoint!
I tried really hard to represent in the [cite: ...] syntax all the
Hi Rasmus,
Rasmus ras...@gmx.us writes:
0
Parts I like:
1) a parenthetical citation for a single work with no prefix and
suffix may be written by just surrounding the key with brackets,
like: [@Doe99].
2) an in-text citation for a single work with no prefix and suffix
Hi Nicolas,
Thanks for your comments. A couple of replies follow.
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
The difference between parenthetical and in-text citations is
expressed using parentheses around the /first/ citation key. A
parenthetical citation has such parentheses around
, a revised proposal
#+DATE: 2015-02-14 Sat
#+AUTHOR: Richard Lawrence
#+EMAIL: richard.lawre...@berkeley.edu
#+LANGUAGE: en
#+SELECT_TAGS: export
#+EXCLUDE_TAGS: noexport
* Citation syntax
** Requirements
A citation is a textual reference to one or more individual works,
together with other information
...and of course, immediately sending, I noticed a small problem in the
grammar:
Richard Lawrence richard.lawre...@berkeley.edu writes:
- A PARENTHETICAL-CITATION is either a SIMPLE-PARENTHETICAL or a
CITATION-LIST whose first INDIVIDUAL-REFERENCE is a
PARENTHESIZED-KEY
Stefan Nobis stefan...@snobis.de writes:
Richard Lawrence richard.lawre...@berkeley.edu writes:
I know these commands are convenient, and that not having them would
introduce this class of errors, but the question is whether they are
so important that it's worth providing an equivalent
Hi Nicolas and all,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
If year, or author, are needed, I suggested to append some optional
parameter to the key, e.g.,
[cite: pre @key:year post]
I proposed exactly this earlier in the thread, but then I came to the
conclusion that we shouldn't
Hi Stefan,
Stefan Nobis stefan...@snobis.de writes:
Richard Lawrence richard.lawre...@berkeley.edu writes:
Rasmus ras...@gmx.us writes:
Citation types for extracting parts:
citeauthor, citetitle, citeyear, citedate, citeurl,
As I've said in other posts, I think maybe we should
Hi Tom and all,
t...@tsdye.com (Thomas S. Dye) writes:
Richard Lawrence richard.lawre...@berkeley.edu writes:
Conceptually, something like `@key:year' isn't a citation, but merely
indirection, because it doesn't actually provide the reader of the
rendered document enough information to look
Rasmus ras...@gmx.us writes:
So, the (opinionated) useful defaults in biblatex are:
cite(s), parencite(s), footcite(s), texcite(s), fullcite,
footfullcite, nocite
So that is to say we need to be able to express the following
distinctions (did I miss anything?):
- in-text vs.
Hi John and all,
John Kitchin jkitc...@andrew.cmu.edu writes:
I think the critical point is that the syntax must be user
extendable. It should be possible to add these different types, even if
most people do not use them. Otherwise, links will continue to be used
anyway.
I completely agree.
Hi Tom and all,
t...@tsdye.com (Thomas S. Dye) writes:
IIUC, Org mode citation syntax needs to capture four pieces of
information for an *individual* citation: a =key= into one or more
stores of bibliographic information; a =citation-command= that is
understood by the =citation-style=
Hi John and all,
On Sun, Feb 8, 2015 at 1:46 AM, John Kitchin jkitc...@andrew.cmu.edu wrote:
My only concern is that it remains possible to support this relatively
full set of citation options on export:
...
which we are currently able to do. I never type any of those in, org-ref
does it
Hi Nicolas and all,
On Sun, Feb 8, 2015 at 1:58 AM, Nicolas Goaziou m...@nicolasgoaziou.fr wrote:
- in-text citation
[KEY] or [KEY suffix]
[@item1] or [@item1 p. 30] or [@item1 p. 30, with suffix]
- out-text citation
[cite: prefix? key suffix?; prefix2? key2 suffix2?
Hi Nicolas,
I just want to say thanks for continuing the conversation, by the way:
I know this thread has gotten long, but I'm glad people are still
paying attention, and Nicolas, your opinion counts for a lot.
On Sat, Feb 7, 2015 at 2:43 PM, Nicolas Goaziou m...@nicolasgoaziou.fr wrote:
What
Hi Nicolas and all,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Richard Lawrence richard.lawre...@berkeley.edu writes:
Thanks for this reverse engineering.
Specifically I think we need the following categories, all of which
would be objects:
- key
- prefix / pre-text
- suffix
Hi Nicolas,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Also, AFAIU, the syntax for valid citations is not defined explicitly so
far. For example, I don't think it was discussed if any subset of Org
objects (e.g., macros or bold text) is allowed in a citation.
This is a good question
Erik Hetzner e...@e6h.org writes:
On Wed, 4 Feb 2015 at 07:59:46 PST,
Richard Lawrence richard.lawre...@berkeley.edu wrote:
The idea is, a citation like As Doe says in @Doe99:title, ... should
render like As Doe says in /The Title/, ..., not like As Doe says in
Doe (1999), ..., even
Erik Hetzner e...@e6h.org writes:
The ideal would be if citeproc would take care of proper formatting
of all such citation types, given just an ordered list of the fields
that should appear. I don't know if CSL supports this, though; do
you?
I’m not entirely sure what you mean. The authors
Hi Eric and all,
Eric S Fraga e.fr...@ucl.ac.uk writes:
On Tuesday, 3 Feb 2015 at 11:35, Rasmus wrote:
I'm enjoying following this thread. I look forward to the community
converging on some solution.
Me too!
For me, any solution will likely do just fine as my use of citations is
quite
Hi Erik and all,
Erik Hetzner e...@e6h.org writes:
On Mon, 2 Feb 2015 at 20:41:06 PST,
Richard Lawrence richard.lawre...@berkeley.edu wrote:
The only reason I proposed anything else was that it seemed like other
people already know that they need more than the Pandoc syntax provides.
I
Hi Rasmus and all,
Thanks for your comments!
Rasmus ras...@gmx.us writes:
** Backend-agnostic formatting properties
*** Selecting specific fields
Selecting specific fields to display could be done by appending field
names to cite keys after colons, much like Org tags:
#+BEGIN_QUOTE
[See
Hi Erik and all,
Erik Hetzner e...@e6h.org writes:
I am really, really glad to see people discussing citations in
org-mode. But I have some concerns about this proposal.
Before extensions are proposed to the pandoc format, I think it is
important to understand how flexible the combination
t...@tsdye.com (Thomas S. Dye) writes:
You and others are advocating a separate syntax for links and citations,
which might indeed be the way to go. I can see it being much nicer than
the current state of affairs with Org mode links. The downside is that
it will mean learning another set of
Hi Rasmus and all,
Rasmus ras...@gmx.us writes:
Richard Lawrence richard.lawre...@berkeley.edu writes:
Within a citation, each reference to an individual work needs to be
capable of containing:
1) a database key that references the cited work
2) prefix / pre-text
3) suffix / post
: Richard Lawrence
* Introduction
In brief, the proposal is:
1. Use the Pandoc syntax for basic, inline citations.
2. Extend the Pandoc syntax modestly to accommodate backend-agnostic
formatting of inline citations.
3. Also allow non-inline citation definitions, with a syntax
comparable to non
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Richard Lawrence richard.lawre...@berkeley.edu writes:
...so the first step for introducing citation syntax to Org should be
compiling a list of all the things such a syntax should represent.
See also
http://permalink.gmane.org
Hi John and all,
John Kitchin jkitc...@andrew.cmu.edu writes:
As for the first problem, I think a good case can be made for adding new
syntax to Org to represent citations, instead of repurposing/extending
existing syntax (most notably, the link syntax).
I think links are remarkable
Hi all,
I wanted to continue the discussion that began in this thread about
adding citation support to Org:
http://thread.gmane.org/gmane.emacs.orgmode/94352/focus=94412
Here are some thoughts I have after reviewing that discussion:
1) Lots of people seem to need/want better support for
Rasmus ras...@gmx.us writes:
IMO we /need/ to add proper citation support to Org, preferably with a
real syntax rather than these link-solutions and with good backend
support (bibtex Zotero for starters, I guess).
...
/Proper/ citation support (not links) is, IMO, the last thing that is
101 - 200 of 332 matches
Mail list logo
