From: Jambunathan K <kjambunathan@gmail.com>
To: Rainer Stengele <rainer.stengele@diplan.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: question about ODT export behavior
Date: Thu, 14 Jul 2011 01:45:07 +0530 [thread overview]
Message-ID: <81oc0yaqes.fsf@gmail.com> (raw)
In-Reply-To: <817h7mce7q.fsf@gmail.com> (Jambunathan K.'s message of "Wed, 13 Jul 2011 22:25:37 +0530")
Jambunathan K <kjambunathan@gmail.com> writes:
> Rainer Stengele <rainer.stengele@diplan.de> writes:
>
>> Hi,
>>
>> having this in an org file:
>> ----------------------------------
>> * Test
>> ** header 2
>> - item 1
>> * subitem 11
>> * subitem 12
>> - item 2
>> * subitem 21
>> * subitem 22
>> ----------------------------------
>
> Could you please post your complete #+OPTIONS line - specifically the
> `H: ' and `toc: ' option?
Looking at the code, I believe these options may not be relevant (for
the odt exporter)
Your org file doesn't use an explicit line break or timestamps. So the
only scenario under which line breaks can occur is precisely when you
have actually requested them.
Check this variable or the corresponding OPTIONS directive.
,----[ C-h v org-export-preserve-breaks RET ]
| org-export-preserve-breaks is a variable defined in `org-exp.el'.
| Its value is nil
|
| Documentation:
| Non-nil means preserve all line breaks when exporting.
| Normally, in HTML output paragraphs will be reformatted. In ASCII
| export, line breaks will always be preserved, regardless of this variable.
|
| This option can also be set with the +OPTIONS line, e.g. "\n:t".
|
| You can customize this variable.
|
| [back]
`----
> How exactly are you exporting - Are you exporting the file, a subtree,
> region etc etc?
>
> What interactive command are you using for export?
>
>> and exporting to ODT I get (I simply copied the Org doc contents via
>> clipboard) I get this:
>>
>> ----------------------------------
>> Test
>> Table of Contents
>> 1. header 2
>> 1. header 2
>> item 1
>>
>> subitem 11
>>
>> subitem 12
>>
>> item 2
>>
>> subitem 21
>>
>> subitem 22
>> ----------------------------------
>>
>> Why do I get extra lines between the items and subitems?
>
> This is beacause there is an explicit line break at the end of the list
> items.
>
> If you open content.xml and remove the <text:line-break/> and save the
> buffer, does the altered odt file match your expectations.
>
> If you export the above outline with the same settings, does the HTML
> exporter also introduce <br/> at the end of the list items?
IIRC, the (x)html exporter adds a line break after emitting an headline
which is listified.
> odt exporter is a derived from the html exporter and mimics the HTML
> exporter mindlessly. I believe the line breaks can be removed.
The odt exporter doesn't emit the line break like the xhtml
exporter. (May be I was a bit mindful while typing out org-odt.el) So
the options H, toc etc may not be relevant.
>
> Once I get the relevant details from you I can post a patch after a
> closer look.
>
>> Where or how can I adjust the behaviour of the exporter?
>>
>> I'll attach the org file.
>>
>> - Rainer
>>
--
next prev parent reply other threads:[~2011-07-13 20:15 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
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 [this message]
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=81oc0yaqes.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rainer.stengele@diplan.de \
/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).