On 21/12/2024 08:48, Joseph Turner wrote:
I can export the following Org content to a .odt file, but the exported
file cannot be opened ("Read Error. Format error discovered in the file
in sub-document content.xml at 368,2(row,col).")
[...]
First reported by bohonghuang:
https://github.com/bohonghuang/org-srs/pull/10#issuecomment-2557417871
In this specific context a workaround should be
#+begin_comment
^L
#+end_comment
Or a commented out empty local variables block above.
I have wrote already that I do not like non-printable characters in Org
files.
I admit that special characters either should cause `org-lint' warnings
or should be filtered out by exporters.
Specifically to ^L, there was a request to treat it as a page break by
all exporters (I would prefer some entity or macro instead to not
deviate from plain text markup).
Marvin Gülker. Feature request: export form feed as page break. Sat, 21
Oct 2023 09:42:33 +0200.
<https://list.orgmode.org/87zg0ce6yi....@guelker.eu>
I have not had a close look at another proposed feature, but I suspect
that it might make filtering special characters more tricky. (I would be
happy to hear that I am wrong.)
Nathaniel Nicandro. [PATCH] ANSI color on example blocks and fixed width
elements. Wed, 05 Apr 2023 07:03:43 -0500.
<https://list.orgmode.org/874jpuijpc....@gmail.com>
