public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: c.buhtz-OA1p21XQzgd4Eiagz67IpQ@public.gmane.org
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Status and quality of Org-reader
Date: Wed, 22 Mar 2023 13:50:41 +0000	[thread overview]
Message-ID: <f0fcc9052a70816fb4b81e21325ab336@posteo.de> (raw)

Hello,

I was pointed to pandoc because it might be usable as an org-file 
parser. Technically I'm interested in reading org-files and get them 
back in JSON format.

Some quick n dirty tests are promising. I'm maintainer of an 
org-to-html-converter application (I assume advertising it isn't suited 
here.) and do most of the parsing myself. But I'm at a point to think 
about refactoring the parsing or finding a better solution.

Before I throw half of my code into the trash I would like to learn and 
hear more about the current status of the org-reader and how you rate 
it?

I was also looking into the bug tracker and only found some minor 
problems with org reading. All problems I found I can handle and 
workaround with my own code.

Do you have any further suggestions about the org-reader part of pandoc? 
How many people in the pandoc project working on the org-reader part?

Kind
Christian Buhtz


             reply	other threads:[~2023-03-22 13:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22 13:50 c.buhtz-OA1p21XQzgd4Eiagz67IpQ [this message]
     [not found] ` <f0fcc9052a70816fb4b81e21325ab336-1KBjaw7Xf1+zQB+pC5nmwQ@public.gmane.org>
2023-03-22 16:04   ` Albert Krewinkel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f0fcc9052a70816fb4b81e21325ab336@posteo.de \
    --to=c.buhtz-oa1p21xqzgd4eiagz67ipq@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).