From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Loris Bennett <loris.bennett@fu-berlin.de>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: [Documentation Bug?] Markdown export
Date: Thu, 19 Apr 2018 09:06:06 -0700 [thread overview]
Message-ID: <CAJ51ETpsDZzfGCVgVqzD9fDREYvAskin+P1WRF9hEVAVJxy1dQ@mail.gmail.com> (raw)
In-Reply-To: <878t9jprh2.fsf@hornfels.zedat.fu-berlin.de>
[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]
Org tables get exported as an html table.
John
-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
On Thu, Apr 19, 2018 at 12:47 AM, Loris Bennett <loris.bennett@fu-berlin.de>
wrote:
> Hi,
>
> On the page
>
> https://orgmode.org/manual/Markdown-export.html
>
> the second line reads:
>
> Since md is built on top of the HTML back-end, any Org constructs not
> supported by Markdown, such as tables, the underlying html back-end
> (see HTML export) converts them.
>
> My guess is that this should be
>
> Since md is built on top of the HTML back-end, any Org constructs not
> supported by Markdown, such as tables, are converted by the underlying
> html back-end (see HTML export).
>
> However, I still don't understand what it means, so maybe my guess is
> incorrect.
>
> In any case, what will an Org table be converted to in the MD output?
>
> Cheers,
>
> Loris
>
> --
> Dr. Loris Bennett (Mr.)
> ZEDAT, Freie Universität Berlin Email loris.bennett@fu-berlin.de
>
>
>
[-- Attachment #2: Type: text/html, Size: 2065 bytes --]
next prev parent reply other threads:[~2018-04-19 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 7:47 [Documentation Bug?] Markdown export Loris Bennett
2018-04-19 16:06 ` John Kitchin [this message]
2018-04-20 9:18 ` Nicolas Goaziou
2018-04-20 9:36 ` Loris Bennett
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=CAJ51ETpsDZzfGCVgVqzD9fDREYvAskin+P1WRF9hEVAVJxy1dQ@mail.gmail.com \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=loris.bennett@fu-berlin.de \
/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).