-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with bibliography while exporting with org mode 9.5 #85
Comments
Thank you for the report. With Org 9.5 having in-built citation support, the way the I have it on top of my list on the maintained fork of ox-pandoc. Feel free to comment there. For now, you'll either have to use Org 9.4 or use Org 9.5 with the built-in export backends, not |
@a-fent Thank you so much for your reply and for your effort: ox-pandoc is such an amazing package and I can't wait to see it fully working again! |
PS. I have played a little with the code and tryed feeding the split-string function with (nth 0 value), to see if I could temporarily patch the problem... It didn't work. The bibliography item was not recognized and simply printed as a link in the output file (a .docx in my case). |
Yes, there are a few things that need to be changed in option handling and processing. I have got as far as having ox-pandoc pass through the bibliography if on 9.5, so it will let Org mode handle citations. So you can use "basic" or "biblatex" (for example) and have it work. It's on a branch if you want to try it. https://github.com/emacsorphanage/ox-pandoc/tree/citations-org9.5 |
Thanks! Sorry, when you say "you can use "basic" or "biblatex" (for example) and have it work", what do you refer to exactly? I have tried the code, it doesn't give me any problem while exporting, but the result is not formatted (i still get a link that says "cite:&bibliographyitem" in my .docx file). Probably this was meant to be, being this an early stage of development of the branch... |
Thank you, I appreciate you taking the time to try it out. I should have been clearer: I meant that if you put a However I have only tried the |
No, thank you!
I had already set the value of org-cite-export-processors:
(setq org-cite-export-processors '((beamer biblatex)
(latex biblatex)
(t csl "~/Dropbox/Standard/Modelli/andrea.csl")))
so – if I am not wrong – it should have worked in the first place, shouldn’t it?
… Il giorno 17 nov 2021, alle ore 15:17, Alex Fenton ***@***.***> ha scritto:
Thank you, I appreciate you taking the time to try it out.
I should have been clearer: I meant that if you put a #+CITE_EXPORT header in the document, Org 9.5+ should process the citations in the way described in the Org manual <https://orgmode.org/manual/Citation-export-processors.html#Citation-export-processors>
However I have only tried the biblatex and basic processors. If you are exporting to docx you probably will want to use the CSL exporter.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#85 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AONRCSKP3S4UBH77KIASY53UMO2OVANCNFSM5HWEUJJQ>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Not 100% sure, I haven't worked that much yet with the new citation system. But looks right. My test document sets it in the org-mode header line. |
Hi! Is there any update on the treatment of org 9.5 citations? I see that a new release appeared on MELPA in the meanwhile, but the exporting of citations via csl still seems impossible. Am I doing anything wrong or the development is still on its way? Thank you so much! |
Please could you post a minimal example at the thread emacsorphanage#1 together with any error messages? It should work in theory, but it's still experimental and more reports on the CSL export in particular would help. |
Sure, I just did it! Thanks!
… Il giorno 1 dic 2021, alle ore 08:11, Alex Fenton ***@***.***> ha scritto:
Please could you post a minimal example at the thread emacsorphanage#1 <emacsorphanage#1> together with any error messages?
It should work in theory, but it's still experimental and more reports on the CSL export in particular would help.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#85 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AONRCSKS3IMUHBBANDBE4YDUOXDCBANCNFSM5HWEUJJQ>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Hi,
I get a "Wrong type argument, stringp, ("/path/to/bibliography.bib")" error every time I try to export via pandoc: as a result, I am not able to export anymore.
I have already written to the org mode mantainers but apparently the problem is upstream and has to do rather with this package specifically...
Here's the backtrace of the error:
Debugger entered--Lisp error: (wrong-type-argument stringp ("/Users/test/Dropbox/ciao.bib" "
/Dropbox/Standard/Bibliografia/bibliografia_gener..."))/Dropbox/Standard/Bibliografia/bibliografia_gener...") "\n")split-string(("/Users/test/Dropbox/ciao.bib" "
#f(compiled-function (it) #<bytecode 0x1a35aa0a79e6febf>)((bibliography . :bibliography))
org-export-as(pandoc nil nil nil (:output-file "prova.tmpPDzJxT.org"))
org-export-to-file(pandoc "prova.tmpPDzJxT.org" nil nil nil nil nil #f(compiled-function (f) #<bytecode 0xb0002599e44c2eb>))
org-pandoc-export(docx nil nil nil nil nil 0)
org-pandoc-export-to-docx-and-open(nil nil nil nil)
org-export-dispatch(nil)
funcall-interactively(org-export-dispatch nil)
command-execute(org-export-dispatch)
Thank you so much,
Andrea.
The text was updated successfully, but these errors were encountered: