Re: Hiding citations

Am Samstag, dem 25. Februar 2023 schrieb Bruce D'Arcus: > Not exactly what you're asking for, but have you seen this activate processor? > > https://github.com/andras-simonyi/org-cite-csl-activate Not yet, and it certainly looks nice, but the CSL style I use uses footnotes, and those are quite

Hiding citations

Dear list, is there a way to visually hide citations in the org buffer, much like links are hidden? I ask because if a text passage contains a number of citations, it quickly becomes hard to read if they are all displayed in raw format. Here is a paragraph from one of my recently published

Re: [PATCH][oc-csl] Improve reference parsing

Am Donnerstag, dem 19. Januar 2023 schrieb András Simonyi: > hopefully somebody more knowledgeable than me can comment on how > viable this is, but would a @@csl like export snippet construct help > with the problem? > In that case your macro could be along the lines of > > #+MACRO: name

Re: [PATCH][oc-csl] Improve reference parsing

Am Donnerstag, dem 19. Januar 2023 schrieb András Simonyi: > 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

Re: Beamer export: Executing LaTeX between two frames

Dear Ihor, please apologise the slow reply. Am Sonntag, dem 26. Juni 2022 schrieb Ihor Radchenko: > This is too hacky as for my taste. > > I'd rather use :ignore: tag from ox-extra: This works decently. I did not know about “ox-extra” before. For reference, it is here:

Re: Filter for HTML (cite) footnotes?

Dear all, I ought to drive this thread to its completion. What I intend to do is better covered by the new callback functions provided by citeproc-el: <https://github.com/andras-simonyi/citeproc-el/issues/111> -quintus Am Dienstag, dem 08. März 2022 schrieb Juan Manuel Macías: > M.

Re: [PATCH][oc-csl] Improve reference parsing

Dear all, I probably have not much to contribute to this rather technical thread, but Ihor has redirected me here two times for my citation formatting questions[1][2]. So I would like to ask if there is something I can do to accelerate its inclusion into org so that I can start using macros in

Re: [RFC PATCH] Re: [bug] Macro in citation not expanded

Dear Ihor, thank for the WIP patch. I have applied it to current main (f83e45526b5ec4627d601673be3680e2dece1b33), but when I now export the document described in the OP to LaTeX, the macro is erased entirely. I receive: 1 Doe, Nothing important, 2. Aufl. (2022), 55, zum vorgenannten Argument

Re: Formatting in citation locator

Dear all, apologies for my slow reply. It is currently hard for me to find some time for these issues, but eventually I do manage it. Am Mittwoch, dem 26. Oktober 2022 schrieb András Simonyi: > I've ended up making the necessary changes in citeproc and also posted > a patch here which should

Re: Formatting in citation locator

Am Mittwoch, dem 19. Oktober 2022 schrieb Ihor Radchenko: > It is expected because we do not allow "]" right after markup. You'd > need to insert an escape character (zero-width space) to force the > italics markup in [Sondervotum /Schluckebier/]. > See

Re: [bug] Macro in citation not expanded

Am Sonntag, dem 16. Oktober 2022 schrieb Ihor Radchenko: > Only bold, code, entity, italic, latex-fragment, strike-through, > subscript, superscript, underline, and verbatim objects are allowed > inside citations. > This is hard-coded inside `org-element-object-restrictions'. This is a bit

[bug] Macro in citation not expanded

Dear list, it turns out that macros in citation commands are not expanded. Minimal working example: /tmp/mwe.org: #+TITLE: Test #+LANGUAGE: de #+bibliography: /tmp/mwe.bib #+cite_export: csl /tmp/juristische-schulung.csl #+MACRO: name @@latex:\textsc{$1}@@ Dies

Beamer export: Executing LaTeX between two frames

Dear list, I am working on a presentation for a conference (using org-mode and its beamer export) and want to exchange the entire background for a specific frame with an image. This is possible with Beamer, see . It works by issueing \usebackgroundtemplate

Re: Filter for HTML (cite) footnotes?

Hi, Am Sonntag, dem 06. März 2022 schrieb Juan Manuel Macías: > I think a function for `org-export-filter-parse-tree-functions' would > work better here. For example, this function replaces "lorem ipsum" with > "foo" in all footnote definitions: I have tried this suggestion, but it does not

