emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: mousebot <mousebot@disroot.org>
To: emacs-orgmode@gnu.org
Subject: Re: is org-export-preserve-breaks incompatible with org verse blocks?
Date: Wed, 2 Dec 2020 17:08:26 +0100	[thread overview]
Message-ID: <c2fe2027-df38-d7b0-9899-b1abdc04abef@disroot.org> (raw)
In-Reply-To: <53f7522e-1af5-7338-a86b-88a51a16fa30@disroot.org>

hi again,

i had a look at the content.xml file in each case.

with org-export-preserve-breaks disabled, whitespace is exported (correctly) like so:

<text:line-break/>
 <text:s text:c="5"/>text here indented 5 spaces.<text:line-break/>

with the option enabled, the the spaces are directly transferred to the file:

<text:line-break/>     text printed after 5 spaces, which are not properly preserved in the org file.<text:line-break/>

regards,
m


On 23/11/2020 19:19, mousebot wrote:
> hi org,
> 
> i use verse blocks to export to odt in a way that preserves whitespace. if i enable org-export-preserve-breaks, whitespace in verse blocks is not preserved: any spaces used to indent text from the left margin are reduced to a single space. is this intended behavior? i had hoped to be able to use both features in my document.
> 
> example:
> 
> #+begin_verse
> here you are,
>         doing your
>     darned
>               best
> to export
> #+end_verse
> 
> will export as
> 
> here you are
>  doing your
>  darned
>  best
> to export
> 
> i tested this by loading emacs -Q, evaluating (setq org-export-preserve-breaks t), then using the normal org export dispatch, with no template.
> 
> best 
> m
> 


      reply	other threads:[~2020-12-02 16:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-23 18:19 is org-export-preserve-breaks incompatible with org verse blocks? mousebot
2020-12-02 16:08 ` mousebot [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=c2fe2027-df38-d7b0-9899-b1abdc04abef@disroot.org \
    --to=mousebot@disroot.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).