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
Support Pandoc citation syntax #21
Comments
|
Extra feedback from @ argentum:
I'll probably make the database setting a comma separated list then |
|
For the LaTeX export this would be quite useful, since you can specify libraries (that can live on different places on your computer) with |
|
So in your example, there are two files Does this mean you want that I'll take a closer look at this after all the existing bugs are fixed - this looks slightly trickier than expected. |
|
No rush! You can add it only if it's possible, this is a one-liner that I can add manually in LaTeX after export. The main takeaway is that |
|
I was pointed here from the Obsidian #academic Discord. Supporting Pandoc citations would be huge for me and many others! |
|
Thank you again for this usefull plugin. Citeproc filter Nevertheless, as many said in the previous comments, It would be great if you could add --citeproc filter, so that we could use our notes with Zotero (via the plugin obsidian-Citation). Thanks a lot Damien |
|
Hi @damienbelveze, @cobblepot1, @argenos, It's just a little fiddly at the moment. I've tested using BibTeX citations with the Here's a tutorial explaining the fiddly bits: https://github.com/OliverBalfour/obsidian-pandoc/wiki/Citations-(work-in-progress) The main caveat is you can either get Pandoc markdown extensions like citations, or Obsidian markdown extensions/plugin features, but not both. I'll think of ways to work around this if it becomes a pain point. If you have any suggestions for improving this process or the documentation, I'm open to ideas. |
Thanks Oliver! Just to clarify, by 'get' do you mean we can only have either one of those markdown extensions enabled on Obsidian, or only one extension involved in the export operation, or something else? I'm a noob and struggling to get my head around what's going on. I'm coming from Zettlr where exporting to PDF or DOCX with citekeys generating full references is a one-click operation. |
Thank you Oliver, I have the same question than @kenanmike I tried to replicate
Thank you Oliver for this new release, Once I have downloaded it this morning and loaded it into my Obsidian list of plugins, I tried to replicate the example you gave. I put your test.bib file in the same directory as my note (which I made it contain the same YAML frontmatter except for the path : bibliography: test.bib Thank you in advance, |
You can either have all of the Obsidian markdown features or all of the Pandoc markdown features, but not both. This is because a different method processes each type of markdown and there's no easy way to combine them. The (poorly named) |
Glad to hear it works! For the citation style, that's where the fiddly-ness comes into play. You'll need to set the citation style using a Pandoc argument by adding the right command line flag to
Sorry about this, it doesn't handle Unicode in PDF exports very well because LaTeX and emoji are not friends... This relates to #22, I'll fix this separately. (The fix might just be to display a more helpful error message if LaTeX cannot be made to support Unicode cleanly) |
|
Yes, the file path searching isn't the same as using the terminal and I'm not sure why. That would explain why it can't find your test.bib file. To fix this, you'll just need to provide the full path, eg By the way, does the citations plugin interfere with this plugin at all? |


Suggested by Mara & SkepticMystic on Discord #plugins
See https://pandoc.org/MANUAL.html#citations
We'll need to
a) add a setting to specify a database file
b) parse
[@foo, p. 33]syntax into whatever Pandoc likes bestc) add a
--citeprocoption to the CLI commandsd) ...
This will be enormously helpful in conjunction with Zotero and the Obsidian citation plugin
This may be a fair bit of work. I'll tentatively mark it for the 0.2.0 release and push it back a week or two if needed (possibly after submission to the community plugins list).
The text was updated successfully, but these errors were encountered: