I think this is a recent regression. At least, LO 3.5.7.2 was ok. Steps to reproduce: 1) Select a single character in a Word 2) Format/Character/Position/Subscript or Superscript 3) See the character disapears (in fact, replaced by a very small space). Workaround: with CTRL-SHIFT-B, I get the normal behaviour (subscript). No such problem in Calc.
I do not reproduce issue under Win7x64 using LibO 4.2.3.3 please define exactly your O/S and provide a test file.
Created attachment 98427 [details] simple odt file containing a single word (before any formating)
Created attachment 98428 [details] the same document with letter "o" subscripted The letter "o" is not visible, but you can select the small space (between "w" and "r") and return the the "normal" character position to see that a "o" is really there.
I'm on Linux Mint 13 Cinnamon 64 bit. See the attachments.
Created attachment 98429 [details] normal findings under Win7x64 your test file are abnormal indeed... but I cannot reproduce the issue from scratch under Win7x64 see attached file probably that's a Linux specific issue that has to be confirmed by another Linux user. In the meantime try resetting the user profile and see if it change things. https://wiki.documentfoundation.org/UserProfile
The attachment created under Win7 is displayed correctly on Linux (superscript O).
I deleted my profile (~/.config/libreoffice) and now it works normally! Thank you for this hint. I still have a copy of my defective profile but I don't know which file I should upload (to help someone to confirm). I don't mark the bug as resolved, since it can happen with a given profile. At least, deleting the profile is a workaround.
try copying a single folder one-by-one of the corrupted profile into the working one and retest soon after. this would allow you to idenfity where the corrupted file is. then once you identify the "bad folder" do the same thing with any singular file of it. once you find who's guilty upload it here but I cannot assure we can find a solution. sometimes user profile corruption are unpredictable and unfixable I set status to NEEDINFO, revert it to UNCONFIRMED once you identify the corrupted file
Created attachment 98472 [details] the bad file (in the profile) put this in ~/.config/libreoffice/4/user
good catch bruno!!! I can reproduce your same bug using that corrupted registrymodifications.xcu file in my user profile under Win7x64 I add Writer expert to CC-list to hear if this may be useful to disclose the root of the bug and maybe prevent further episodes. @Michael, would you please take a look at it?
** 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.0.5 or 5.1.0) 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: 2016-02-21
** 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.2.5 or 5.3.0 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-20170306
Closing this bug as INVALID because the only chance to ever fix it is to find the reason why xcu corrupted. Only having the file won't help.