emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Torsten Wagner <torsten.wagner@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: [odt] Export of LaTeX Fragments
Date: Mon, 23 Apr 2012 23:57:57 +0900	[thread overview]
Message-ID: <CAPaq-gM6Eht3PpAy3A3odcnzBZCDEDxGAabwbiuPR2uJ7knTHA@mail.gmail.com> (raw)
In-Reply-To: <87vckq1ozv.fsf@gnu.org>

Hi Bastien,
I agree.
Some, I used more of a habit reasons (how many orgers are latexers?!
;) ) and they have a org-replacement.
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.

Thanks

Torsten


On 23 April 2012 23:50, Bastien <bzg@gnu.org> wrote:
> Hi Thorsten,
>
> Torsten Wagner <torsten.wagner@gmail.com> writes:
>
>> I have a minor problem, I used some LaTeX format commands. I know I
>> might get away by replacing \textbf with *<text>*, etc.
>
> Yes, that's the way to go.  Should be quick with M-x replace-regexp.
>
>> But know its
>> there already. Sure it worked out great for the LaTeX-PDF export.
>> However, in openoffice I had stuff like \textbf{text}. I was
>> wondering, the exporter is doing all this nifty work already, could we
>> have a flag to replace the most common Linux inline text-formats by
>> the corresponding odt format?
>
> Mhh... I think it would be too hackish.  Converting \textbf{...} to
> *...* in .org files just for converting them back to another format
> means that \textbf{...} shouldnot be used on the first place.  But
> maybe I'm misunderstanding something...
>
> Best,
>
> --
>  Bastien

next prev parent reply	other threads:[~2012-04-23 14:58 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 [this message]
2012-04-23 15:08     ` Bastien
2012-04-23 17:30       ` Darlan Cavalcante Moreira

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=CAPaq-gM6Eht3PpAy3A3odcnzBZCDEDxGAabwbiuPR2uJ7knTHA@mail.gmail.com \
    --to=torsten.wagner@gmail.com \
    --cc=bzg@gnu.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

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).