In 24.8.6.2, I add an entry into Autocorrect via Context menu -> "Always Autocorrect to" and it works while the application is running. But it seems the new entry isn't saved because when I relaunch the app it no longer remembers it. This is on a fresh install and clean profile. It occurs irrespective of language (tried two). I even entered an entry via the autocorrect options dialog, still the same. Not seeing an acor_xx-XX.dat file created/updated either. The AutoCorrect -> "While Typing" option is enabled. Version: 24.8.6.2 (X86_64) / LibreOffice Community Build ID: 6d98ba145e9a8a39fc57bcc76981d1fb1316c60c CPU threads: 12; OS: Windows 10 X86_64 (10.0 build 19045); UI render: Skia/Raster; VCL: win Locale: en-AU (en_AU); UI: en-GB Calc: CL threaded To reproduce, - open new doc in writer - mispell a word - auto correct via context menu - close LO completely - open and repeat spelling error - no automatic correction occurs.
Previous version I've been using, Version: 7.6.7.2 (X86_64) / LibreOffice Community Build ID: dd47e4b30cb7dab30588d6c79c651f218165e3c5 CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-AU (en_AU); UI: en-GB Calc: CL threaded behaves as expected.
no repro on linux. (In reply to Jordi from comment #0) > ... Not seeing an acor_xx-XX.dat file created/updated either. what if you copy your acor_ file from your previous version ?
(In reply to fpy from comment #2) > no repro on linux. > > > (In reply to Jordi from comment #0) > > ... Not seeing an acor_xx-XX.dat file created/updated either. > > what if you copy your acor_ file from your previous version ? That is what I sort of do normally do when I test new versions. I link my normal acor_ files from cloud drive (shared among machines) but wasn't seeing the file updated. Created new profile without linking anything and saw the same, no file created. Just check btw and even the installdir\user\autocorr folder hasn't been created. PS: its a parallel install using "Separate Install GUI".
Given fpy's comment I tried the MSI from SiGui and installed it properly on a W10 VM, no issues there. Cleared my previous SiGUI parallel install on my physical machine and reinstalled it, no issues now! No idea what happened.