Thanks to all for the responses here. They have opened my eyes to new
org features I can use in other ways.
For now, I think my solution to the table export question will be just
to keep everything in org mode and to heck with Editorial and Markdown.
Thanks!
-pd
--
Peter Davis
www.techcu
On Sun, 4 Jun 2017, Vicente Vera wrote:
Cool, you're welcome. It is not the most convenient solution, but
keeping your tables in Editorial Markdown syntax should work:
#+BEGIN_EXPORT md
Cat | Fur |
--- | --- |
A | A lot |
B | None |
#+END_EXPORT
Except that the above is not recogniz
Cool, you're welcome. It is not the most convenient solution, but
keeping your tables in Editorial Markdown syntax should work:
#+BEGIN_EXPORT md
Cat | Fur |
--- | --- |
A | A lot |
B | None |
#+END_EXPORT
2017-06-03 16:46 GMT+00:00 Peter Davis :
> Thanks, Vincente.
>
> I'm specifically
On Sat, Jun 03 2017, Peter Davis wrote:
(FWIW, I tried using pandoc, but this just removed the table
syntax altogether, so an entire table would just run together
into a
paragraph of gibberish.)
You need a somewhat recent version of Pandoc for Org tables to be
handled correctly (some distro
Thanks, Vincente.
I'm specifically aiming at the Markdown syntax supported by the
Editorial app, which does include markup for tables. Unfortunately, it
looks like Editorial's Markdown doesn't use the initial '|', so simply
exporting the org markup won't work without some editing.
Thanks!
-pd
On
There are several Markdown "forks" which have different sets of features.
AFAIK the markdown exporter in Org is based upon John Gruber's
Markdown, which does not include a syntax for tables. Thus all tables
in Org documents get exported as HTML.
A workaround is to wrap your Org tables as:
#+BEGI
