[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] [odt] Export of LaTeX Fragments
From: |
Darlan Cavalcante Moreira |
Subject: |
Re: [O] [odt] Export of LaTeX Fragments |
Date: |
Mon, 23 Apr 2012 14:30:01 -0300 |
User-agent: |
Wanderlust/2.15.9 (Almost Unreal) Emacs/24.1 Mule/6.0 (HANACHIRUSATO) |
Since org already accepts \SomeCommandName, maybe org-mode could provide
some very basic functionality for the user to provide definitions for these
macros for each (desired) output format. For instance, there could be a
list similar to
#+begin_src emacs-lisp
(
("somecommand" :html 'somecommand-html-export :latex ;
somecommand-latex-export :buffer 'somecommand-buffer-change)
("someothercomand" :html someothercomand-html-export)
)
#+end_src
The export function definitions should be provided by the user for each
desired export format and any unspecified format should do what org-mode
does right now. The "buffer" format would be a function for changing the
way the command (and its argument) look in the org-buffer.
I'm no lisp programmer and this is probably no the best way to implement
this feature, but I think this flexibility could allow orgers to tweak
org-mode to their needs easily.
--
Darlan
At Mon, 23 Apr 2012 17:08:13 +0200,
Bastien <address@hidden> wrote:
>
> Torsten Wagner <address@hidden> writes:
>
> > However, whats with "\," "\mbox{}" "\noindent" and maybe some others?
> > They helped me to tweak the formatting at some points where the
> > standard stuff did not make much sense.
>
> There commands are meaningful in a TeX context, and there is not
> necessary a precise translation of their meanings in other contexts
> like ODT documents.
>
> In Org file, it is better to stick to Org syntax -- even if some
> flexibility is allowed with \noindent and friends while converting
> to LaTeX.
>
> --
> Bastien
>