From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Kyeong Soo (Joseph) Kim" Subject: Re: Changed behaviours of LaTeX exporter in version 8.0+ Date: Thu, 18 Sep 2014 12:50:24 +0800 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c2caa2f7099405034fb887 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59589) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XUTfu-0002q4-28 for emacs-orgmode@gnu.org; Thu, 18 Sep 2014 00:50:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XUTfp-0001Gp-Q1 for emacs-orgmode@gnu.org; Thu, 18 Sep 2014 00:50:33 -0400 Received: from mail-qc0-x230.google.com ([2607:f8b0:400d:c01::230]:34401) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XUTfp-0001GN-K8 for emacs-orgmode@gnu.org; Thu, 18 Sep 2014 00:50:29 -0400 Received: by mail-qc0-f176.google.com with SMTP id x3so504967qcv.21 for ; Wed, 17 Sep 2014 21:50:24 -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 --001a11c2caa2f7099405034fb887 Content-Type: text/plain; charset=UTF-8 Hello Nicolas, Great thanks for the detailed instructions with clear explanations for the problems. I have addressed all those issues per your suggestions, but put some comments embedded below. Again, many thanks for your great help! Joseph On Thu, Sep 18, 2014 at 3:01 AM, Nicolas Goaziou wrote: -----> snip <----- > > > 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 > > [...] > > > Version 8.2.7c, however, produces the following from the same settings: > > > > \begin{ieeekeywords} > > . > > \end{ieeekeywords} > > I'm surprised {{{KEYWORDS}}} even worked as, AFAIK, it wasn't > documented. Indeed, there is no such macro in Org 8.0. However, you > can define your own > '{{{KEYWORDS}}}' worked without any issues in previous versions, which in fact was suggested by someone in the mailing list or stackoverflow (unfortunately, I couldn't find that via Google any longer). By the way, in Sec. 12.3 of the Org manual (ver. 8.2.7c), 'KEYWORDS' is listed together with 'AUTHOR', 'TITLE' and so on as export keywords. Also, according to Sec. 11.6, those predefined keywords (e.g., #+TITLE:, #+AUTHOR:) can be accessed by {{{title}}} and {{{author}}} like user-defined macros. It seems that there is some inconsistency between the actual behavior and the corresponding manual in export engine of org-mode ver. 8.2.7c. -----> snip <----- --001a11c2caa2f7099405034fb887 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello Nicolas,

Great thanks for the detailed instructions with cle= ar explanations for the problems.

I have addressed all those issues per your suggestions, but put some com= ments embedded below.


Again, many thanks for your great he= lp!

Joseph


On Th= u, Sep 18, 2014 at 3:01 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr= > wrote:

-----> snip <-----

> 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 sett= ings:
>
> #+KEYWORDS: AAA, BBB, CCC
> ...
> #+BEGIN_IEEEkeywords
> {{{KEYWORDS}}}.
> #+END_IEEEkeywords

[...]

> Version 8.2.7c, however, produces the following from the same settings= :
>
> \begin{ieeekeywords}
> .
> \end{ieeekeywords}

I'm surprised {{{KEYWORDS}}} even worked as, AFAIK, it wasn'= t
documented.=C2=A0 Indeed, there is no such macro in Org 8.0.=C2=A0 However,= you
can define your own

'{{{KEYWORDS}}}= ' worked without any issues in previous versions, which in fact was sug= gested by someone in the mailing list or stackoverflow (unfortunately, I co= uldn't find that via Google any longer).

B= y the way, in Sec. 12.3 of the Org manual (ver. 8.2.7c), 'KEYWORDS'= is listed together with 'AUTHOR', 'TITLE' and so on as exp= ort keywords. Also, according to Sec. 11.6, those predefined keywords (e.g.= ,=C2=A0=C2=A0#+TITLE:, #+AUTHOR:) can be accessed by {{{title}}} and {{{aut= hor}}} like user-defined macros.

It seems that the= re is some inconsistency between the actual behavior and the corresponding = manual in export engine of org-mode ver. 8.2.7c.

-= ----> snip <-----
--001a11c2caa2f7099405034fb887--