Filter for HTML footnotes?

Dear list, I recently discovered export filters and found some useful applications for them. For instance, the scientific domain I work in (law) uses footnote citations, and in these footnotes we abbreviate some words which would otherwise be written out in ordinary text, like name particles.

Re: Concrete suggestions to improve Org mode third-party integration :: an afterthought following Karl Voit's Orgdown proposal

Am Montag, dem 06. Dezember 2021 schrieb Tom Gillespie: > [On not excluding discussions about org markup from the mailing list] Thank you for writing this up. I agree with it. This discussion has taken routes which I would never have expected. We started with an interoperability topic and now

Re: Orgdown: negative feedback & attempt of a root-cause analysis (was: "Orgdown", the new name for the syntax of Org-mode)

Am Dienstag, dem 30. November 2021 schrieb Karl Voit: > One of the next things I do have on my list is to try out crdt as > I've learned at EmacsConf21 that it is mature enough to be used in > practice. > > If that holds true, we can start dreaming of having a Etherpad-like > session from our

Re: "Orgdown", the new name for the syntax of Org-mode

Am Montag, dem 29. November 2021 schrieb Karl Voit: > It seems to be the case that the name "Orgdown" is the reason why > the Org-mode community does not support the idea of an > implementation-agnostic definition of the syntax. Which is ... kinda > funny if you think about it. > > Well if the

Re: [PATCH] c-csl : accept relative CSL filenames

