Description: I believe I've done my due diligence (fingers crossed) I'll add screenshots. All my win10 language and keyboard options are default UK english. All the default options in tools->languages in the libre launcher are default UK english. As the summary states, when right-click creating a new writer file, default language is ignored and changes to US english. If you create a new writer file through the libre launcher instead everything is fine and the default language is correct. Steps to Reproduce: 1.Right click in a folder 2.click create new writer document 3.open new writer document 4.look at default language in the bottom bar of the document Actual Results: wrong text language/spellchecker is used Expected Results: same default language as if creating a new document from the launcher Reproducible: Always User Profile Reset: Yes Additional Info: N/A
Created attachment 165522 [details] win10 lang settings
Created attachment 165523 [details] libreoffice launcher language settings
Created attachment 165524 [details] right-click created file ignoring default UK language settings
Can confirm, still occurs for me in 7.0.3
Hello Warior, Thank you for reporting the bug. I can confirm that the bug is present in last release. Version: 7.0.3.1 (x64) Build ID: d7547858d014d4cf69878db179d326fc3483e082 CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win Locale: cs-CZ (cs_CZ); UI: en-US Calc: CL No idea how to check it in master.
I confirm it with Version: 7.0.3.1 (x64) Build ID: d7547858d014d4cf69878db179d326fc3483e082 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL See Tools => Options => Language settings => Languages: Default language for documents changes from German (in my case) to English (USA). Thisonly happens if I create a new document from desktop or explorer.
*** Bug 140790 has been marked as a duplicate of this bug. ***
*** Bug 140867 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 133661 ***