Description: Mixed case Alpha where the first two characters are upper case are changed to Sentence? case Steps to Reproduce: Try to change any of the cells in the attached sheet to make the first two characters upper case. Try to type a word into a free cell where the first two characters are intentionally upper case Actual Results: Reverting to Sentence case? Expected Results: What I type is what I want to see Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: Version: 7.0.4.2 (x64) Build ID: dcf040e67528d9187c66b2379df5ea4407429775 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: sv-SE (en_GB); UI: en-GB Calc: threaded
Created attachment 168937 [details] Simple example spreadsheet
That is an option. Menu/Tools/Autocorrect/Options - Correct TWo INitial CApitals
(In reply to m.a.riosv from comment #2) > That is an option. > Menu/Tools/Autocorrect/Options - Correct TWo INitial CApitals Does that make it an update/implementation error because it only became apparent after a recent update. Is software released with some parameters modified as a result of the developer having to set various options to verify their code - but then not returning them to the "normal" default?
(In reply to Colin from comment #3) > (In reply to m.a.riosv from comment #2) > > That is an option. > > Menu/Tools/Autocorrect/Options - Correct TWo INitial CApitals > > Does that make it an update/implementation error because it only became > apparent after a recent update. This option has existed in LibreOffice since forever and has always been on by default, at least for English locale and UI. If you are sure that it was turned off before your update and wasn't due to your personal configuration, please provide more detailed version information for your old system before update.
(In reply to Colin from comment #1) > Created attachment 168937 [details] > Simple example spreadsheet FWIW, I just tested 5.2.7 on Windows: Version: 5.2.7.2 (x64) Build ID: 2b7f1e640c46ceb28adf43ee075a6e8b8439ed10 CPU Threads: 2; OS Version: Windows 6.19; UI Render: default; Locale: zh-CN (zh_CN); Calc: group And the option is on by default. Using your sample document I can reproduce both cases (changing an existing string or type a new string) unless I turn it off.
(In reply to Ming Hua from comment #4) > (In reply to Colin from comment #3) > > (In reply to m.a.riosv from comment #2) > > > That is an option. > > > Menu/Tools/Autocorrect/Options - Correct TWo INitial CApitals > > > > Does that make it an update/implementation error because it only became > > apparent after a recent update. > This option has existed in LibreOffice since forever and has always been on > by default, at least for English locale and UI. > > If you are sure that it was turned off before your update and wasn't due to > your personal configuration, please provide more detailed version > information for your old system before update. I have Swedish Locale and English UI. It may be that I turned it off last century and forgot it even existed. I couldn't find anything remotely resembling it in the FORMAT menus, hence my suspicion it was a bug. Confirm it works for me @NOW(). I suspect somehow the latest upgrade reset some defaults. My apologies for wasting time although I imagine you must be inundated with reports when a new release changes some of the default settings at the user end.
(In reply to Colin from comment #6) > I suspect somehow the latest upgrade reset some defaults. To the best of my knowledge it shouldn't. If you didn't explicitly delete/reset your user profile (https://wiki.documentfoundation.org/UserProfile), LibreOffice should keep your old configurations after an upgrade. It's definitely a bug if it reset this option for you by itself. But again, it is tricky to reproduce unless you can provide exact steps. And most users don't bother when they experience this -- it's much easier to just set the configurations again than trying to reproduce with re-installations. > My apologies for wasting time although I imagine you must be inundated with > reports when a new release changes some of the default settings at the user > end. No apologies needed, we appreciate the bug reports. It's generally better to err on the side of reporting too many than reporting too few, I think.
(In reply to Ming Hua from comment #7) > (In reply to Colin from comment #6) > > I suspect somehow the latest upgrade reset some defaults. > To the best of my knowledge it shouldn't. If you didn't explicitly > delete/reset your user profile Spot on, just remembered - I messed up/reset my profile in an endeavour to verify a previously reported issue on a later release. Discovered there's no way to reject the profile reset once the wrong choices have been taken. All gone. I thought it would ask me if I wanted to save the existing profile before resetting it - No such luck :((.