Pedro Andres Aranda Gutierrez <[email protected]> writes:
> 1. I would appretiate your help in deciding whether you want the LaTeX
> packages to be in monotype or just spelt out (babel vs. =babel= vs
> ~babel~)
The basis is in doc/Documentation_Standards.org:
- When to use = ... = or ~ ... ~ markup:
+ files or extensions use = ... =,
+ anything that is meant to be written in the Org buffer uses = ... =,
+ any meaningful token in a programming language uses ~ ... ~.
LaTeX is somewhat awkward in this regard - latex constructs are
generally recognized as Org markup as well. Also, the de facto manual is
not itself very consistent on using =...= vs ~...~.
In my mind, things that go to LaTeX preamble are more like "programming
language" and should use ~...~. So, I prefer ~...~ slightly over
=...=. This is not something I feel very strongly about though.
> 2. It would also be helpful to understand the best way of handling the
> keyword vs. export setting issue.
I personally think that export setting should be preferred. When we talk
about keyword, it is limited to that specific keyword in Org buffer:
#+KEYWORD_NAME. In contrast, export setting is more general - many
settings can be set via (1) keyword; (2) #+OPTION; (3) Elisp variable.
So, by mentioning keyword, you may create an impression that other way
to set things up are not available.
--
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
