From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Kyeong Soo (Joseph) Kim" <kyeongsoo.kim@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Changed behaviours of LaTeX exporter in version 8.0+
Date: Wed, 17 Sep 2014 21:01:58 +0200 [thread overview]
Message-ID: <87d2aujck9.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CACsgZ=rBy0R6tkiyYc5t+hAu9KKBZu=++f6Lpmj6tRcPhTmrxQ@mail.gmail.com> (Kyeong Soo Kim's message of "Wed, 17 Sep 2014 22:54:16 +0800")
Hello,
"Kyeong Soo (Joseph) Kim" <kyeongsoo.kim@gmail.com> writes:
> 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
>
[...]
> 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.
AUTHOR, like TITLE, and DATE, now expect Org syntax, not LaTeX code. You
can insert raw LaTeX using an export snippet: @@latex:\\@@. Your author
line would then be
#+AUTHOR: Joseph Kim@@latex:\\@@Department of Electrical and Electronic Engineering@@latex:\\@@Example University
Note that you can shorten this with a macro.
> 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
#+MACRO: keywords AAA, BBB, CCC
and then use
#+BEGIN_IEEEkeywords
{{{keywords}}}.
#+END_IEEEkeywords
> Because the keyword environment in IEEE LaTeX class is case-sensitive,
> again it results in LaTeX compilation error.
I fixed it in master. It will land in Org 8.3. Meanwhile, you can use
a filter to upcase IEEE in your special blocks.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-09-17 19:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 14:54 Changed behaviours of LaTeX exporter in version 8.0+ Kyeong Soo (Joseph) Kim
2014-09-17 19:01 ` Nicolas Goaziou [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-09-18 4:50 Kyeong Soo (Joseph) Kim
2014-09-18 7:07 ` Kyeong Soo (Joseph) Kim
2014-09-18 7:32 ` Kyeong Soo (Joseph) Kim
2014-09-18 16:10 ` Richard Lawrence
[not found] ` <CACsgZ=r1vzPQg1KB3N7j6Mn+nyu=PUrxJCeRr5ebqmpywsQ0bg@mail.gmail.com>
2014-09-19 15:49 ` Richard Lawrence
2014-09-20 15:32 ` Kyeong Soo (Joseph) Kim
2014-09-22 16:00 ` Nicolas Goaziou
2014-09-23 3:03 ` Kyeong Soo (Joseph) Kim
2014-09-27 22:01 ` Nicolas Goaziou
2014-09-29 4:51 ` Kyeong Soo (Joseph) Kim
2014-09-29 7:07 ` Nicolas Goaziou
2014-09-29 7:57 ` Kyeong Soo (Joseph) Kim
2014-09-29 8:53 ` Rasmus
2014-09-29 9:59 ` Kyeong Soo (Joseph) Kim
2014-09-29 10:09 ` Rasmus
2014-09-29 12:18 ` Kyeong Soo (Joseph) Kim
2014-09-29 14:18 ` Rasmus
2014-09-29 14:18 ` Rasmus
2014-10-01 9:39 ` Kyeong Soo (Joseph) Kim
2014-09-18 15:47 ` Richard Lawrence
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d2aujck9.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=kyeongsoo.kim@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).