From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Jay Kamat <jaygkamat@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>,
Kaushal Modi <kaushal.modi@gmail.com>
Subject: Re: [PATCH] Add TITLE export to ox-md
Date: Sat, 26 Aug 2017 10:11:30 +0200 [thread overview]
Message-ID: <87y3q6wxxp.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87ziaphvu7.fsf@gmail.com> (Jay Kamat's message of "Thu, 24 Aug 2017 10:41:20 -0400")
Hello,
Jay Kamat <jaygkamat@gmail.com> writes:
> I agree that vanilla markdown does not support title, but if ox-md does not
> support any form of title, then there is disparity between the output of other
> org exports and the markdown exporter. I would like to solve that disparity if
> possible.
The point of "md" export back-end is not to provide the same features as
full-fledged ones like "latex" or "html". I wrote it to take care of the
boring stuff of markdown syntax. Anyone willing to write a back-end with
a different Markdown flavour just needs to concentrate of the
differences between the original syntax.
IOW, discrepancy here is not a concern.
> From the markdown that I've worked with, this isn't the case. The
> original markdown tool (https://daringfireball.net/projects/markdown/)
> dosen't seem to output filename titles in it's export, so I wouldn't
> think it's part of the vanilla standard.
I don't think either.
>> Maybe we eventually end up with 3 options (something like below):
>>
>> - org-md-title-as-h1
>> - org-md-subtitle-as-h2
>> - org-md-heading-offset
>
> that's probably the best idea I've heard so far, since I would imagine most
> people would either not want to have two H1 headings right after each other, or
> not want to have their headings shifted. Having such options would allow people
> to pick the scenario they want (shifting headings under the title, including the
> title but no offset, or not including the title at all).
I don't think this is a good idea, because it makes "ox-md.el" less
neutral. That could get in the way of other back-ends.
AFAIC, I think <title>...</title> or even <header>...</header>
<main>...</main>, as you suggested, are better choices.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-08-26 8:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 3:32 [PATCH] Add TITLE export to ox-md Jay Kamat
2017-08-24 9:30 ` Nicolas Goaziou
2017-08-24 10:28 ` Kaushal Modi
2017-08-24 14:41 ` Jay Kamat
2017-08-26 8:11 ` Nicolas Goaziou [this message]
2017-08-28 2:43 ` Jay Kamat
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y3q6wxxp.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=jaygkamat@gmail.com \
--cc=kaushal.modi@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).