From: <denis.maier-NSENcxR/0n0@public.gmane.org>
To: <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: AW: what is the scope for supported formats?
Date: Sat, 18 Feb 2023 18:49:07 +0000 [thread overview]
Message-ID: <02fe1fafa217459e8898672dfc23e47d@unibe.ch> (raw)
In-Reply-To: <23ad1f68-17f5-4176-9a7f-a43ea102e2fdn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
How is that format different from the regular org format? Could that treated like a variant of the standard org format?
________________________________________
Von: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> im Auftrag von eldritch cookie <henrique.hsa2002-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Gesendet: Samstag, 18. Februar 2023 19:18:24
An: pandoc-discuss
Betreff: what is the scope for supported formats?
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?
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/23ad1f68-17f5-4176-9a7f-a43ea102e2fdn%40googlegroups.com<https://groups.google.com/d/msgid/pandoc-discuss/23ad1f68-17f5-4176-9a7f-a43ea102e2fdn%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/02fe1fafa217459e8898672dfc23e47d%40unibe.ch.
next prev parent reply other threads:[~2023-02-18 18:49 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 ` denis.maier-NSENcxR/0n0 [this message]
[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
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=02fe1fafa217459e8898672dfc23e47d@unibe.ch \
--to=denis.maier-nsencxr/0n0@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).