Re: Form feed characters break odt export

2024-12-28 Thread Ihor Radchenko
Joseph Turner writes: >> Subject: [PATCH v3] ox-odt: Avoid putting forbidden characters into ODT xml > > LGTM! TIL about clicking on ⛔ and warning-suppress-types. Thank you! Thanks for checking! Applied, onto main. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=e16c9ed54f --

Re: Form feed characters break odt export

2024-12-28 Thread Joseph Turner
Ihor Radchenko writes: > Joseph Turner writes: > >> From ce506caa0bffbd243a2aba384f75f7aaac7fdc4b Mon Sep 17 00:00:00 2001 >> From: Ihor Radchenko >> Date: Fri, 27 Dec 2024 10:21:02 + >> Subject: [PATCH] ox-odt: Avoid putting forbidden characters into ODT xml > > Thanks for helping with the

Re: Form feed characters break odt export

2024-12-28 Thread Ihor Radchenko
Joseph Turner writes: > From ce506caa0bffbd243a2aba384f75f7aaac7fdc4b Mon Sep 17 00:00:00 2001 > From: Ihor Radchenko > Date: Fri, 27 Dec 2024 10:21:02 + > Subject: [PATCH] ox-odt: Avoid putting forbidden characters into ODT xml Thanks for helping with the patch! I modified it further, addi

Re: Form feed characters break odt export

2024-12-27 Thread Joseph Turner
Ihor Radchenko writes: [...] > +(defconst org-odt-forbidden-char-re > + (rx (not (in ?\N{U+9} ?\N{U+A} ?\N{U+D} > + (?\N{U+20} . ?\N{U+D7FF}) > + (?\N{U+E000} . ?\N{U+FFFD}) > + (?\N{U+1} . ?\N{U+10} Indentation mismatch ^ > + "Regexp matching

Re: Form feed characters break odt export

2024-12-27 Thread Ihor Radchenko
Joseph Turner writes: > Thanks, Ihor! Tested working on my machine. > > Here's another potential solution to consider, which adds a defcustom to > let the user decide how to handle forbidden characters: > > https://github.com/kjambunathan/org-mode-ox-odt/commit/07fde1e9b7cdda3e3ef8136f5b1d478499

Re: Form feed characters break odt export

2024-12-25 Thread Joseph Turner
Max Nikulin writes: > On 21/12/2024 10:56, Max Nikulin wrote: >> On 21/12/2024 08:48, Joseph Turner wrote: >>> https://github.com/bohonghuang/org-srs/pull/10#issuecomment-2557417871 >> In this specific context a workaround should be >> #+begin_comment >> ^L >> #+end_comment > > To avoid confusion

Re: Form feed characters break odt export

2024-12-25 Thread Joseph Turner
Ihor Radchenko writes: > Christian Moe writes: > >> I don't think it's specific to ODT or LibreOffice, it's the underlying >> XML 1.0 spec that "discourages" control characters and does not include >> #xC in the range of characters that XML processors must accept. >> >> Spec: https://www.w3.org/

Re: Form feed characters break odt export

2024-12-24 Thread Max Nikulin
On 21/12/2024 10:56, Max Nikulin wrote: On 21/12/2024 08:48, Joseph Turner wrote: https://github.com/bohonghuang/org-srs/pull/10#issuecomment-2557417871 In this specific context a workaround should be #+begin_comment ^L #+end_comment To avoid confusion of other contributors it should be mor

Re: Form feed characters break odt export

2024-12-24 Thread Ihor Radchenko
Max Nikulin writes: > On 24/12/2024 18:04, Christian Moe wrote: >> I don't think it's specific to ODT or LibreOffice, it's the underlying >> XML 1.0 spec that "discourages" control characters and does not include >> #xC in the range of characters that XML processors must accept. > > Pandoc retain

Re: Form feed characters break odt export

2024-12-24 Thread Max Nikulin
On 24/12/2024 18:04, Christian Moe wrote: I don't think it's specific to ODT or LibreOffice, it's the underlying XML 1.0 spec that "discourages" control characters and does not include #xC in the range of characters that XML processors must accept. Pandoc retains "^L" in export to markdown, but

Re: Form feed characters break odt export

2024-12-24 Thread Ihor Radchenko
Christian Moe writes: > I don't think it's specific to ODT or LibreOffice, it's the underlying > XML 1.0 spec that "discourages" control characters and does not include > #xC in the range of characters that XML processors must accept. > > Spec: https://www.w3.org/TR/REC-xml/#charsets > > Some dis

Re: Form feed characters break odt export

2024-12-24 Thread Christian Moe
(re-sending to include the list, apologies, recent mu4e ui changes keep tripping me up) Ihor Radchenko writes: > Joseph Turner via "General discussions about Org-mode." > writes: > >> I can export the following Org content to a .odt file, but the exported >> file cannot be opened ("Read Error.

Re: Form feed characters break odt export

2024-12-23 Thread Ihor Radchenko
Joseph Turner via "General discussions about Org-mode." writes: > 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).") > > --8<---cut here---

Re: Form feed characters break odt export

2024-12-21 Thread Joseph Turner
Max Nikulin writes: > On 21/12/2024 13:52, Joseph Turner wrote: >> Max Nikulin writes: >>> >>> #+begin_comment >>> ^L >>> #+end_comment > >> Thank you! Or even simpler: >> # ^L > > It was first I tried, but Emacs-28.2 demands to decide if Local > Variables should be applied. Oops! You're right

Re: Form feed characters break odt export

2024-12-20 Thread Max Nikulin
On 21/12/2024 13:52, Joseph Turner wrote: Max Nikulin writes: #+begin_comment ^L #+end_comment Thank you! Or even simpler: # ^L It was first I tried, but Emacs-28.2 demands to decide if Local Variables should be applied. You may ask Emacs developers for a *plain text* spell to stop pr

Re: Form feed characters break odt export

2024-12-20 Thread Joseph Turner
Max Nikulin writes: > 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

Re: Form feed characters break odt export

2024-12-20 Thread Max Nikulin
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/boh

Form feed characters break odt export

2024-12-20 Thread General discussions about Org-mode.
Tested on GNU Emacs 29.4 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.41, cairo version 1.18.0) Org mode version 9.7.6 (9.7.6-7a4527 @ /home/joseph/.emacs.d/elpa/org-9.7.6/) I can export the following Org content to a .odt file, but the exported file cannot be opened ("Read Error. Format erro