From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: what is the scope for supported formats?
Date: Sat, 18 Feb 2023 21:29:14 +0100 [thread overview]
Message-ID: <875ybyllvj.fsf@zeitkraut.de> (raw)
In-Reply-To: <a771c33b-8adc-4945-bc48-384fce6e88a5n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
eldritch cookie <henrique.hsa2002-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> basically can any markup format be added in the core repo? i am
> planning on adding support for the custom format used by https://
> github.com/nvim-neorg/neorg if i implement my code in haskell can
> i just make a pr to add norg support in the main repo? or would
> the norg format be out of scope?
The format should be reasonably popular, which I think is the case here
(3.4k stars on GitHub). Adding the code directly to pandoc is fine;
another method is to write a separate Haskell package for the neorg
format. The `commonmark` package is the best showcase for this approach,
with `jira-wiki-markup` being another example.
https://github.com/jgm/commonmark-hs
https://github.com/tarleb/jira-wiki-markup
>> On Saturday, February 18, 2023 at 3:49:13 PM UTC-3 denis...-NSENcxR/0n0@public.gmane.org
>> wrote:
>>
>> How is that format different from the regular org format? Could
>> that treated like a variant of the standard org format?
>
> i don't think it could [...] it certainly is really
> different now.
I agree that they are completely different formats. Looks like the only
remaining similarity is the use of asterisks as markers for headings. It
looks a lot like textile and Markdown were major inspirations for the
new format.
--
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
prev parent reply other threads:[~2023-02-18 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AQHZQ8Vnebl1Q5+IJEK04j0KLNP/mK7VCv8I>
2023-02-18 18:18 ` eldritch cookie
[not found] ` <23ad1f68-17f5-4176-9a7f-a43ea102e2fdn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-02-18 18:49 ` AW: " denis.maier-NSENcxR/0n0
[not found] ` <02fe1fafa217459e8898672dfc23e47d-NSENcxR/0n0@public.gmane.org>
2023-02-18 19:28 ` eldritch cookie
[not found] ` <a771c33b-8adc-4945-bc48-384fce6e88a5n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-02-18 20:29 ` Albert Krewinkel [this message]
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=875ybyllvj.fsf@zeitkraut.de \
--to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@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).