Am Freitag, dem 19. November 2021 schrieb Nicolas Goaziou: > I think a better order for a relative file name would be: > > 1. relatively to `org-cite-csl-styles-dir', > 2. relatively to buffer's default directory, > 3. failure. > > WDYT? I would be fine with it. -quintus -- Dipl.-Jur. M.

Re: [BUG] Citations: Locator treated as prefix [9.5 (release_9.5-225-g494c20 @ /home/quintus/.emacs.d/org-mode/lisp/)]

Am Freitag, dem 12. November 2021 schrieb Nicolas Goaziou: > Indeed. I forgot to say you also need to re-evaluate > ‘org-cite-csl--label-regexp’ definition (in "oc-csl.el"), in order to > refresh the locator regexp matched against. Ah, I see. Indeed, re-evaluating that definition after amending

Re: [BUG] Citations: Locator treated as prefix [9.5 (release_9.5-225-g494c20 @ /home/quintus/.emacs.d/org-mode/lisp/)]

Am Freitag, dem 12. November 2021 schrieb Nicolas Goaziou: > This is because "Kap." is not known as a locator identifier. See > ‘org-cite-csl--label-alist’ for the full list of such identifiers. You are right, sir. “Kap.” is German for “chapter” and CSL does have a localisable chapter locator.

[BUG] Citations: Locator treated as prefix [9.5 (release_9.5-225-g494c20 @ /home/quintus/.emacs.d/org-mode/lisp/)]

Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See https://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org mailing list.

Re: [BUG] Elisp error when exporting citation [9.5 (release_9.5-104-g2b1fc6 @ /home/quintus/.emacs.d/org-mode/lisp/)]

Am Samstag, dem 06. November 2021 schrieb András Simonyi: > I've pushed a change to citeproc-el which should solve that problem -- > thanks for reporting it. Thank you again! It works now properly. -quintus -- Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite Passau,

Re: [PATCH] c-csl : accept relative CSL filenames

Am Donnerstag, dem 04. November 2021 schrieb Nicolas Goaziou: > I think there are two ways forward when a relative file name is used: > > 1. First check `org-cite-csl-styles-dir' and, if it is nil, expand >against `default-directory'; > > 2. Drop `org-cite-csl-styles-dir' and always expand

Re: [BUG] Elisp error when exporting citation [9.5 (release_9.5-104-g2b1fc6 @ /home/quintus/.emacs.d/org-mode/lisp/)]

Dear all, Am Donnerstag, dem 04. November 2021 schrieb Nicolas Goaziou: > Great! Hopefully, OP's problem is completely solved, then. I can confirm that the original example I gave (the one with the missing @ sign) does not error anymore now. The improper formatting on LaTeX export I mentioned in

Citations: position="first" match not properly evaluated

Dear all, the CSL style I use has footnotes. When a book is cited, it is once cited with the full bibliographic information, and later footnotes then reference the footnote in which this information first appeared, shortening the later footnotes to the format "Author, (o. Fn. ), ...". (the

Re: Ox-pandoc and Org-cite

Am Donnerstag, dem 14. Oktober 2021 schrieb Alex Fenton: > The arrival of citation support in Org is fantastic, but it is a bit > tricky for ox-pandoc, b/c pandoc itself has csl-based cite processing > ability. I'd appreciate any pointers on a couple of points: Maybe it will get easier when

Re: Manual suggestion and experience report from a new user (citation processors, 9.5)

Am Mittwoch, dem 13. Oktober 2021 schrieb Leszek Wroński: > Ideally I'd like a click on a citation to open the PDF whose location > is stored in the 'file' field of the .bib entry: is there an easy way > to achieve this? [I've tried various ways of doing this in the last > 10+ years, including

Re: Citations: non-page locators placed in front of citation

Am Dienstag, dem 12. Oktober 2021 schrieb András Simonyi: > No, it's citeproc-el which is supposed to determine whether the passed > locator string represents single vs multiple references, using § vs §§ > shouldn't make a difference, because they simply signal that the label > is "section". I

Re: Citations: non-page locators placed in front of citation

Am Dienstag, dem 12. Oktober 2021 schrieb Nicolas Goaziou: > I mapped both § and §§ to "section". Hopefully, the issue is now > completely fixed. Nearly :-). Thank you so much for your hard work so far! It is incredible to see how this develops. With »Org mode version 9.5

Re: Citations: non-page locators placed in front of citation

Am Montag, dem 11. Oktober 2021 schrieb Bruce D'Arcus: > Looks like § is currently mapped to the same as ¶: "paragraph", which > is indeed incorrect. > > https://github.com/citation-style-language/locales/blob/0cc3885f6100e26ac6c6d103efa6f3d7195fd21b/locales-de-DE.xml#L210 This is interesting.

Re: Citations: non-page locators placed in front of citation

Am Montag, dem 11. Oktober 2021 schrieb Nicolas Goaziou: > Indeed. The "fix" I introduced was a mistake. I pushed a new fix. > I think the initial issue is solved now. Could you confirm it? Thank you so far -- we are getting closer. Now at »Org mode version 9.5 (release_9.5-102-gd0b557 @

Re: Citations: non-page locators placed in front of citation

Am Sonntag, dem 10. Oktober 2021 schrieb András Simonyi: > looks like an Org (oc-csl) side locator parsing problem to me, because > using the alternative [cite:@saenger2013gsr para. 12 Rn. 488] form I > seem to get the correct result. Can it be a regex matching problem > with the paragraph

Re: Citations: non-page locators placed in front of citation

Am Sonntag, dem 10. Oktober 2021 schrieb Nicolas Goaziou: > Then, this may be a bug in Citeproc library itself. I suggest to report > it upstream. Done: https://github.com/andras-simonyi/citeproc-el/issues/57 -quintus -- Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite

Re: Citations: non-page locators placed in front of citation

Am Sonntag, dem 10. Oktober 2021 schrieb Nicolas Goaziou: > On the contrary, feedback on citations is very much welcome. This is > a new features, and as such, has some rough edges. Thanks for bearing with me. > It is a bug. You use a non-breaking space between the locator and the > number. I

Citations: non-page locators placed in front of citation

Dear all, apologies for my frequent e-mails. It’s just that I am evaluating the citations facility for me. This time it’s about non-page locators. Take the following document: #+TITLE: Test #+AUTHOR: testauthor #+LANGUAGE: de #+bibliography: /tmp/mwe/mwe.bib #+cite_export:

Re: Citations: Locale specific adaptions?

Am Freitag, dem 08. Oktober 2021 schrieb Nicolas Goaziou: > Meanwhile, the `csl' processor is copiously documented in the > "Commentary" section of the "oc-csl.el" file. Thanks for the heads-up. Next time I will take a look there as well. -quintus -- Dipl.-Jur. M. Gülker |

Re: Citations: Locale specific adaptions?

