From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vicente Vera Subject: Exporting blocks of text completely verbatim Date: Thu, 9 Feb 2017 14:11:28 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11416070aaf33f0548198e9f Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54615) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cbpRd-0000Zu-9I for emacs-orgmode@gnu.org; Thu, 09 Feb 2017 09:11:34 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cbpRc-0000W1-8R for emacs-orgmode@gnu.org; Thu, 09 Feb 2017 09:11:33 -0500 Received: from mail-ot0-x22a.google.com ([2607:f8b0:4003:c0f::22a]:36078) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cbpRc-0000V0-3B for emacs-orgmode@gnu.org; Thu, 09 Feb 2017 09:11:32 -0500 Received: by mail-ot0-x22a.google.com with SMTP id 32so3594577oth.3 for ; Thu, 09 Feb 2017 06:11:29 -0800 (PST) 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: emacs-orgmode --001a11416070aaf33f0548198e9f Content-Type: text/plain; charset=UTF-8 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? --001a11416070aaf33f0548198e9f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello. This discussion
https://lists.gnu.org/ar= chive/html/emacs-orgmode/2017-02/msg00163.html
points out that Org t= ables are converted to HTML tables when exporting
through "ox-md&qu= ot;. 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 expo= rted 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
documen= tation (does it work like this for others back-ends?).

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

--001a11416070aaf33f0548198e9f-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Kitchin Subject: Re: Exporting blocks of text completely verbatim Date: Thu, 9 Feb 2017 15:27:53 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a114b4738677ad1054819c917 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59393) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cbphW-0001rU-4D for emacs-orgmode@gnu.org; Thu, 09 Feb 2017 09:27:59 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cbphU-0005hY-RV for emacs-orgmode@gnu.org; Thu, 09 Feb 2017 09:27:58 -0500 Received: from mail-wr0-x244.google.com ([2a00:1450:400c:c0c::244]:34816) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cbphU-0005fP-Jj for emacs-orgmode@gnu.org; Thu, 09 Feb 2017 09:27:56 -0500 Received: by mail-wr0-x244.google.com with SMTP id o16so12126943wra.2 for ; Thu, 09 Feb 2017 06:27:54 -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: Vicente Vera Cc: emacs-orgmode --001a114b4738677ad1054819c917 Content-Type: text/plain; charset=UTF-8 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? > > --001a114b4738677ad1054819c917 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Isn't

#+BEGIN_EXAMPLE
Long block
#+END_EXAMPLE

what yo= u want?

John

-----------------------------------
= Professor John Kitchin=C2=A0
Doherty Hall A207F
Department of Chemica= l Engineering
Carnegie Mellon University
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?

--001a114b4738677ad1054819c917-- 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-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Charles C. Berry" Subject: Re: Exporting blocks of text completely verbatim Date: Thu, 9 Feb 2017 11:19:36 -0800 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46588) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cbuFr-000327-U1 for emacs-orgmode@gnu.org; Thu, 09 Feb 2017 14:19:45 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cbuFo-0006Gu-QA for emacs-orgmode@gnu.org; Thu, 09 Feb 2017 14:19:43 -0500 Received: from iport-acv3-out.ucsd.edu ([132.239.0.4]:43500) by eggs.gnu.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.71) (envelope-from ) id 1cbuFo-0006GE-Cn for emacs-orgmode@gnu.org; Thu, 09 Feb 2017 14:19:40 -0500 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: Vicente Vera Cc: emacs-orgmode On Thu, 9 Feb 2017, 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. > Not in recent versions of org. Here is an example of a table that is exported as a table without any html-ization: #+BEGIN_SRC emacs-lisp :results raw (org-export-string-as " ,#+begin_export md | a | | b | ,#+end_export" 'md t) #+END_SRC #+RESULTS: | a | | b | Of course, the comma escapes are stripped before `org-export-string-as' sees the string. HTH, Chuck 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 23:16:19 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a113deb20407eb40548212b03 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59106) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cbxws-0002Z0-Dr for emacs-orgmode@gnu.org; Thu, 09 Feb 2017 18:16:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cbxwr-0004WD-AF for emacs-orgmode@gnu.org; Thu, 09 Feb 2017 18:16:22 -0500 Received: from mail-ot0-x231.google.com ([2607:f8b0:4003:c0f::231]:36328) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cbxwr-0004W9-4G for emacs-orgmode@gnu.org; Thu, 09 Feb 2017 18:16:21 -0500 Received: by mail-ot0-x231.google.com with SMTP id 32so15514596oth.3 for ; Thu, 09 Feb 2017 15:16:21 -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: "Charles C. Berry" Cc: emacs-orgmode --001a113deb20407eb40548212b03 Content-Type: text/plain; charset=UTF-8 You're absolutely right. The MWE I made had a nasty typo that blew everything up! I'm sorry for the noise. The information in the manual still looks misleading to me: #+BEGIN_EXPORT ascii All lines in this block will appear only when using this back-end. #+END_EXPORT (Taken from "12.7 ASCII/Latin-1/UTF-8 export") This doesn't seem to be related to verbatim text. 2017-02-09 19:19 GMT+00:00 Charles C. Berry : > On Thu, 9 Feb 2017, 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. >> >> > Not in recent versions of org. Here is an example of a table that is > exported as a table without any html-ization: > > #+BEGIN_SRC emacs-lisp :results raw > (org-export-string-as > " > ,#+begin_export md > | a | > | b | > ,#+end_export" > 'md t) > > #+END_SRC > > #+RESULTS: > | a | > | b | > > > Of course, the comma escapes are stripped before `org-export-string-as' > sees the string. > > HTH, > > Chuck > --001a113deb20407eb40548212b03 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
You're absolutely right. The MWE I made had a nasty ty= po that blew
everything up! I'm sorry for the noise.

The info= rmation in the manual still looks misleading to me:

#+BEGIN_EXPORT a= scii
All lines in this block will appear only when using this back-end.<= br>#+END_EXPORT

(Taken from "12.7 ASCII/Latin-1/UTF-8 export&qu= ot;)

This doesn't seem to be related to verbatim text.

2017-02-09 19:19 GMT+= 00:00 Charles C. Berry <ccberry@ucsd.edu>:
On Thu, 9 Feb 2017, 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.


 Not in recent versions of org. Here is an example of a table that is export= ed as a table without any html-ization:

#+BEGIN_SRC emacs-lisp :results raw
=C2=A0 (org-export-string-as
=C2=A0 =C2=A0"
=C2=A0 ,#+begin_export md
=C2=A0 | a |
=C2=A0 | b |
=C2=A0 ,#+end_export"
=C2=A0 =C2=A0'md t)

#+END_SRC

#+RESULTS:
| a |
| b |


Of course, the comma escapes are stripped before `org-export-string-as'= sees the string.

HTH,

Chuck

--001a113deb20407eb40548212b03--