emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Christian Moe <mail@christianmoe.com>, emacs-orgmode@gnu.org
Subject: Re: [ODT][BUG] Format error on export with table in list structure
Date: Fri, 05 Apr 2024 10:21:25 +0000	[thread overview]
Message-ID: <87zfu8qfdm.fsf@localhost> (raw)
In-Reply-To: <87edxn9z7n.fsf@localhost>

Ihor Radchenko <yantar92@gmail.com> writes:

>> Consider the following minimal example, a nested list with a table in a
>> sub-item (regardless of list types and empty lines):
>>
>> #+BEGIN_EXAMPLE
>> 1. List item
>>    - Sub-item
>>      | Table |
>> #+END_EXAMPLE
>>
>> This causes a format error on ODT export (I'm running Org version
>> 9.5.4). In the content.xml file, just before the final closing
>> </text:list> tag, there appears a </text:list-header> tag without a
>> corresponding opening tag, invalidating the XML.
>
> Confirmed.

Fixed, on main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=ef4364287

Note that ODT format does not allow tables inside lists, so we do
nothing better than a workaround. It is generally not a good idea to
export documents like this to odt.

There is still a bug in a similar scenario when the table is nested even
further:

1. List item
   - Sub-item
     #+begin_textbox
     | Table |
     #+end_textbox

I added a FIXME to the code.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=d491a74fd

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


      reply	other threads:[~2024-04-05 10:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-10 21:17 [ODT][BUG] Format error on export with table in list structure Christian Moe
2022-08-11  4:33 ` Ihor Radchenko
2024-04-05 10:21   ` Ihor Radchenko [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=87zfu8qfdm.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@christianmoe.com \
    --cc=yantar92@gmail.com \
    /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).