Am Freitag, dem 08. Oktober 2021 schrieb Nicolas Goaziou: > I think you need to provide locales in addition to the style file, see > `org-cite-csl-locales-dir'. That resolved the problem! Thank you (and Bruce). I cloned https://github.com/citation-style-language/locales and set

Citations: Locale specific adaptions?

Dear list, CSL has a concept of locales, where things like specific terms or the date format are drawn from locale files (see https://docs.citationstyles.org/en/1.0.1/specification.html#locale). I am not entirely sure if this is supported yet by the new citations functionality. Take this test

Re: [BUG] Citations: exporting with csl crashes [9.5 (9.5-g0a86ad @ /home/quintus/.emacs.d/elpa/org-9.5/)]

Am Montag, dem 04. Oktober 2021 schrieb Nicolas Goaziou: > It looks like the issue is in the Citeproc library, not in the Org > wrapper. You may want to report it upstream. Ah, I see. Thank you for the pointer. I created an issue ticket with a copy of the OP here:

Re: Help requested: Support for basic Org mode support in tools outside of Emacs

Am 04. August 2021 um 12:57 Uhr +0200 schrieb Karl Voit: > My focus is on Emacs-independent tools, emphasizing the argument > that Org mode is not Emacs-only and its syntax does have > applications outside of Emacs as well because it is a well-defined > syntax in the sense of >

Re: wip-cite status question and feedback

Am 05. Mai 2021 um 14:27 Uhr -0400 schrieb Bruce D'Arcus: > Hope that explains. Sure, thank you! I just wanted to provide some possibly useful input. I am not to critise these exciting efforts. -quintus -- Dipl.-Jur. M. Gülker | https://mg.guelker.eu |For security: Passau, Germany |

Re: wip-cite status question and feedback

Am 05. Mai 2021 um 09:46 Uhr -0400 schrieb Bruce D'Arcus: > We found three rules: > > 1. what Chicago calls "American" > 2. what it calls "British" > 3. French (though Denis is still confirming how these work in actual books) > > The output in each, when formatting as a note: > > 1. A sentence

Re: wip-cite status question and feedback

Am 23. April 2021 um 09:24 Uhr -0400 schrieb Bruce D'Arcus: > It can be that not only does the space get removed, but the note mark > is moved outside the period. > > So if you have ... > > Some sentence with a concluding citation [cite:@key]. > > ... that should end up like this: > > Some

Re: (Not so) Short note about citations in Org

Hi, Am 22. April 2021 um 01:34 Uhr +0200 schrieb Nicolas Goaziou: > A noteworthy difference with the last merge is that I removed the > opportunity to add some Org syntax (emphasis, sub/superscript…) in > prefixes or suffixes. It makes the code a bit simpler. Of course, I'm > open to discussion

Re: wip-cite status question and feedback

Hi, Am 12. April 2021 um 15:19 Uhr +0200 schrieb Nicolas Goaziou: > The syntax is complete in "wip-cite-new" branch. For the record, in its > full glory, it can look like this: > > [cite/style: global prefix; prefix -@key suffix ; ... ; global suffix] > > [...] > - "exporting" action is

Re: wip-cite status question and feedback

Am 24. März 2021 um 09:22 Uhr -0400 schrieb Bruce D'Arcus: > Anyone know anything else? Not really. I would just like to say that I am eagerly watching this thread and am earnestly curious about what will happen to wip-cite. A proper cite system for org would be such a useful feature. -quintus

Re: Org as a book publisher

Am 06. März 2021 um 20:34 Uhr +0100 schrieb Juan Manuel Macías: > I would like to share here two samples of one of the most intense > uses that I give Org Mode: for typesetting, layout and editorial > design. [...] The samples are from a book on classical philology, > recently published here in

Re: local variables and export processing in hooks

Am 11. Februar 2021 um 21:12 Uhr +0100 schrieb Sébastien Miquel: > The purpose of #+BIND is to set some variables in the copied buffer. > > Also, these variables are set after macro expansion (and > org-export-before-parsing-hook). Thanks for the information. If they are set after macro

Re: local variables and export processing in hooks

Am 09. Februar 2021 um 14:21 Uhr +0100 schrieb Sébastien Miquel: > Eric S Fraga writes: > > I tried but this doesn't seem to be propagated to the export as the > > export works on a copy of the buffer, not the buffer itself. That's > > what #+BIND is for, supposedly... > > I think this buffer