Skip to content
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

Suggestions for implementing custom Pandoc reader/writer? #6

Open
raj-magesh opened this issue Dec 18, 2022 · 1 comment
Open

Suggestions for implementing custom Pandoc reader/writer? #6

raj-magesh opened this issue Dec 18, 2022 · 1 comment

Comments

@raj-magesh
Copy link

Congrats on 1.0!

I'm interested in writing a Pandoc reader/writer for .norg files. Since those are typically written in Lua, I was wondering if any existing parsing-related code could be leveraged for use with Pandoc. A suggestion floating around was to use Treesitter AST but I'm not familiar with that, so I wanted to ask for your advice.

@raj-magesh raj-magesh changed the title Suggestions for implementing custom Pandoc reader/writer Suggestions for implementing custom Pandoc reader/writer? Dec 18, 2022
@mrossinek
Copy link
Member

Congrats on 1.0!

Hi there, and thank you!

I believe that work on a pandoc reader/writer has been started multiple times in multiple places by multiple people. The one project that I know from the top of my head is this one: https://github.com/Simre1/neorg-haskell-parser

This is definitely something that we want to see happen but at the moment all maintainers of Neorg (and the Norg spec) are pretty bandwidth-limited. Our discord is probably a good place to discuss this and potentially find other people interested in working on this (I know that the author of the link above is also on that server).

In terms of advice: I myself also do not know much about pandoc parsers. I believe the reason for the haskell-based project is because pandoc is written in Haskell. I do not know much about its lua interoperability.
That said, the norg parser used by Neorg is based on tree-sitter but also that one is likely to undergo a major rewrite in some unpredictable future..

Hope this helps in terms of providing some context here rather than letting the issue sit stale 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants