Hi,
As said, I need a fresh start on this...
I envisage two major steps towards restructuring of the LaTeX output.
1. ox-beamer: putting the theme config as soon as possible.
2. ox-latex: font management (AKA all-tex-fonts)
If we can agree on 1. and psuh the changes to the repo, we could
concentrate on 2, which we can very much simplify from my initial proposal
(This would be the third attempt for me and I can put in the experience
I've gained in my playground).
So, let's try to tackle theme config in ox-beamer first.
My proposal is
Q1: We have a "theme block" for Beamer (with or w/o BEAMER_THEME_PRE):
where do we want to place it?
A1: From my experience in writing a Beamer theme for my lectures I have
learnt that it needs to be a self-contained block that must work with a
LateX preamble as simple as
\usepackage[presentation]{beamer}
\usetheme{my-theme}
Q2: Do we need more LaTeX before \usetheme?
A2: Normally not, but to cater for the exceptions, we can use
BEAMER_THEME_PRE.
An example for such an exception in my use case is using the geometry
package to fine-tune the appearance.
So my proposal is to mimic the behaviour of ox-latex:
- substitute the documentclass by the documentclass+the theme
configuration, instead of putting the theme configuration after
all the packages.
- If a user includes '\\usetheme{}' in the org-latex-class entry
for his/her presentation style, we can decide that we skip
inserting the theme configuration altogether.
IMHO, it makes little sense to add and cater a [THEME] token in the
org-latex-classes, so forget I even dared to mention it ;-)
/PA
--
Fragen sind nicht da, um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
"Sagen's Paradeiser" (ORF: Als Radiohören gefährlich war) => write BE!
Year 2 of the New Koprocracy
This was produced by a human (implied virtues and weaknesses acknowledged)
I'd hate this being fed to any form of AS (sorry AI)...
