From: Rainer Stengele <rainer.stengele@diplan.de>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: question about ODT export behavior
Date: Wed, 13 Jul 2011 17:04:16 +0200 [thread overview]
Message-ID: <4E1DB3F0.1050200@diplan.de> (raw)
In-Reply-To: <87r55u1cqe.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 705 bytes --]
Am 13.07.2011 16:23, schrieb Bastien:
> Rainer Stengele <rainer.stengele@diplan.de> writes:
>
>> I'll attach the org file.
>
> You forgot the org file, you just attached the odt file.
>
> I don't know when Jambunathan can have a loot at this, but please
> bare in mind that such formatting issues are relatively hard to fix
> (talking from experience).
>
> Thanks,
>
Org file is attached.
I think this is the most simple org file - nothing special
- and the odt file just extends some extra lines, so I thought this
to be a fundamental issue.
I would like to be able to export the minutes of a meeting but cannot as my colleagues
will wonder why I put all these extra lines in ...
Thanks,
Rainer
[-- Attachment #2: test.org --]
[-- Type: text/org, Size: 115 bytes --]
* Test
** header 2
- item 1
* subitem 11
* subitem 12
- item 2
* subitem 21
* subitem 22
next prev parent reply other threads:[~2011-07-13 15:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 13:20 question about ODT export behavior Rainer Stengele
2011-07-13 14:23 ` Bastien
2011-07-13 15:04 ` Rainer Stengele [this message]
2011-07-13 16:14 ` Bastien
2011-07-13 20:18 ` Jambunathan K
2011-07-13 16:55 ` Jambunathan K
2011-07-13 20:15 ` Jambunathan K
2011-07-14 6:50 ` Rainer Stengele
2011-07-14 15:44 ` Bastien
2011-07-15 5:54 ` Jambunathan K
2011-07-15 20:34 ` Renzo Been
2011-07-16 20:13 ` ODT Charset/Encoding issues (was question about ODT export behavior) Jambunathan K
2011-07-17 14:12 ` Renzo Been
2011-07-17 19:13 ` Jambunathan K
2011-07-18 8:59 ` Bastien
2011-07-22 14:38 ` [PATCH 1/2] org-odt: Improve customization of org-export-odt-styles-file Jambunathan K
2011-07-22 15:49 ` Bastien
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=4E1DB3F0.1050200@diplan.de \
--to=rainer.stengele@diplan.de \
--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).