Re: [O] Exporting blocks of text completely verbatim

[Vicente Vera]

Hmm nope. Still some modifications are introduced depending on the
back-end. Example blocks are generally indented.

There are cases where those changes makes sense such as in HTML export
but for ASCII and ASCII-based markups truly verbatim blocks would make
sense I believe.

For example, one could edit an Org document and keep some text blocks
completely unchanged so later another processing tool (such as Pandoc)
could deal with them accordingly.

2017-02-09 14:27 GMT+00:00 John Kitchin <address@hidden>:

Isn't

#+BEGIN_EXAMPLE

Long block

#+END_EXAMPLE

what you want?

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, Feb 9, 2017 at 3:11 PM, Vicente Vera <address@hidden> wrote:

Hello. This discussion
https://lists.gnu.org/archive/html/emacs-orgmode/2017-02/msg00163.html
points out that Org tables are converted to HTML tables when exporting
through "ox-md". Leaving Markdown-related issues aside, I've stumbled
upon this problem a while back.

It is suggested that wrapping the table within a "#+(BEGIN|END)_EXPORT
md" should leave it as-is in the exported document but that is not the
case. The table gets converted to HTML anyway.

When skimming through the Org manual I found that
"#+(BEGIN|END)_EXPORT back-end" blocks are used to export text *only*
for the specified back-end. This appears in the ASCII back-end
documentation (does it work like this for others back-ends?).

In a general level, is there a way to keep blocks of text completely
unmodified (without indentation also) on export?