Dear All,
On Wed, 28 Aug 2024 at 10:41, Sharon Kimble
wrote:
> I now have
> ** Chapter 2
> blah
> ** Chapter 2
> blah de blah
> How can I get these new chapters to autorenumber themselves please, so that
> they will show Chapter 2, Chapter 3
one way of doing the required renumbering would be p
Dear All,
> Sébastien Gendre writes:
> > And I search for example of online documentation made with Org-mode. As
> > inspirations.
AFAIU, the online documentation of the Magit and Borg Emacs packages
by Jonas Bernoulli were also made using Org (probably with the texinfo
exporter), see https://ma
Dear All,
On Sun, 28 Jul 2024 at 21:22, Orm Finnendahl
wrote:
>
> Trying to define a file local filter doesn't work:
>
> #+BIND: org-export-filter-final-output-functions (hiho)
> #+BEGIN_SRC emacs-lisp :exports results :results none
> (defun hiho (s backend info)
> (message "HiHo")
> s)
Dear All,
On Sun, 21 Jul 2024 at 12:15, Sébastien Gendre wrote:
> I have seen if a special keyboard shortcut is needed after selecting a
> key to cite, but neither in the documentation or the function docstring
> I found it.
> Any idea ?
I think it depends on the used completion system, but one
A quick correction: instead of "BibLaTex title fields" I should have written
"BibTeX or biblatex title fields".
best wishes,
András
On Mon, 8 Jul 2024 at 14:56, András Simonyi wrote:
>
> On Mon, 8 Jul 2024 at 12:57, Max Nikulin wrote:
> > On 06/07/2024 16:59
On Mon, 8 Jul 2024 at 12:57, Max Nikulin wrote:
> On 06/07/2024 16:59, András Simonyi wrote:
> If a style does not specify conversion or use "title" then result should
> be in title case. Title case is recommended for BibTeX databases. If you
> pass string in title case th
Dear All,
(sorry for the late reply again)
On Fri, 21 Jun 2024 at 12:27, Max Nikulin wrote:
>
> On 19/06/2024 16:27, András Simonyi wrote:
> > Of course it could be checked whether
> > a CSL style contains explicit instructions about how to format titles
> > and skip sen
Dear All,
On Wed, 19 Jun 2024 at 16:35, Ihor Radchenko wrote:
> Thanks! I have no further comments.
> Feel free to install the patch.
Thanks, I'have applied the patch to main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=782f6c33beed8d7baac9549b94a6a08040eba838
best wishes,
Dear Ihor and Max,
thanks for the feedback and apologies for responding that late.
On Wed, 15 May 2024 at 13:48, Max Nikulin wrote:
> Is it possible to keep title formatting from .bib files till it becomes
> known that specific style requires sentence case for particular entry
> type? I had a h
Dear Ihor,
thanks for asking -- unfortunately, I've been absurdly busy in the
last few weeks but it's getting better now, so I'm going to respond
shortly with a new, hopefully final, version.
best wishes,
András
On Mon, 17 Jun 2024 at 13:37, Ihor Radchenko wrote:
>
> Ihor Radchenko writes:
>
> >
Dear All,
On Sat, 11 May 2024 at 19:24, Ihor Radchenko wrote:
>> > since bibtex and biblatex requires title fields to be in title case
> Are you sure? AFAIK, bibtex and biblatex (depending on the bibstyle)
> does not care about capitalization and instead applies its own, unless
> the title expli
Dear All,
On Sat, 11 May 2024 at 11:55, Ihor Radchenko wrote:
> See the attached updated version of the patch with all your comments
> addressed.
Thanks Ihor, the patch looks good to me now!
best wishes,
András
Dear All,
since bibtex and biblatex requires title fields to be in title case
but CSL assumes that they are in sentence-case, citeproc-el converts
title fields in bib(la)tex bibliography databases into sentence-case
before processing them except for entries with an explicit non-English
langid valu
Dear Ihor,
thanks for working on this, I agree that the current version,
especially the introduction, was too technical, so that is a very
good direction to take. Some comments on the proposed changes:
> Org mode will gather citation metadata from =#+bibliography= database
> and use it to typese
Thanks Ihor, I have pushed it to main.
best wishes,
András
On Sun, 5 May 2024 at 14:13, Ihor Radchenko wrote:
>
> András Simonyi writes:
>
> > there is a rather peculiar set of numeric citation styles (perhaps
> > most famously, that of Nature's) which sets citation
Dear All,
there is a rather peculiar set of numeric citation styles (perhaps
most famously, that of Nature's) which sets citation numbers in
superscript -- similarly to footnote numbers, these citations should
not have any space between them and the previous word. The attached
patch checks during
Dear All,
On Wed, 27 Mar 2024 at 04:17, Christian Wittern wrote:
> This paper is discussing and comparing translations to the same text. So
> when I mention publications in the text, I want to have the keyword to
> be the translator, rather than the author.
I think your best bet is modifying (t
Dear All,
On Sun, 14 Jan 2024 at 06:39, William Denton wrote:
> > While we're talking about citations, I'm stuck on something else. If I run
> > "C-c C-x @" to insert a citation into a file, I'm shown a list of
> > bibliography entries and I can go up and down and hit RET on any I chose.
> >
Dear All,
On Sun, 24 Dec 2023 at 19:12, Ihor Radchenko wrote:
>
> Pedro Andres Aranda Gutierrez writes:
>
> > Just to submit a small addition to the org-mode documentation. This not
> > being the best of times, I would have needed this pointer,
>
> Thanks!
> Applied, onto main, adding a commit m
Dear All,
On Thu, 23 Nov 2023 at 17:54, William Denton wrote:
> I think I've found another bug with citations, this time about filtering on
> keywords when printing bibliographies with the CSL processor. Either that
> or I'm wrong about how it works.
Thanks for reporting, I've managed to repro
Dear All,
On Wed, 25 Jan 2023 at 12:53, Ihor Radchenko wrote:
> Confirmed, after replacing the .bib key with
> abnarQuantifyingAttentionFlow2020a.
>
> András, may you take a look?
First of all, apologies for reacting that late, unfortunately, I've
had way less time to work on Org-mode and citep
Dear All,
On Sat, 25 Feb 2023 at 18:19, M. ‘quintus’ Gülker
wrote:
> Not yet, and it certainly looks nice, but the CSL style I use uses
> footnotes, and those are quite verbose. Rendering them (or rather, their
> content) into the text would expand it even more.
there is no assumption that the
Dear All,
On Thu, 19 Jan 2023 at 11:15, M. ‘quintus’ Gülker
wrote:
> That is, the macro has to work both in a citation and in> normal text. Even
> if a @@csl: construct would be ignored in normal text,> I cannot see how to
> write the macro then, because something like
>
> #+MACRO: name @@
Dear All,
On Wed, 25 Jan 2023 at 16:10, Ihor Radchenko wrote:
> If we do not specify a bibliography style, LaTeX export will fail.
> With the attached patch, the following simple-minded Org document will
> export without errors:
Thanks, I think that is an important improvement -- when I tried t
Dear All,
On Sun, 22 Jan 2023 at 12:15, Ihor Radchenko wrote:
> Also, note that `org-cite-biblatex--package-options' combines INITIAL
> option list from the \usepackage declaration already present with
> options dictated by STYLE. However, only certain options are considered.
> After applying yo
Dear All,
On Thu, 19 Jan 2023 at 09:35, M. ‘quintus’ Gülker
wrote:
> I am not sure this targets the usecase I am pursuing, which is to use
> macros to produce @@latex: escape constructs in order to have small-caps
> markup in the citation footnotes:
>
> #+MACRO: name @@latex:\textsc{$1}h
Dear All,
apologies for replying that late. If I understand the situation
correctly, we could handle the question of allowing macros in
citations independently of the handling of other constructs, because
macros are resolved before processing citations, so they have no
effect on the input of Citep
Dear All,
first of all, sorry for replying that late.
On Tue, 20 Dec 2022 at 11:46, Christian Moe wrote:
> Arbitrary sexps would give us more flexibility. Alternately, one could
> achieve more or less the same by letting :filter collect any additional
> arguments and pass them as &rest to the us
Dear All,
On Thu, 29 Dec 2022 at 11:14, Ihor Radchenko wrote:
> LGTM!
> Feel free to push upstream.
thanks Ihor, I've pushed the changes to main as commit
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=29103fc60
best wishes,
András
Dear All,
I have attached a new version of the patch with added ascii "illustrations".
best wishes,
András
On Tue, 13 Dec 2022 at 20:03, András Simonyi wrote:
>
> Dear All,
>
> On Tue, 13 Dec 2022 at 17:07, Timothy wrote:
>
> > Perhaps an ASCII approximation in an
On Tue, 20 Dec 2022 at 09:22, Denis Maier wrote:
> allowing lambda expressions would
> probably be quicker to implement, and it would also allow for predicates
> not anticipated by DSL designers.
Yes, on the other hand, we will have to be very careful with regard to
security if we choose this ro
... I've forgotten to add that another (probably more user friendly)
option would be to design and implement some kind of filtering DSL.
András
On Mon, 19 Dec 2022 at 23:05, András Simonyi wrote:
>
> Dear All,
>
> On Mon, 19 Dec 2022 at 15:49, Christian Moe wrote:
>
>
Dear All,
On Mon, 19 Dec 2022 at 15:49, Christian Moe wrote:
> Refinements welcome. I'm especially wondering what would be an elegant
> way to generalize this for more languages without defining a predicate
> for each language (given that we cannot pass the language as an
> additional argument i
Dear All,
On Tue, 13 Dec 2022 at 17:07, Timothy wrote:
> Perhaps an ASCII approximation in an example block could work? Even if it’s
> exaggerated to give the idea.
yes, I'm also thinking of first trying to produce something in ASCII
as the docstring will probably need it anyway,
and we can thi
Dear All,
On Mon, 12 Dec 2022 at 10:07, Ihor Radchenko wrote:
> Would it be possible
> to provide an example of bibliography output and how it is affected by
> the new custom variables?
> In the news, it could be example image indicating the distances,
Hm, I tried to find an image in the ORG-NE
nko wrote:
>
> András Simonyi writes:
>
> >> Also, it would be nice to describe CSL usage and tweaks in the manual.
> >
> > Time permitting I may try to add something, but wouldn't it be a
> > problem if the CSL export processor was discussed in much more
Dear All,
On Mon, 7 Nov 2022 at 03:47, Ihor Radchenko wrote:
> Please, document the new customization in ORG-NEWS.
Dear Ihor, thanks for the comments! I'm going to update the NEWS file
shortly in a new version of the patch.
> Also, it would be nice to describe CSL usage and tweaks in the manu
Dear All,
the attached patch substantially improves the formatting of CSL-based
bibliographies in LaTeX export by supporting in-style formatting
settings that were previously ignored, most importantly,
'second-field-align', which is typically used for numeric styles such
as ieee.csl.
I'm sending
Dear All,
On Wed, 2 Nov 2022 at 07:28, Ihor Radchenko wrote:
> I do not think that CSL limitations are really limiting us.
>
> - Allowing macros will be handled by ox.el itself automatically
> - Export snippets can also be processed without much issue (consider
> direct LaTeX code)
> - inline-
Dear All,
On Thu, 27 Oct 2022 at 06:10, Ihor Radchenko wrote:
> This will render e.g. strike-through empty.
> Note that citation references may contain the following Org markup objects:
> '(bold code entity italic
> latex-fragment strike-through subscript
> superscript underline verbatim)
th
best wishes,
András
On Tue, 25 Oct 2022 at 13:16, Ihor Radchenko wrote:
>
> András Simonyi writes:
>
> >> No. It is some bug in org-cite-csl--create-structure.
> >> I am CCing the oc-csl maintainer.
> >> András, can you please take a look?
> >
> >
Dear All,
the attached patch improves the parsing and exporting of cite
prefixes, suffixes and locators -- the most noticeable change is
probably the support for formatted locators and of underlining in
general. Comments are welcome.
best wishes,
András
From 5bec7025f66eb65f13a701dc616aca244011
Dear Ihor,
thanks a lot for the super-quick fix!
best wishes,
András
On Wed, 26 Oct 2022 at 06:35, Ihor Radchenko wrote:
>
> András Simonyi writes:
>
> > using the most recent version of the main branch I've noticed some
> > problems with the spacing of documents expo
Dear All,
using the most recent version of the main branch I've noticed some
problems with the spacing of documents exported with the odt exporter:
spaces around links and formatted (for instance, italicized) words are
missing, for example, the Org line
text1 https://orgmode.org/ text2 /italics/
Dear All,
On Thu, 20 Oct 2022 at 07:23, Ihor Radchenko wrote:
> M. ‘quintus’ Gülker writes:
> > Thanks for the hint, but it does not work still even if I change the
> > line to contain the said zero-width space:
> > The buffer is now fontified as expected, but it does not work when
> > exported
Dear All,
I'd like to volunteer to maintain oc-csl.el, which currently doesn't
have an official maintainer as far as I can tell. As the author and
maintainer of citeproc-el and the author of oc-csl's precursor,
citeproc-org, I think I'm reasonably well positioned to handle issues
and make improvem
Dear All,
On Tue, 9 Aug 2022 at 17:38, Rudolf Adamkovič wrote:
> THANK YOU for working on this! I have tried the "locators" style, and
> it works great. At last, we can write in the APA style with no hacks!
thanks for your kind words, I'm glad that you find the additions useful.
> P.S. Not
Could you try Alt-j?
best wishes,
András
On Sat, 13 Aug 2022 at 03:22, Tyler Grinn wrote:
>
> "Bruce D'Arcus" writes:
>
> > You need to use whatever keybinding exits.
>
> I've tried every key in the mode map.
>
Dear All,
I've just noticed that there was a missing citeproc function
declaration in oc-csl.el which could cause a compiler warning. The
attached patch adds the required declaration.
best wishes,
András
From e2573d8c858a280922f1dd13d2c49de9b74a9ec1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C
Dear All,
On Sun, 7 Aug 2022 at 11:45, Ihor Radchenko wrote:
> LGTM in general, but please add a proper commit message.
[...]
> Also, it would be useful to explain a bit what bibentry stands for.
thanks, I've attached a new patch implementing these recommendations.
best wishes,
András
From 361
Dear All,
the attached patch adds support for three new citation styles which
recently got supported by citeproc-el:
- cite/title or cite/ti to cite only the title of an item,
- cite/locators or cite/l to cite only the locators, and
- cite/bibentry or cite/b to cite the full bibliography entry.
Dear All,
On Sun, 31 Jul 2022 at 04:32, Ihor Radchenko wrote:
> Can we then change the oc-biblatex et al defaults to output
> \printbibliography[heading=none]
> ?
>
> Best,
> Ihor
unfortunately, IUC, for bibtex suppressing the heading requires the
(possibly local) redefinition of some commands,
Dear All,
On Fri, 29 Jul 2022 at 03:32, Ihor Radchenko wrote:
> This is an important point. I think that we should describe this gotcha
> in the "Bibliography printing". oc-basic and oc-csl just print the list
> of bibliography entries, while oc-bibtex/oc-natbib/oc-biblatex insert a
> separate s
Dear All,
On Tue, 26 Jul 2022 at 07:37, Ihor Radchenko wrote:
> I am also a non-native speaker, so lets obey the Bruce's judgment.
...
> > yes :title is not supported by the "csl" processor. Should we perhaps
> > replace the example with another one using a multi-word keyword, like
I've attached
Dear All,
this might be a very stupid question as I'm not familiar with the
internals of the Org export engine, but couldn't this change lead to
problems with the Org-to-Org export of documents containing these
"semantic separators"?
thanks and best wishes,
András
On Tue, 26 Jul 2022 at 16:52, T
Dear All,
On Sun, 24 Jul 2022 at 09:41, Ihor Radchenko wrote:
>
> Thanks!
>
> I have made some changes to the patch, mostly fixing grammar issues (the
> ones I can notice). I also changed the sub-section from "Bibliography
> options" to "Bibliography options in "biblatex" and "csl" export process
Dear All,
On Sat, 23 Jul 2022 at 05:59, Ihor Radchenko wrote:
> Could you please create a dedicated subsection under "15 Citation> handling"
> instead of documenting PRINT_BIBLIOGRAPHY together with export
> processors? The section should contain a general overview of what
> PRINT_BIBLIOGRAPHY d
...of course, I managed to leave a typo in the manual patch, please
ignore the earlier version and consider the attached one.
best wishes,
András
On Thu, 21 Jul 2022 at 00:03, András Simonyi wrote:
>
> Dear All,
>
> On Sat, 16 Jul 2022 at 10:43, Ihor Radchenko wrote:
> any Lisp
Dear All,
On Sat, 16 Jul 2022 at 10:43, Ihor Radchenko wrote:
any Lisp predicate as a filter.
> Thanks! LGTM!
>
> Can you please also document the new feature in the manual? Especially,
> the CLS-specific filter options. It is not clear what are they.
many thanks for looking into the patch! I'v
On Tue, 12 Jul 2022 at 13:36, John Kitchin wrote:
> Maybe it is still needed so the tooltip looks nice.
currently, oc-basic.el contains the single activation (fontification)
processor (called "basic") shipped with Org, the other oc-*.el files
provide only export processors.
best wishes,
András
Dear All,
On Sun, 10 Jul 2022 at 09:17, Ihor Radchenko wrote:
> AFAIU, oc-natbib/oc-bibtex also do not support @string because they also
> rely upon the built-in Emacs parser for bib files.
> I have submitted a bug report to Emacs devs [1]. Hopefully it can be
> fixed on Emacs side without a ne
Dear All,
On Mon, 11 Jul 2022 at 04:05, Ihor Radchenko wrote:
> >> Then, I am wondering if parsebib can be added to ELPA or at least
> >> non-GNU ELPA. The same can be said for all other dependencies of
> >> citeproc.el and for citeproc itself.
> non-GNU ELPA is also fine. The idea is to avoid
Dear All,
the attached patch adds support for filter-based sub-bibliographies in the "csl"
org-cite export processor. It supports the same syntax for specifying
filters as the biblatex processor and supports some of the biblatex
filter types, concretely, entry-type and keyword based filtering. It
Dear All,
On Sat, 9 Jul 2022 at 05:55, Ihor Radchenko wrote:
> The problem with parsebib is that it does not even have license
> (I do not see any in https://github.com/joostkremers/parsebib). If
> parsebib were a part of Emacs core or at least a part of ELPA, we would
> also be able to use it i
Dear All,
On Mon, 4 Jul 2022 at 14:27, Ihor Radchenko wrote:
> András Simonyi writes:
> I do not agree.
> If someone sets up natbib for latex export and basic for other formats,
> "*" will not be correctly exported in those other formats (because basic
> d
Dear All,
I'm experiencing the following mysterious problem with the csl
citation export processor: exporting using the export dispatcher
without a prefix argument works fine, but when I repeat the export
action using C-u before C-e the exported bibliography items containing
quotes have the quotes
Dear All,
On Sun, 3 Jul 2022 at 15:09, Ihor Radchenko wrote:
> Then, oc-natbib, oc-biblatex, and oc-csl should be modified to provide
> an alternative activation function that will not highlight @* as
> non-existing key.
>
> Probably, we can even use an alternative "special" key face, not
> 'org
Dear Ihor,
thanks a lot for your reply!
On Sat, 2 Jul 2022 at 06:37, Ihor Radchenko wrote:
> By "*", do you mean something like [cite/n:@*]?
> If so, will it be correctly fontified as an existing citation?
Yes I meant exactly that. As for fontification, this is a very good
question! I've check
Dear All,
the attached patch adds support for nocite citations in the csl
org-cite export processor, including support for using the special key
"*" to include all entries in the bibliography.
best wishes,
András
From 3e6514d2e2f4fa68462a02578880b126e3116739 Mon Sep 17 00:00:00 2001
From: =?UTF-
Dear All,
On Mon, 6 Jun 2022 at 03:45, Alan Tyree wrote:
> A short random test shows that the export chokes when there is a single name
> for an author. Again an example:
> author = {{Wolfsberg Group}} works fine;
> author = {{Wolfsberg}} chokes.
Alan, could you open an issue in the citeproc-e
Dear All,
On Wed, 19 Jan 2022 at 10:56, Ihor Radchenko wrote:
> As a side note, citeproc-el currently has poor performance on large org
> files. It is unusable for me.
Could you elaborate? In theory, oc-cs.el's performance should depend
only on the number of citations (as opposed to the size of
Dear All,
On Wed, 19 Jan 2022 at 04:24, Ihor Radchenko wrote:
> > Scientific papers require more work, it is necessary to make them
> > available to org-cite somehow. Some nerds use quite peculiar blog
> > engines and strange setting of metadata. So shopping on some sites might
> > work better t
Dear All,
On Sat, 1 Jan 2022 at 14:53, Julien Chastang
wrote:
> I have been experimenting with org-cite. I noticed that I can insert
> (org-cite-insert) all bibtex types *except* for @conference. [...]
> yet I believe @conference is a valid bibtex type. I noticed that
> org-bibtex-types has an
Dear All,
On Thu, 9 Dec 2021 at 10:54, Xianwen Chen (陈贤文) wrote:
> Thinking about the new org-cite, which is orgmode's native citation solution,
> I'm wondering if it would be easier to use org-cite within orgmode and export
> to ODT? A small example with configuration suggestion will be highl
Dear All,
On Mon, 6 Dec 2021 at 14:43, Ypo wrote:
> I am able to make macros, but I think I am far away from Lisp programming.
> [...]
> Is there a path to go from macros to elisp programming?
there is a package called 'elmacro' (https://github.com/Silex/elmacro)
which you can look into. Appar
www.youtube.com/watch?v=rRR-5NSpKyE
> > <https://www.youtube.com/watch?v=rRR-5NSpKyE> for an overview of what to
> > do. basically you need a csl file that provides the style you want, and
> > you specify it like this in the org file or in default settings. You may
> > also n
Dear Joseph,
unfortunately, my note on the `citeproc-org` page has become kind of
misleading and has to be updated because org-ref didn't switch to the
new org-cite citation syntax after all, although this was the plan for
a while. I think if you wish to use org-ref 3 then you should simply
remove
On Thu, 25 Nov 2021 at 12:21, juh wrote:
> After I fixed my installation I now use org-mode 9.5.1 but still
> citations are not rendered in no export format neither with basic nor
> with csl.
> test.bib in same directory:
>
>
> @article{doe,
> author={org, mode and Syntax, Citation and
Dear All,
On Wed, 24 Nov 2021 at 16:49, juh wrote:
> The error disappears but the bibliography still is not rendered.
>
> I get the plain code:
>
> [@doe 45]
>
> [cite/t:@doe 45]
>
> juh
is the rendering OK when you export using the built-in, standard
backends, e.g., html or txt? As a data point,
Dear All,
On Wed, 17 Nov 2021 at 16:07, Bruce D'Arcus wrote:
>
> On Wed, Nov 17, 2021 at 9:59 AM Rudolf Adamkovič wrote:
>
> > I would like to start using the new citations with the APA Style. To cite
> > in APA, I use a CSL file. Everything works well with Pandoc, but with Org,
> > all citati
Dear All,
On Thu, 4 Nov 2021 at 20:26, M. ‘quintus’ Gülker
wrote:
> The improper formatting on LaTeX export I mentioned in the other e-mail[1]
> however is still persisting,
> both with the @ and without it.
I've pushed a change to citeproc-el which should solve that problem --
thanks for rep
Dear All,
On Wed, 3 Nov 2021 at 17:02, Nicolas Goaziou wrote:
> It looks like there's something to repair on the Citeproc side. I'm
> Cc'ing András Simonyi for a better understanding of the problem.
I think this problem has been fixed in citeproc-el (see PR #55) -- you
Dear All,
the attached simple patch fixes a problem in oc-csl.el which led to
missing footnote number information for citations that were
automatically footnote-wrapped based on the used CSL style.
best wishes,
András
From 1423e0f600d8e4e29f275faa9c9117db9b081b19 Mon Sep 17 00:00:00 2001
From: =?
Dear All,
I think I found the source of this problem in oc-csl.el -- I'll post a
patch shortly.
best wishes,
András
On Tue, 19 Oct 2021 at 16:08, Ihor Radchenko wrote:
> By the way, do I understand correctly that oc-csl.el requires
> citeproc-el to be installed? It is not clearly stated in the commentary.
Yes, oc-csl.el uses citeproc-el for formatting the citations and the
bibliography. I'm not entirely sure
Dear Ypo,
I also think that the org-bibtex format is pretty close to what you
are looking for. An added benefit could be that the org-cite CSL
export processor has recently gained (admittedly rather experimental)
support for directly using org-bibtex bibliographies, although insert
and follow func
Dear Joseph,
in theory evaluating
(libxml-available-p)
should tell you whether your Emacs has libxml support -- most probably
it doesn't. Maybe you should try to recompile using the --with-xml2
switch.
best wishes,
András
On Mon, 18 Oct 2021 at 14:42, Joseph Vidal-Rosset
wrote:
>
>
>
> Le 18/1
Dear All,
On Tue, 12 Oct 2021 at 07:43, M. ‘quintus’ Gülker
wrote:
> Das ist ein Test [cite:@saenger2013gsr § 12 Rn. 488].
>
> gives:
>
> Saenger, Gesellschaftsrecht, 2. Aufl. (2013), §§ 12 Rn. 488
[...]
> This is a little confusing. Maybe an error on my part? Do I need to
> signal singu
Dear All,
On Sun, 10 Oct 2021 at 22:11, Nicolas Goaziou wrote:
>
> Then, this may be a bug in Citeproc library itself. I suggest to report
> it upstream.
looks like an Org (oc-csl) side locator parsing problem to me, because
using the alternative [cite:@saenger2013gsr para. 12 Rn. 488] form I
se
Dear All,
setting the `org-cite-csl-locales-dir' variable to a directory
containing the German CSL locale file I indeed get the localized
Akbarian, Samira, An einen, der vorüberfuhr, Stand: 14. Dezember 2020,
https://verfassungsblog.de/an-einen-der-voruberfuhr/ (besucht am
02.01.2021).
version o
Dear Marvin,
thanks for the bug report! I was able to reproduce the issue and it
seems to be indeed a problem in citeproc-el -- I'll investigate and
respond to the citeproc-el ticket.
best wishes,
András
On Mon, 4 Oct 2021 at 19:29, Nicolas Goaziou wrote:
>
> Hello,
>
> M. ‘quintus’ Gülker wri
Dear All,
the patch which I attached removes some stray/leftover words from the
manual's section on citations.
best wishes,
András
From 1936c8a3e4668192cb279f417d980fa353fc6bbb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A1s=20Simonyi?=
Date: Tue, 28 Sep 2021 23:13:07 +0200
Subject: [PATCH]
Dear All,
I've attached a patch with the pcase pattern refactored following
Nicolas's example -- hopefully this solves the problem.
best wishes,
András
On Tue, 28 Sept 2021 at 17:16, András Simonyi wrote:
>
> Thanks, I'll try to put together a patch fixing the problem a
Thanks, I'll try to put together a patch fixing the problem and send it shortly.
best wishes,
András
On Tue, 28 Sept 2021 at 17:03, Max Nikulin wrote:
>
> On 28/09/2021 21:40, Bastien wrote:
> > András Simonyi writes:
> >
> >> the attached patch adds support
Dear All,
the attached patch adds support for the text (textual) and year
(year-only) citation styles in the CSL org-cite processor.
best wishes,
András
From ce91f9332ed154fd14f36177bc6dd96cdda0690e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A1s=20Simonyi?=
Date: Tue, 28 Sep 2021 11:45:13
Hi Timothy,
> Regarding the content of this patch and the few you have planned that follow —
> would it be fair to say that overall you’re trying to update `oc-csl' based on
> changes you’ve made to `citeproc-el' since `oc-csl' was written?
yes exactly, basically all of my patches are directed to
Dear All,
this is the first item in a series of oc-csl patches which I've
accumulated and am planning to send this week. (My first attempt to
send a patch, so please be patient and forgiving :-) )
This particular change removes the itemgetter constructor function
defined in oc-csl.el and uses the
Perhaps a useful workaround would be to first "export to Org" (with
org-org-export-as-org)?
AFAICS this replaces the Org cites with their export
processor-rendered counterparts, e.g.,
with suitable Natbib cite commands when the
#+cite_export: natbib
line is used.
best regards,
András
On Thu, 5 Au
Dear Jason,
this is excellent news, thanks for your work! I always wondered why
there is no Org exporter for ConTeXt which seemed such an obvious
target -- can't wait to try it out!
best regards,
András
On Wed, 4 Aug 2021 at 21:44, Juan Manuel Macías wrote:
>
> Hi Jason,
>
> Jason Ross writes:
Absolutely, thanks for the correction -- I meant Org's master, even
though the question was clearly about Emacs's.
best regards,
András
On Tue, 3 Aug 2021 at 12:23, Eric S Fraga wrote:
>
> On Tuesday, 3 Aug 2021 at 12:10, András Simonyi wrote:
> > Most of the function
1 - 100 of 132 matches
Mail list logo
