From: Bastien <email@example.com>
To: Rob Sargent <firstname.lastname@example.org>
Subject: Re: list re-numbering not working in odt export
Date: Sun, 26 Sep 2021 13:29:54 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Rob Sargent's message of "Thu, 24 Jun 2021 10:45:55 -0600")
Rob Sargent <email@example.com> writes:
> It appears to me that explicitly setting list order number is not
> honoured by the odt export mechanism. The following works on latex
> (list numbering starts at 7) but not on odt (list numbering starts at
> one though the [@7] is stripped from the output (as expect)):
> 1. [@7](/facilities/) The tangible compute infrastructure
> employed by SGSaaS is entirely ...
> I am using org version 9.1.9 and libre office version 18.104.22.168
What happens if you manually fix the list numbering *within* your Org
buffer before exporting it?
It works fine here, and ox-odt.el honors the in-buffer numbers.
I think it's fine to expect the buffer to be up to date before it is
prev parent reply other threads:[~2021-09-26 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 16:45 list re-numbering not working in odt export Rob Sargent
2021-06-24 16:54 ` Eric S Fraga
2021-09-26 11:29 ` Bastien [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).