-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Problem with <code> section in footnote #252
Comments
The issue can be re-produced by exporting a wiki page with the following content:
|
Any progress on this? |
No, no news yet. |
It could happen that usage of footnotes broke the document by generating a document that did not conform to the ODT format specification. To be more precise it could happen that paragraph elements were not closed properly.
@drwetter I hope this is fixed now, please re-test. I did not publish this change yet so please manually install the master branch for testing (=manually install this version https://github.com/LarsGit223/dokuwiki-plugin-odt/archive/master.zip). |
who is LarsGit223? I got a 404 on https://github.com/LarsGit223 , so also if I can download the master.zip. That's not trustworthy to me. |
That's me. Just changed my username a few days ago. It looks like repository addresses are forwarded from my old username but not the profile/main page. |
(copied from #229 (comment))
I ran into the same issue as in #229. My plugin is from July 2019.
If I open the document straight away with libreoffice I get the (sorry, German) message Formatfehler in Teildokument content.xml bei 2324,10(Zeile,Spalte) in der Datei entdeckt. . When I open in the archive the content with ark I get a similar message in English error on line 2324 at column 10: Opening and ending tag mismatch: note-body line 0 and p.
xmllint:
I can't hand over the documents, sorry. But I had in the two documents in question a footnote
(())
which contained<code>
sections. Once I converted the footnote from(())
-->()
it worked.So I guess that should be pretty much reproducible.
The text was updated successfully, but these errors were encountered: