Except the numbering, footnote texts of WikiMedia is not <sup>**</sup> The filter can not distinguish footnote numbering and footnote text.
Hello Steven, I exported a footnote from 4.2.5 in Linux Mint using MediaWiki and here is the output i got. ----------------------- Test 1<ref name="ftn0">Test 1</ref> ---- <references/> ----------------------- If you have a document which shows the '<sup>**</sup>' result you mentioned, please supply it to us for testing.
Created attachment 102325 [details] Source Doc Hi Jay, Thank you for your reply. Please check attachment Doc., when I use Writer to open a Word (doc), then export to MediaWiki, footnote texts show "<sup>**</sup>". Note: Docx no such issue.
Hello Steven, I outputted your sample document as MediaWiki and here is the result. ----------------------- == Test == This chapter focuses on '''claims,''' arguably the most important part of a patent. A patent claim is a precision-drafted, single-sentence definition of the patent owner’s right to exclude others.<ref name="ftn1"><sup>[1] Se''e'' Chapter 1 (“Foundations of the U.S. Patent System”), ''supra'', for further discussion of the nature of the exclusive right conveyed by a patent.</sup></ref> Every U.S. utility patent must conclude with one or more claims that particularly point out and distinctly claim the subject matter which the applicant regards as his invention.<ref name="ftn2"><sup>[2] 35 U.S.C. §112(b) (eff. Sept. 16, 2012).</sup></ref> ---- <references/> ----------------------- Please paste what your output looks like. Please also let us know which linux distro you are running and which UI (user interface) language you are running in.
Hi Jay, Thank you so much. Only no "<sup>**</sup>" in the outputted footnote text, i.e.: == Test == This chapter focuses on '''claims,''' arguably the most important part of a patent. A patent claim is a precision-drafted, single-sentence definition of the patent owner’s right to exclude others.<ref name="ftn1">[1] Se''e'' Chapter 1 (“Foundations of the U.S. Patent System”), ''supra'', for further discussion of the nature of the exclusive right conveyed by a patent.</ref> Every U.S. utility patent must conclude with one or more claims that particularly point out and distinctly claim the subject matter which the applicant regards as his invention.<ref name="ftn2">[2] 35 U.S.C. §112(b) (eff. Sept. 16, 2012).</ref> Steven
Hi Steven, Thanks for pointing that out. Yes superscript tags shouldnt be used in footnotes. Confirmed in 4.2.5 and master.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.1 or later): https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-07-18
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
I sent this patch to review for master: https://gerrit.libreoffice.org/#/c/38666/
Julien Nabet committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=6a24160894e91c007d4a2f8ef193eed670909ea5 tdf#80671: mediawiki, no superscript tags allowed in footnotes It will be available in 6.0.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Julien Nabet committed a patch related to this issue. It has been pushed to "libreoffice-5-4": http://cgit.freedesktop.org/libreoffice/core/commit/?id=c7cfdaa7a43dbee4a2257d99a34a167ba9dcd1db&h=libreoffice-5-4 tdf#80671: mediawiki, no superscript tags allowed in footnotes It will be available in 5.4.0.1. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Julien Nabet committed a patch related to this issue. It has been pushed to "libreoffice-5-3": http://cgit.freedesktop.org/libreoffice/core/commit/?id=1684ef2146dce6c132e3472b38b932d99f22b41c&h=libreoffice-5-3 tdf#80671: mediawiki, no superscript tags allowed in footnotes It will be available in 5.3.5. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.