From: Heinz Tuechler <tuechler@gmx.at>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: vertical spacing between lines in a list at odt-export
Date: Sun, 6 Sep 2020 10:23:13 +0200 [thread overview]
Message-ID: <8c0aa405-55b6-e0c1-fa0b-25733fc54824@gmx.at> (raw)
In-Reply-To: <87imcsgvbm.fsf@gnu.org>
Dear Bastien,
thank you for you for patience. It is a minor issue, still I try to
explain by an example (see below).
If the example below is exported to LibreOffice I am happy with all the
format, except the vertical spacing between list elements, which results
from the vertical space after each paragraph in the "Textkörper" format.
I could change this format, but that would affect all paragraphs, not
only the lists.
BTW, there is a convenient solution for Latex-export
(https://emacs.stackexchange.com/questions/47864/org-mode-set-separation-length-between-elements-of-a-list).
best regards,
Heinz
Example org file:
* example project
This is an example project description ... more text.
The motivation for this research resulted mainly from the following
clinical questions.
- Is there a need for intense therapy?
- cytostatic
- transplantation
- If yes, when should the therapy start?
- immediately after diagnosis
- at first signs of progression
- after relapse
Some of these questions were partially answered by Genius et al.,
2003 and ... more text.
** introduction
The main purpose ... more text.
** material
Data was contributed from ten centers ... more text.
All data collection was done between 2010 and 2018. Informed consent
was obtained by each patient.
The following inclusion and exclusion criteria were applied.
- inclusion criteria
- age > 16
- stable disease for >= 2 months
- etc.
- exclusion criteria
- other malignant disease
- missing cytogenetics
- etc.
All inclusion criteria had to be fulfilled. No exclusion criterion
had to be fulfilled.
A data review was performed by two coauthors (AB, TC).
** methods
The following measures were used to describe relations:
- for numeric data: Pearson correlation
- for ordered data: Kendall's tau
- for unordered data
- dichotomous: odds ratio
- polytomous: contingency coefficient
As level of significance .05 was set. Hypotheses were defined
two-sided. In view of the exploratory nature of the study no adjustment
for multiple testing was applied.
** results
The main result ... more text.
Bastien wrote/hat geschrieben on/am 05.09.2020 16:19:
> Dear Heinz,
>
> Heinz Tuechler <tuechler@gmx.at> writes:
>
>> thank you - I know that. The problem seems to be that in the odt-file
>> all lists, as well as all "normal" text share the same format. In my
>> German version of LibreOffice it is called "Textkörper".
>> So, if I modify that format in a ODT_STYLES_FILE it changes all the
>> "normal" text, not only the lists.
>> If I were able to assign a different format to lists, then your proposal
>> would be the optimal solution. Until now I did not find out, how to
>> assign such a different format to lists.
>
> Perhaps you can send a feature request to the LibreOffice team?
>
>> Why do I use lists at all? It is, because they offer a hierarchical way
>> of description, but, contrary to headings and subheadings, after the end
>> of a list, you jump to the same level as before the list. Instead with
>> headings and subheadings I think, I can go back to the level at the
>> beginning only by inserting a new (sub)heading of the desired level.
>> Maybe I am missing some alternative.
>
> Perhaps try M-RET in a heading or explore `org-adapt-indentation' (I'm
> not sure I completely grok your need, hence the suggestions.)
>
> Best,
>
prev parent reply other threads:[~2020-09-06 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-16 8:13 vertical spacing between lines in a list at odt-export Heinz Tuechler
2020-09-04 10:03 ` Bastien
2020-09-04 10:58 ` Heinz Tuechler
2020-09-05 8:25 ` Bastien
2020-09-05 10:45 ` Heinz Tuechler
2020-09-05 14:19 ` Bastien
2020-09-06 8:23 ` Heinz Tuechler [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=8c0aa405-55b6-e0c1-fa0b-25733fc54824@gmx.at \
--to=tuechler@gmx.at \
--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
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).