From: "Kyeong Soo (Joseph) Kim" <kyeongsoo.kim@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Changed behaviours of LaTeX exporter in version 8.0+
Date: Thu, 18 Sep 2014 15:07:36 +0800 [thread overview]
Message-ID: <CACsgZ=qo904up9Y8pY-oHmACmkAu+Lr444dbK8RFspHOGEi5ww@mail.gmail.com> (raw)
In-Reply-To: <CACsgZ=r_Ko9KkROjuyB4GZU8hVujfuutoqtYHGT66Fu2DkZ_Tw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3001 bytes --]
Nicolas and All,
One further question regarding your suggestion of the use of filter for
special blocks in export:
I just found out that, if I close Emacs and relaunch it, all variables for
filter (i.e., 'org-export-filter-*') are not defined. As a result, the
following elisp codes for the workaround based on both your suggestion and
the filter example in the manual causes void variable error (i.e.,
"Symbol's value as variable is void:
org-export-filter-special-block-function"):
;; workaround solution (until 8.3.0) for case-sensitve handling of
special-block for IEEE LaTeX class
(defun my-latex-filter-ieeekeywords (text backend info)
"Upcase 'IEEE' in IEEEkeywords environment in LaTeX export."
(when (org-export-derived-backend-p backend 'latex)
(replace-regexp-in-string "ieeekeywords" "IEEEkeywords" text)))
(add-to-list 'org-export-filter-special-block-functions
'my-latex-filter-ieeekeywords)
It turns out that those variables are defined only after exporting org file
into LaTeX.
Again, any advice on propor addition of custom filter functions in the
configuration file would be greatly appreciated; maybe the said example in
the manual needs to be updated as well.
Regards,
Joseph
On Thu, Sep 18, 2014 at 12:50 PM, Kyeong Soo (Joseph) Kim <
kyeongsoo.kim@gmail.com> wrote:
> 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 <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
>> 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 <-----
>
[-- Attachment #2: Type: text/html, Size: 5007 bytes --]
next prev parent reply other threads:[~2014-09-18 7:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 4:50 Changed behaviours of LaTeX exporter in version 8.0+ Kyeong Soo (Joseph) Kim
2014-09-18 7:07 ` Kyeong Soo (Joseph) Kim [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2014-09-17 14:54 Kyeong Soo (Joseph) Kim
2014-09-17 19:01 ` Nicolas Goaziou
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=qo904up9Y8pY-oHmACmkAu+Lr444dbK8RFspHOGEi5ww@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).