| Summary: | Saving a subscript character | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | andy.dabsmith |
| Component: | LibreOffice | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | minor | CC: | barta, ilmari.lauhakangas, stgohi-lobugs |
| Priority: | medium | Keywords: | filter:doc |
| Version: | 3.6.6.2 release | ||
| Hardware: | Other | ||
| OS: | Windows (All) | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 112681 | ||
| Attachments: | example text in .doc file | ||
please attach the original .odt file so we can reproduce the bug saving it as .doc and see exactly what change. by the way, do you still see this bug with recent 4.x releases Sorry that you had to wait such a long time for a reply. Buggy behavior was reproducible with LO 4.1.4.2 (Win8). The subscripts are changed but not back to 100% as reported. Steps done: 1. Open the attached file 2. Select the subscript "2" 3. Go to FORMAT -> CHARACTER and to the tab POSITION 4. Check that the RELATIVE FONT SIZE is 100% and RAISE/LOWER BY shows 95% 5. Now change RAISE/LOWER BY to 50% 6. Save this file as doc file and close WRITER 7. Open the changed doc file 8. Go to FORMAT -> CHARACTER and to the tab POSITION 9. Check that the RELATIVE FONT SIZE is 100% and RAISE/LOWER BY shows now 45% instead of 50% The same happens with docx files. If you change it to any other percentage above 10% it always changes to 5% less. Below 10% the subscript gets lost and it is changes to POSITION = NORMAL, RAISE/LOWER BY = 1% and AUTOMATIC is activated. Could you please retry it with the latest release of LO, whether you can see the same behavior. ** 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-04-18 (In reply to A (Andy) from comment #2) > 9. Check that the RELATIVE FONT SIZE is 100% and RAISE/LOWER BY shows now > 45% instead of 50% Repro from scratch. Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+ Build ID: 01a189abcd9a4ca472a74b3b2c000c9338fc2c91 TinderBox: Win-x86@39, Branch:master, Time: 2015-06-14_07:46:28 Locale: fi-FI (fi_FI) ** 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 LO and MSWord implement superscript very differently. With only 5% difference being reported, that seems close enough in emulation to me. Marking this as wontfix. Granted, there definitely are problems in the algorithm I'm sure - but other bug reports deal with that. This example file doesn't demonstrate a sufficient bug. |
Created attachment 79613 [details] example text in .doc file Format a subscript character at 50% works fine, then saving as MS Word .doc file also gives no perceived problem. However, when re-opening the previously closed file, the subscript size has changed to 100%, and the line spacing is thrown out. Used to work OK on previous versions. My University only accepts MS Word format.