From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Kyeong Soo (Joseph) Kim" Subject: Changed behaviours of LaTeX exporter in version 8.0+ Date: Wed, 17 Sep 2014 22:54:16 +0800 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a113398dabaa1fd0503440a5a Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49882) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XUGcj-0008Kp-3N for emacs-orgmode@gnu.org; Wed, 17 Sep 2014 10:54:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XUGce-0006P6-8O for emacs-orgmode@gnu.org; Wed, 17 Sep 2014 10:54:25 -0400 Received: from mail-qa0-x234.google.com ([2607:f8b0:400d:c00::234]:42117) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XUGce-0006Ob-3w for emacs-orgmode@gnu.org; Wed, 17 Sep 2014 10:54:20 -0400 Received: by mail-qa0-f52.google.com with SMTP id m5so1889358qaj.25 for ; Wed, 17 Sep 2014 07:54:16 -0700 (PDT) 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 --001a113398dabaa1fd0503440a5a Content-Type: text/plain; charset=UTF-8 I recently upgraded my org-mode from 7.x to 8.2.7c (bundled with a Windows Emacs package for ESS) and have been struggling with changed behaviours of LaTeX exporter since. Below is the list of those changes: 1. Double backslashes (for line break) embedded in a string for "#+AUTHOR:" With version 7.x, the following line #+AUTHOR: Joseph Kim\\Department of Electrical and Electronic Engineering\\Example University is exported to \author{Joseph Kim\\Department of Electrical and Electronic Engineering\\Example University} With version 8.2.7c, however, the same line is exported to \author{Joseph Kim$\backslash$\Department of Electrical and Electronic Engineering$\backslash$\Example University} which results in LaTeX compilation error. 2. Accessing the value of "#+KEYWORDS:" and change of cases in "org-special-blocks" For keywords section in IEEE papers, I used to have the following settings: #+KEYWORDS: AAA, BBB, CCC ... #+BEGIN_IEEEkeywords {{{KEYWORDS}}}. #+END_IEEEkeywords which turns into \begin{IEEEkeywords} AAA, BBB, CCC. \end{IEEEkeywords} Version 8.2.7c, however, produces the following from the same settings: \begin{ieeekeywords} . \end{ieeekeywords} Because the keyword environment in IEEE LaTeX class is case-sensitive, again it results in LaTeX compilation error. Now I wonder whether I should go back to 7.x or not in spite of many improvements in the new version. Any advice or help would be greatly appreciated in this regard. Regards, Joseph --001a113398dabaa1fd0503440a5a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I recently upgraded my org-mode from 7.x to 8.2.7c (bundle= d with a Windows Emacs package for ESS) and have been struggling with chang= ed behaviours of LaTeX exporter since.

Below is the list= of those changes:


1. Double backsl= ashes (for line break) embedded in a string for "#+AUTHOR:"
=

With version 7.x, the following line

#+AUTHOR: Joseph Kim\\Department of Electrical and Electronic Engine= ering\\Example University

is exported to

\author{Joseph Kim\\Department of Electrical and El= ectronic Engineering\\Example University}


With version 8.2.7c, however, the same line is exported to
=

\author{Joseph Kim$\backslash$\Department of Electrical= and Electronic Engineering$\backslash$\Example University}
<= br>
which results in LaTeX compilation error.


2. Accessing the value of "#+KEYWORDS:" and = change of cases in "org-special-blocks"

= For keywords section in IEEE papers, I used to have the following settings:=

#+KEYWORDS: AAA, BBB, CCC
...
#+BEGIN_IEEEkeywords
{{{KEYWORDS}}}.
= #+END_IEEEkeywords

which turns into

\begin{IEEEkeywords}
AAA, BBB, CCC.
\end{IEEEkeywords}


Version 8.= 2.7c, however, produces the following from the same settings:
\begin{ieeekeywords}
.
\end{ieeekeywor= ds}


Because the keyword envir= onment in IEEE LaTeX class is case-sensitive, again it results in LaTeX com= pilation error.


Now I wonder whethe= r I should go back to 7.x or not in spite of many improvements in the new v= ersion.

Any advice or help would be greatly apprec= iated in this regard.

Regards,
Joseph
--001a113398dabaa1fd0503440a5a--