From: "Kyeong Soo (Joseph) Kim" <kyeongsoo.kim@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Changed behaviours of LaTeX exporter in version 8.0+
Date: Wed, 17 Sep 2014 22:54:16 +0800 [thread overview]
Message-ID: <CACsgZ=rBy0R6tkiyYc5t+hAu9KKBZu=++f6Lpmj6tRcPhTmrxQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1495 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 2259 bytes --]
next reply other threads:[~2014-09-17 14:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 14:54 Kyeong Soo (Joseph) Kim [this message]
2014-09-17 19:01 ` Changed behaviours of LaTeX exporter in version 8.0+ Nicolas Goaziou
-- 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='CACsgZ=rBy0R6tkiyYc5t+hAu9KKBZu=++f6Lpmj6tRcPhTmrxQ@mail.gmail.com' \
--to=kyeongsoo.kim@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).