Created attachment 103155 [details] The document I was working on when experiencing spurious font changes Font changes randomly at times when I insert unformatted text (Ctrl-Shift-V, or using menu bar), or even when I just click somewhere and start typing. This occurs even after I selected the entire document and set the font to a particular value (Arial 11, in this case). Also, the entire document is set to "Default Style". I've attached the document I've been working on that has been exhibiting the problem. I think it was created originally using MS Word (probably a fairly old version of Word). You can see in the 4th paragraph down where it suddenly switched to Symbol font. Later on, I set the address info up top to size 8, but when I clicked at the end of the line to start adding something, it started typing out in size 11 again. Later still, I put in a carriage return (newline) and it changed the font to System. Naturally, I can't use Writer if I have to fix the font every time I add some text in a new place. Platform is Windows 7. The version of Writer is 4.2.4.2, Build ID: 63150712c6d317d27ce2db16eb94c2f3d7b699f8 Thank you for your attention. Sincerely, Jeff
Is that the original document or was it saved by LO?
Hi, it was saved by LO Writer. I'm wondering: could be something encoded into the original MS Word file that is somehow confusing Writer?
Dear Herouth, Thank you for submitting the bug. Regarding the address being set to 8pt, all the text in the address is 11pt. Regarding the font switching to symbol, i think this might be due to your keyboard switching languages. If you'd like to set the documents font to Arial, i'd recommend you pressing F11 and then right clicking on 'Default Style' and clicking modify, and then under the Font tab, select Arial 11pt.
Mea culpa; I should probably clear up some confusion re. the sample document that I attached: After experiencing the pasted-text-turns-into-Symbol-font problem several times, and changing the font back to Arial, I decided to leave one instance of it unchanged, and then I saved off the document to use it as an attachment to the bug post. It was later that I experienced the other problems, but I neglected to save off successive versions of the document that displayed those. However, the problem with Writer "forgetting" the new font size after I change the address section to 8 pt is eminently reproducible. The random appearance of the System font has not recurred, though. Thanks for the F11 suggestion. I did try that, and oddly, the default font was pre-set to Times New Roman 12, which is a font that hasn't randomly appeared yet in the document. > Regarding the font switching to symbol, i think this might be due to your > keyboard switching languages. I'm afraid my keyboard isn't set up for multiple languages, at least not through Windows. Maybe Writer has some option to switch languages that is getting tripped accidentally, somehow?
Hi Jeff, Unfortunately without the original document that we can test against about the issue of the pasted-text-turns-into-Symbol-font problem, we couldnt look further into this issue. (In reply to comment #4) > However, the problem with Writer "forgetting" the new font size after I > change the address section to 8 pt is eminently reproducible. I wasnt able to reproduce this issue when i opened the attached file, changed the font to 8pt, saved it, and then reopened it. Is there something that i'm doing wrong about this issue?
(In reply to comment #5) > Hi Jeff, > > Unfortunately without the original document that we can test against about > the issue of the pasted-text-turns-into-Symbol-font problem, we couldnt look > further into this issue. > > (In reply to comment #4) > > However, the problem with Writer "forgetting" the new font size after I > > change the address section to 8 pt is eminently reproducible. > > I wasnt able to reproduce this issue when i opened the attached file, > changed the font to 8pt, saved it, and then reopened it. Is there something > that i'm doing wrong about this issue? Hi Jay -- Thank you for checking this out. I might not have articulated the "forgetting" problem very well... Here's what I meant to say: After setting a group of lines to the new font size (Arial 9), click on the end of one of these lines to place the cursor at the very end of the line. Now start typing anything. The newly typed characters come up in the old size (Arial 11) instead of the new size you just set (Arial 9).
Hi Jeff, Thanks for the explanation. I can confirm this issue in LibO 3.3.0, 4.2.5 and 4.3.1. Steps: 1) Open attachment 103155 [details] 2) Select the 5 address lines 3) Change font size to 9pt 4) Click at the end of any of the lines 5) Font size is set to 11pt It is strange because if i save the unedited file as an odt and then reopen it and do the changes, it works fine.
Steps: 1) Open attachment 103155 [details] 2) Select the 5 address lines 3) Change font size to 9pt 4) Click at the end of any of the lines 5) Font size is set to 11pt Wherever I click, font size does not change after setting it to 9pt for the address at the top of the document. OS X 10.10.3 Version: 5.0.0.0.alpha1+ Build ID: d2ab54bb0d07d285c91a8ac17f53559e438d042a TinderBox: MacOSX-10.10@61, Branch:master, Time: 2015-05-03_01:14:24 Locale: de-DE (de.UTF-8) Since there is no specific commit fixing this issue, setting to WORKSFORME. FIXED is used only when a commit exists. Feel free to reopen this issue if you still can reproduce this particular problem or if I did miss something peculiar.
Still present for me. Version: 5.0.0.0.alpha1+ Build ID: 59adad74084e9281887e3f78a225794f37b784d7 TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:master, Time: 2015-04-29_12:34:23
Migrating Whiteboard tags to Keywords: (filter:doc)
** 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 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
repro 7.0+
Dear Jeff, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Fixed in LO 7.6 with commit 92fe70072d16922af41ab0fd3746172f3a58e489 Author: Justin Luth on Tue May 2 20:05:41 2023 -0400 tdf#148956 sw: clear nAttrStart == paraEnd hints in DOCX *** This bug has been marked as a duplicate of bug 148956 ***