Description: This is too obvious, too fundemental and too simply fixed, to believe that it could ever be fixed. But here goes: I would love it if there were the option of no auto-formatting, e.g. I was making a list of Ukrainian lexical items not obviously corresponding to (mainly) Russian or English. I had, in an earlier session, four-spaced by default, giving me the chance to lesser-space phrasal lexical items and semantically close clusters. I reopened it and was scanning through: "...дія, дмухнутий, до...," then thought, "до?" I didn't write "до", and realised, ah, "до побачення". What had happened was, I didn't notice that the word-spacing had, upon reopening, auto-corrected to single. I tried looking for a command to turn off the auto-spacing, corrected that one item, saved, closed and reopened; and it was back to the all-knowing, all-powerful auto-correct. Some people might find auto-format useful. I don't think I can recall a single instance when I have. Word, especially: Word decided that most people like to leave a space btw paragraphs, so tied the enter key to double-space. You can't permanently turn that off. My work-around was to create one generic file each for Word and Wordpad, wherein I set up single spacing and "entered" several pages worth of blank text. So in using those blanks, I just used the down-arrow instead of "enter." Same with those god-awful charms on Windows 8. Long gone to God (poor God) and not lamented. Microsoft lost a lot of users over that, but they just could have offered the option of turning off the charms. That's basically the universal malady of software writing - the failure to apply to every single feature the same option: toggle, on/off. I believe that Wordperfect used to follow that principle - and I've tried to get it back a couple of times. But bad money drives out good; VHS drives out Beta; Word drives out Wordperfect; Google drives out all other Sir Chenjens, and every new one copies effing, useless Google. I've gone on a bit here, but really, this is a fundamental principle - I'm sure a huge, 35 kg gold nugget, just lying on the groud waiting for any developer to pick it up and revolutionise proramming. "Toggle, on/off" would bring programmers and end users onto the same planet. Steps to Reproduce: 1.Write a brief document, e.g. five or ten words, using varied word-spacing. 2."Save as" and close the document. 3.Reopen: the variable spacing will have been reduced to uniformity. Actual Results: As stated above. Expected Results: Not interfered with what I wrote. Reproducible: Always User Profile Reset: No Additional Info: No other information. I have selected the first version, but I have no idea which. Doesn't matter, this is not a tiny, technical "bug" relating to this or that version. it is a fudamental failure in programming. There will certainly be the same problem on all listed versions.
(In reply to loathgoogel from comment #0) > Steps to Reproduce: > 1.Write a brief document, e.g. five or ten words, using varied word-spacing. > 2."Save as" and close the document. > 3.Reopen: the variable spacing will have been reduced to uniformity. Are you using an HTML? Because in that format, it could be some poor filter issue (not requiring to keep spaces, and defaulting to HTML's usual "collapse spaces" behavior); but for other formats, the multiple spaces *must* be kept. And everything else in your report is unrelated, because when you describe is not a "auto-formatting", but a bug.
Please attach a sample. When you make it with visibly large word spacing, make a screenshot and put it in the same document.
Dear loathgoogel, 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 loathgoogel, 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