From: Darlan Cavalcante Moreira <darcamo@gmail.com>
To: Bastien <bzg@altern.org>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: [odt] Export of LaTeX Fragments
Date: Mon, 23 Apr 2012 14:30:01 -0300 [thread overview]
Message-ID: <4f95919d.e41c340a.0358.78e9@mx.google.com> (raw)
In-Reply-To: <87mx621o6a.fsf@altern.org>
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 <bzg@altern.org> wrote:
>
> Torsten Wagner <torsten.wagner@gmail.com> 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
>
prev parent reply other threads:[~2012-04-23 17:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 14:41 [odt] Export of LaTeX Fragments Torsten Wagner
2012-04-23 14:50 ` Bastien
2012-04-23 14:57 ` Torsten Wagner
2012-04-23 15:08 ` Bastien
2012-04-23 17:30 ` Darlan Cavalcante Moreira [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4f95919d.e41c340a.0358.78e9@mx.google.com \
--to=darcamo@gmail.com \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).