On Sun, 14 Jun 2015 11:14:13 +0200
wero_sacero <mail2w...@gmail.com> wrote:

> Thank you for the reply.
> But I don't think it's a good idea. For example: what can I do if want
> to put a text like the title of my file in the latex header? is there
> an other way?
> I know I can use the \@title function of latex, it works. but I need
> it also for email, date, etc.. macro would be exactly what I want, but
> maybe someone has thought something better!

I have a set-up to be able to use title, author etc. in LaTeX blocks.

Every one of those documents has a (filled out) header like:

#+AUTHOR: Robert Klein
#+EMAIL: rokl...@roklein.de
#+LaTeX_HEADER: \newcommand{\mySubtitle}{}
#+LaTeX_HEADER: \newcommand{\myProducer}{org-mode / pdflatex}

Further down I #include a largish file with my standard settings which
has the following in it:

#+name: docinfo
#+begin_src elisp :exports none
  (let ((props (org-export-get-environment)))
    (concat  "#+LaTeX_HEADER: \\newcommand{\\myTitle}{"
              (plist-get props :title))
             "#+LaTeX_HEADER: \\newcommand{\\myAuthor}{"
              (plist-get props :author))
             "#+LaTeX_HEADER: \\newcommand{\\myDate}{"
              (plist-get props :date))
             "#+LaTeX_HEADER: \\newcommand{\\myCreator}{"
              (plist-get props :creator))
             "#+LaTeX_HEADER: \\newcommand{\\myKeywords}{"
              (plist-get props :keywords))
             "#+LaTeX_HEADER: \\newcommand{\\mySubject}{"
              (plist-get props :description))

#+CALL: docinfo() :exports results :results raw

So, further down I can use all those \myTitle etc. commands in LaTeX,

#+LaTeX_HEADER: % Hyperref PDF Info
#+LaTeX_HEADER: \hypersetup{
#+LaTeX_HEADER:   pdfinfo={
#+LaTeX_HEADER:     Author={\myAuthor},
#+LaTeX_HEADER:     Title={\myTitle},
#+LaTeX_HEADER:     Subject={\mySubject},
#+LaTeX_HEADER:     Keywords={\myKeywords},
#+LaTeX_HEADER:     Creator={\myCreator},
#+LaTeX_HEADER:     Producer={\myProducer}
#+LaTeX_HEADER:   }}

I also use document-wide properties for data org doesn't
handle, e.g.

# note: classify as `open access', `internal', `confidential'
#+Property: documenttype   form sheet
#+Property: classification open access

though I don't use it in a LaTeX block but in a elisp block w/ org

#+name: dochead
#+header: :var trustlevel=(org-entry-get nil "classification" t)
#+header: :var doctype=(org-entry-get nil "documenttype" t)
#+begin_src elisp :exports none :results value raw
  (let ((props (org-export-get-environment)))
    (concat "#+ATTR_HTML: :rules all\n"
            "#+ATTR_LATEX: :environment tabu :align ll|ll :booktabs
            t :width \\textwidth\n"
            "| Document Type:   | " doctype
            " | Classification: | " trustlevel " |\n"
            "| Document Title: | " (org-element-interpret-data
                                    (plist-get props :title))
            " | Author: | " (org-element-interpret-data
                                           (plist-get props :author))
                                           " |\n"))

#+Call: dochead() :exports results :results raw

I use this code to generate output intended for both HTML and LaTeX, so
I can't use the \myXXX commands above (and, I'm creating org code here
to be exported in the course of the current export).

I won't claim this is `something better' than using {{{title}}} or so,
but once I had the set-up working I'm happy with it.

Best regards

> Thanks again!
> Wero
> 2015-06-13 18:58 GMT+02:00, Nicolas Goaziou <m...@nicolasgoaziou.fr>:
> > Hello,
> >
> > wero_sacero <mail2w...@gmail.com> writes:
> >
> >> hi, is there anybody that know why in the lastest version of
> >> org-mode exporting in latex, the macro like {{{title}}} is not
> >> expanded if it is put in a begin_latex?
> >>
> >> In version 7.9... it was working, and I think it should work also
> >> now.
> >>
> >> Can anyone explain me if it is a non-feature or a bug?
> >
> > It is a non-feature. Macro are not allowed in raw or verbatim
> > environments.
> >
> > Regards,
> >
> > --
> > Nicolas Goaziou
> >

Reply via email to