Problem description: If you are editing some files which were created in MS Word(it doesn't matter if you re-save them in .odt or not), which have superscript position in footnote character styles, text remains in superscript if inserted right after footnote characters. Steps to reproduce: 1. Open an attached MS Word file 2. Type text right after footnote, see that it remains superscript Current behavior: Text style remains superscript if text is inserted right after footnote. Expected behavior: Text style must change to default. Same issue was reported here by someone else: http://www.oooforum.org/forum/viewtopic.phtml?t=127834 Platform (if different from the browser): Browser: Mozilla/5.0 (Ubuntu; X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0
Created attachment 54375 [details] Doc file to test the bug
Here is a bug screencast: http://vpk.cloudkill.org/site_media/openoffice_bug.ogv BTW, having a maximum of 3mb for attachments in bugzilla is very bad for bug reporting.
Little bit of history behind my bug report: Few of my fellows have recently moved from Windows to Linux Mint(11.04). All of them say that LibreOffice Writer is a decent editor and they didn't have trouble adapting to it, but they are complaining about ONE SINGLE ANNOYANCE which is described in this bug report. They have hundreds of footnotes in their scientific papers and to change font style after every footnote seems insane. I have already installed MS Word via Wine for one of them. The issue is serious, it is pushing users away from your otherwise good product. Please, fix it ASAP.
1) lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.4.4-0ubuntu1 Candidate: 1:3.4.4-0ubuntu1 Version table: *** 1:3.4.4-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.4.3-3ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 3) What is expected to happen in LibreOffice Writer importing a Word created file via the Terminal: cd ~/Desktop && wget -c https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/903608/+attachment/2630995/+files/footnoteformattingbug_1.doc -O example.doc && lowriter -nologo example.doc on page 1 if one clicks immediately after superscript footnote 1 and begins to type, the characters are not superscript, as it would occur in Word. 4) What happens instead is the characters are superscript as shown in https://launchpadlibrarian.net/87353347/libreofficeformattingbug.ogv WORKAROUND: Click immediately after the footnote and press Ctrl+Shift+P then begin typing as desired. This is documented at: http://help.libreoffice.org/Writer/Making_Text_Superscript_or_Subscript Severity Normal > Minor quoting from http://wiki.documentfoundation.org/BugReport_Details#Severity "minor loss of function, or other problem where easy workaround is present" Importance High > Low This really should not be high on the developer to do list as the WORKAROUND is trivial to perform and well documented. Platform All All > x86 (IA32) Linux (All) Only documented test cases up or downstream are Linux, IA32.
Christopher, thanks for the info about workaround. However, the bug is all platform and is not architecture dependent. As I have written, the bug exists in Ubuntu 10.10 (x86_64) (default packages), Ubuntu 11.04 (x86_64) (default packages), Ubuntu 11.04 (x86_64) (packages from LibreOffice stable PPA). Just now I have tested the bug in LibreOffice 3.4.4 in virtualised Windows XP i386, and (unsurprisingly) the bug exists here too. So I am changing it back to all architectures and all platforms. Best regards, Ivan
Created attachment 54437 [details] modified version of file to demonstrate a possible fix modification of the paragraph style 'footnote characters' to remove the indent and modification of the applied character style 'footnote characters' to change font position from superscript to normal removes the problem. Settings based on the default footnote style on a new LO 3.4.4 document. file attached to demonstrate
Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
Still reproducible. The doc file can be created in LO, saved, closed, reopened, and the effect is the same. Windows Vista 64 Version: 4.4.3.2 Build ID: 88805f81e9fe61362df02b9941de8e38a9b5fd16
** 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
Dear Ivan Kharlamov, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Following the footnote is a tab, and after the tab any entered text (to modify the existing footnote) is normal. I can't imagine why text would need to be added before the tab. Anyway, it makes sense for text it inherit the format of the text preceding the cursor. So I don't see the problem here (and the video link is dead.) Lots of improvements have been made to footnote compatibility. I'm closing as works for me, since there haven't been any complaints for years.