Using The character format at the end of a line is the character format of the next character regarded as the first character of the next line. Typing at the end uses the wrong format, that from the first character of the next line. To reproduce make a document with two lines of text and apply a direct character format effect (not using character template). Use any of italics, bold, and/or underline on the first one (or more) characters of the second line. Use either the menu format->text->whatever or the buttons on the formatting toolbar. Leave the first line of text entirely plain, no applied character format. Save as temp.doc and reload (or else close and open). Move cursor to end of the first line and see the 'projected' character format. Type at the end of the first line to see the wrong character format applied to added text. Save a similar two-line document as temp.ODT and otherwise repeat to see that the problem does NOT exist with the .odt file extension (which I would normally use but MS .doc is the format for uploading an Amazon ebook manuscript). I am using Funtoo Linux on a Sony Vaio laptop. I don't know what OSs and hardware platforms are effected. I tentatively put 'All'. Thx.
I have just compiled and tested Writer for LibreOffice 5.0.5.2 and get the same bug. I have also discovered a potential workaround, though I worry about file corruption. WORKAROUND-ISH: If I type a non-space character at the end of the offending line and then undo with ctrl-z, the bad character format setting is corrected.
Reproduced. Arch Linux 64-bit, KDE Plasma 5 Version: 5.2.0.0.alpha0+ Build ID: 235411c9d47ecba88e46d859ea93bcecefb0c46e CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; Locale: fi-FI (fi_FI.UTF-8) Built on March 11th 2016
Created attachment 123544 [details] DOC for testing
** 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.7 or 5.3.3 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-20170522
Dear Doug, 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
As instructed, I tested for the bug on the current LibreOffice I have on my Linux. The bug is gone. LibreOffice is now working as expected. The LibreOffice version I tested for this comment is: Version: 6.1.5.2 Build ID: 1:6.1.5-3+deb10u4 CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk2; Locale: en-US (en_US.UTF-8); Calc: group threaded Thanks for great software!