Re: [O] Use [org-latex] or [org-e-latex] for exporter problems

[Sebastien Vauban]

Hi Jambunathan,

Jambunathan K wrote:
> Please use [org-latex] or [org-e-latex] while reporting exporter
> problems.  Likewise for other exporters.

This was code for Beamer slides, hence using the old LaTeX exporter.

> If you are exporting with old exporter, export once with the new
> exporter also, just for the fun of it.

Converted the Beamer slideware to a document:

--8<---------------cut here---------------start------------->8---
#+TITLE:     Org code in slide
#+DATE:      2012-06-04 Mon
#+DESCRIPTION:
#+KEYWORDS:
#+LANGUAGE:  en

#+LaTeX_CLASS: article
#+LaTeX_HEADER: \lstdefinelanguage{org}{%
#+LaTeX_HEADER:   morekeywords={:results, :session, :var, :noweb, :exports},
#+LaTeX_HEADER:   sensitive=false,
#+LaTeX_HEADER:   morestring=[b]",
#+LaTeX_HEADER:   morecomment=[l]{\#},
#+LaTeX_HEADER: }
#+LaTeX_HEADER: \lstset{%
#+LaTeX_HEADER:   mathescape=false,
#+LaTeX_HEADER:   columns=flexible,
#+LaTeX_HEADER:   keepspaces=true
#+LaTeX_HEADER: }

* Contexte

- I want to show (in Beamer slides) how to write an Org table.

- I first need to add Org as a language to the listings settings -- that's the
  purpose of the above =BEAMER_HEADER_EXTRA= lines.

- I then write an Org source block, which is exported to LaTeX... but not
  fully... The line =#+ATTR_LaTeX: align=rrl= disappears from the exported code!

- See ECM.

* ECM

Here's a "simple" but already powerful Org table:

#+begin_src org :exports code
,#+ATTR_LaTeX: align=rrl
,| Janvier | 1300 | \EUR |
,| Fevrier | 1280 | \EUR |
,|---------+------+------|
,| Total   | 2580 | \EUR |
,#+TBLFM: @3$2=vsum(@address@hidden)
#+end_src

I can't get it properly exported to LaTeX, because the line =ATTR_LaTeX= is
*removed from the published code block* (compare the Org source of the code
block with what's shown in the PDF).
--8<---------------cut here---------------end--------------->8---

- Same problem with the old exporter
- It works with the new one -- but N/A yet for slides; anyway, this is good
  news.

> More importantly report problems or inconsistencies. This will immensely
> help to improve the current backends and associated infrastructure.

That, I clearly do (and will still do)...

Best regards,
  Seb

-- 
Sebastien Vauban