Created attachment 106088 [details] It's an LO Writer file in which I used AutoText and encountered this problem. Problem description: When you use the AutoText feature, it changes your font to Times New Roman. Steps to reproduce: 1. .... Start a new document using a font other than the default Times New Roman (or whatever you have set as the default). I usually use Courier New or Ubuntu. 2. .... Type in some text you want to repeat often, such as the name of a character in a play. In this example, let's use "Kelsey: " 3. .... Highlight Kelsey with the mouse. 4. .... Choose Edit ==> AutoText 5. .... The AutoText menu comes up. In the name field, type "Kelsey". The shortcut field suggests "K". That's what we want. 6. .... From the AutoText button (on the far right) click on the down arrow and choose New (text only). 7. .... Click on the Close button. 8. .... Delete anything that's in the document or open a new one. 9. .... Type K and then F3. AutoText puts in the name Kelsey. It may or may not have already changed it to Times New Roman. If not, type some text, which will be in Courier New or whatever font you originally chose. Hit enter down to the next line and type another character's name, for example: "Bill." 10. .... Go through the same process to make an AutoText entry for Bill. Try to type up a conversation between Kelsey and Bill in whatever font you chose. At some point, the AutoText feature will change your font to Times New Roman without your having chosen that font. Current behavior: AutoText changes the font to Times New Roman without your having chosen that. Expected behavior: AutoText should put in the text and leave it in the font that the user originally chose when creating the document. I've encountered this problem while writing documents in English (USA) and in French (France). Operating System: Ubuntu Version: 4.2.6.2 release
Did you try to create your autotext by chosing New (text) instead of New (text only) at step 6 ? Set status to NEEDINFO. Please set it back to UNCONFIRMED once you have provided requested informations. Thank you for your understanding. Best regards. JBF
Jean-Baptiste Faure: Yes, thank you for responding. I still have the same problem when I do it that way. The difference is doing it that way does not push me down to the next line (undesired). In previous versions, choosing "New" (without "text only) produced the problem of changing the font, but did not force the cursor down to the next line. Choosing "New (Text Only)" forced the cursor down to the next line, but, fortunately, did not change the font. I therefore used the latter, circumventing the forced-to-next line problem by programming Ctrl+H to the same thing as the backspace key. Therefore, previously, I was able to (if I did it as in the example) type the letter K and then hit F3, making my character name typed, but I would be on the next line, requiring a quick Ctrl+H to get back up where I really wanted to be. I guess you could call that being forced down undesired to the next line another bug. Should I file a report for that or is this one sufficient? So, to recap: 1. Choosing "New" changes the font against the user's will, does not force cursor down to next line. 2. Choosing "New (Text Only)" changes the font against user's will, forces cursor down to next line. I very much appreciate you for looking at this problem, and all the programmers who create and maintain LibreOffice. Thank you.
(In reply to Tom Meinen from comment #2) > So, to recap: > 1. Choosing "New" changes the font against the user's will, does not force > cursor down to next line. > 2. Choosing "New (Text Only)" changes the font against user's will, forces > cursor down to next line. Confirmed in Windows and Linux. Setting to NEW and lowering severity per https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg Also, when I had played around with the autotext in Ubuntu for a while, adding and deleting entries, I got to a point that I can't click on any autotext entry in the dialog without a crash and this output: warn:legacy.osl:4529:1:sw/source/core/doc/DocumentListsManager.cxx:96: <DocumentListsManager::createListForListStyle(..)> - a list for the provided list style name already exists. Serious defect -> please inform OD. warn:legacy.osl:4529:1:sw/source/core/doc/DocumentListsManager.cxx:96: <DocumentListsManager::createListForListStyle(..)> - a list for the provided list style name already exists. Serious defect -> please inform OD. warn:legacy.osl:4529:1:sw/source/core/unocore/unosett.cxx:2248: <SwXNumberingRules::getPropertyValue(..)> - no default list id found. Serious defect -> please inform OD. soffice.bin: /home/buildslave/source/libo-core/xmloff/source/text/txtimp.cxx:921: XMLTextImportHelper::XMLTextImportHelper(const com::sun::star::uno::Reference<com::sun::star::frame::XModel>&, SvXMLImport&, bool, bool, bool, bool, bool): Assertion `!sListId.isEmpty() && "no default list id found at chapter numbering rules instance. Serious defect -> please inform OD."' failed. Tested on: Win 7 64-bit Version: 4.5.0.0.alpha0+ Build ID: b144f0ac8695dd62a2053b4e88212d0b109c9a41 TinderBox: Win-x86@51-TDF, Branch:MASTER, Time: 2014-11-25_00:14:54 Ubuntu 14.10 64-bit Version: 4.5.0.0.alpha0+ Build ID: 6b219f012edbe069c461f4e0746898e33fa1dd49 TinderBox: Linux-rpm_deb-x86_64@46-TDF-dbg, Branch:master, Time: 2014-11-25_21:56:46
** 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.4 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 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-12-20
Present on: Version: 5.0.6.3 Build ID: 490fc03b25318460cfc54456516ea2519c11d1aa Locale: it-IT (it_IT.UTF-8) Version: 5.1.3.2 Build ID: 644e4637d1d8544fd9f56425bd6cec110e49301b CPU Threads: 2; OS Version: Linux 4.1; UI Render: default; Locale: it-IT (it_IT.UTF-8) Version: 5.2.0.0.beta2 Build ID: ae12e6f168ba39f137fc110174a37c482ce68fa4 CPU Threads: 2; OS Version: Linux 4.1; UI Render: default; Locale: it-IT (it_IT.UTF-8) Version: 5.3.0.0.alpha0+ Build ID: a8bd44573b75d1399257d6f5d052611439607189 CPU Threads: 2; OS Version: Linux 4.1; UI Render: default; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2016-06-13_23:46:49 Locale: it-IT (it_IT.UTF-8) OS: openSUSE Leap 42.1 (x86_64)
** 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
What I can reproduce with Version: 6.3.0.4 Build ID: 057fc023c990d676a43019934386b85b21a9ee99 Threads CPU : 8; OS : Linux 4.15; UI Render : par défaut; VCL: gtk3; Locale : fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR Calc: threaded style of paragraph is restored just after insertion of autotext. ==> Workaround: modify the style of paragraph to reflect the format you expect. Steps to reproduce from scratch: 1. New Writer document 2. Change directly font, size or whatever in format (but do not modify style) 3. Type a word 4. Select the word 5. Ctrl+F3, enter a name (for instance same as word) 6. Autotext > "New" or "New (text only)". Close 7. Type some other stuff, then shortcut of autotext+F3 Actual behavior: Format is now set to paragraph style Expected behavior: Direct Formatting should be kept Workarounds, choose one: - simplest: modify paragraph style to reflect your needs Shift+Ctrl+F11. Done once for a document. Modify your default template to be done for life :-) - move up/down cursor (does not work for Autotext text only) - type a character and erase it or erase extra carriage return inserted with Autotext text only (see bug 53023)
I don't see a bug here or I don't understand it. New and New (Text Only) work as expected, formatted text or text only. Comment 2 recap "not/force cursor down" is still repro but "changes the font against the user's will" and title "AutoText changes font" is not clear. What is expected there? Comment 7 is different and Actual behavior is OK, Expected behavior is NOK. This needs a clarification so I set Needinfo.
Dear Tom Meinen, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Tom Meinen, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp