From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vicente Vera Subject: Re: Exporting blocks of text completely verbatim Date: Thu, 9 Feb 2017 16:27:23 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c18ff8ac21ac005481b74e8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40885) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cbrZ8-0003PD-70 for emacs-orgmode@gnu.org; Thu, 09 Feb 2017 11:27:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cbrZ6-0004Od-UM for emacs-orgmode@gnu.org; Thu, 09 Feb 2017 11:27:26 -0500 Received: from mail-ot0-x230.google.com ([2607:f8b0:4003:c0f::230]:34787) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cbrZ6-0004OM-KT for emacs-orgmode@gnu.org; Thu, 09 Feb 2017 11:27:24 -0500 Received: by mail-ot0-x230.google.com with SMTP id f9so6946200otd.1 for ; Thu, 09 Feb 2017 08:27:24 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: John Kitchin Cc: emacs-orgmode --94eb2c18ff8ac21ac005481b74e8 Content-Type: text/plain; charset=UTF-8 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 : > 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 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? >> >> > --94eb2c18ff8ac21ac005481b74e8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hmm nope. Still some modifications are introduced dependin= g on the
back-end. Example blocks are generally indented.

There a= re 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 b= elieve.

For example, one could edit an Org document and keep some te= xt 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 K= itchin <jkitchin@andrew.cmu.edu>:
Isn't

#+BEGIN_EX= AMPLE
Long block
#+END_EXAMPLE

what you want?

John

---= --------------------------------
Professor John Kitchin=C2=A0
Do= herty Hall A207F
Department of Chemical Engineering
Carnegie Mellon U= niversity
Pittsburgh, PA 15213
412-268-7803

On Thu, Feb 9, 2017 at 3:11 PM, Vicente Vera= <vicentemvp@gmail.com> wrote:
Hello. This discussion
https://lists.gnu.org/archive/html/emacs-orgmode/2017-02/msg001= 63.html
points out that Org tables are converted to HTML tables when= exporting
through "ox-md". Leaving Markdown-related issues as= ide, I've stumbled
upon this problem a while back.

It is sugg= ested that wrapping the table within a "#+(BEGIN|END)_EXPORT
md&quo= t; should leave it as-is in the exported document but that is not the
ca= se. The table gets converted to HTML anyway.

When skimming through t= he Org manual I found that
"#+(BEGIN|END)_EXPORT back-end" blo= cks are used to export text *only*
for the specified back-end. This appe= ars in the ASCII back-end
documentation (does it work like this for othe= rs back-ends?).

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


--94eb2c18ff8ac21ac005481b74e8--