From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: [question/patch] How detailed may org.texi be? Date: Wed, 29 Oct 2014 14:24:10 +0100 Message-ID: <8738a7f1qd.fsf@gmx.us> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57677) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XjTEl-0004sn-PT for emacs-orgmode@gnu.org; Wed, 29 Oct 2014 09:24:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XjTEf-0000Sp-D6 for emacs-orgmode@gnu.org; Wed, 29 Oct 2014 09:24:31 -0400 Received: from plane.gmane.org ([80.91.229.3]:52125) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XjTEf-0000Sa-6X for emacs-orgmode@gnu.org; Wed, 29 Oct 2014 09:24:25 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XjTEc-0000M6-Tp for emacs-orgmode@gnu.org; Wed, 29 Oct 2014 14:24:22 +0100 Received: from 46.166.186.240 ([46.166.186.240]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 29 Oct 2014 14:24:22 +0100 Received: from rasmus by 46.166.186.240 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 29 Oct 2014 14:24:22 +0100 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Hi, I would like to push the following patch to org.texi on export behavior of sub/superscripts and LaTeX delimiters. To me it seems relevant, but it's somewhat technical. Is it relevant to include such "implementation" details/choices in org.texi? —Rasmus -- You people at the NSA are becoming my new best friends! --=-=-= Content-Type: text/x-diff Content-Disposition: attachment; filename=0001-org.texi-Clarifications-of-math-subscript-export.patch >From 04e0b5c7ed5329bf62175f58192577b895a10cdb Mon Sep 17 00:00:00 2001 From: rasmus Date: Wed, 29 Oct 2014 14:15:41 +0100 Subject: [PATCH] org.texi: Clarifications of math/subscript export. * org.texi (Subscripts and superscripts), (@LaTeX{} fragments): More information on export output. --- doc/org.texi | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/doc/org.texi b/doc/org.texi index 3c1790a..0d8fa0e 100644 --- a/doc/org.texi +++ b/doc/org.texi @@ -10222,6 +10222,11 @@ The mass of the sun is M_sun = 1.989 x 10^30 kg. The radius of the sun is R_@{sun@} = 6.96 x 10^8 m. @end example +By default super- and subscript are exported as plain text, rather than math, +when exporting to HTML and @LaTeX{}. Thus @code{\beta_t} is exported as +@code{βt} for HTML and @code{\(\beta_@{\text@{t@}@}\)} for +@LaTeX{}. + @vindex org-use-sub-superscripts If you write a text where the underscore is often used in a different context, Org's convention to always interpret these as subscripts can get in @@ -10269,7 +10274,9 @@ math delimiters if the enclosed text contains at most two line breaks, is directly attached to the @samp{$} characters with no whitespace in between, and if the closing @samp{$} is followed by whitespace, punctuation or a dash. For the other delimiters, there is no such restriction, so when in doubt, use -@samp{\(...\)} as inline math delimiters. +@samp{\(...\)} as inline math delimiters. In HTML and @LaTeX{} exports, +inline math are enclosed in @samp{\(...\)} irrespective of whether enclosed +in @samp{$} or @samp{\(...\)} in the Org source. @end itemize @noindent For example: -- 2.1.2 --=-=-=--