I did the following: 1. Change of the global settings "standard document language" and "standard template". 2. Creating a new document by using the context menu of the windows explorer. Expected behaviour: New file is according to the global lo-settings as mentioned above. Current behaviour: The new file is a standard file created once in the installation process. Workaround: I replaced the files in the folder share\template\shellnew according to my presonal preferences. Comment: The solution of this might also resolve Bug 94857.
(In reply to Bernhard from comment #0) > I did the following: > 1. Change of the global settings "standard document language" and "standard > template". > 2. Creating a new document by using the context menu of the windows explorer. No problem here. Tools - Options - Language settings - Languages - Default languages for documents: changed from Finnish to Dibole. Win explorer produces Dibole documents. Version: 6.1.2.1 (x64) Build ID: 65905a128db06ba48db947242809d14d3f9a93fe CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: fi-FI (fi_FI); Calc: group threaded
(In reply to Buovjaga from comment #1) > (In reply to Bernhard from comment #0) > > I did the following: > > 1. Change of the global settings "standard document language" and "standard > > template". > > 2. Creating a new document by using the context menu of the windows explorer. > > No problem here. > > Tools - Options - Language settings - Languages - Default languages for > documents: changed from Finnish to Dibole. > > Win explorer produces Dibole documents. > > Version: 6.1.2.1 (x64) > Build ID: 65905a128db06ba48db947242809d14d3f9a93fe > CPU threads: 4; OS: Windows 10.0; UI render: default; > Locale: fi-FI (fi_FI); Calc: group threaded I just updated to 6.1.2.1 Documents in templates folder C:\Program Files\LibreOffice\share\template\shellnew were overwritten by installation program with english templates. Problem persists. In other words: Changing standard language does not change documents in templates folder. Win explorer takes the documents from that folder as template for new documents. Question: Could you please check, whether the changing of the standard language does result in a changed template in the templates folder?
I already tried. If there is something I misunderstood, you must provide clearer and *exact* steps to reproduce this. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information.
(In reply to Buovjaga from comment #3) > I already tried. If there is something I misunderstood, you must provide > clearer and *exact* steps to reproduce this. > > Set to NEEDINFO. > Change back to UNCONFIRMED after you have provided the information. (I can't speak English well but try to explain.) I think the steps to reproduce is exactly written in comment#0. As long as I know, this annoying behavior has not changed since LibreOffice ver.4.0x. Now, in LibreOffice ver.6.x, All Japanese users' setting of "standard language for documents" is "US-EN" for western languages and "Simplified Chinese" for Asian languages whenever they create any document from windows explorer's context menu(shellnew). Not only the language setting but all settings of LibreOffice is applied by "shellnew template files" when you create the file with using shellnew. And LibreOffice has no command for changing "shell new template files". So, you can find that last updated date of "shell new template files" has been not changed since the day LibreOffice installed. This is clearly the fatal lack of function. * I mean "shellnew template files" is the 4 files (soffice.odg, .odp, .ods, .odt) where are (installed folder)/LibreOffice/share/template/shellnew.
Hi, I have just reproduced this on my partner's new windows 10 computer (fresh windowsn installation). - Windows 10, latest version and updates - German (Germany) locale in the windows system Since you asked for a more precise reproduction flow @Buovjaga: * download libreoffice https://www.libreoffice.org/download/download/ * run installer, leave all standard settings * start libreoffice writer from start menu * type "Rice Reis" ("reis" is german for rice) -> "rice" underlined by spell checker, i.e. libreoffice finds the english spellling not OK but the german one OK. * close libreoffice * open windows explorer * navigate to documents folder * right click/tap in folder, choose "Neu -> OpenDocument Text" in context menu ("neu" is german for "new") * type a file name, press return * double click the file, opens in libreoffice * type "Rice Reis" -> "Reis" underlined by spell checker, i.e. libreoffice finds the german spelling not OK but the english one OK. Expected behavior in last step: "Rice" underlined in spell checker because all defaults should be properly set to the system locale on a fresh install. I chose the spell checker because it's an obviously visible use case. But the document created via the context menu in the explorer is overall not set to the standard locale. --- My guess / gut feeling about the issue: The problem is that creating a new file via the context menu in the windows explorer is happening without any software interaction with libreoffice. Windows solely relies on the registry information to decide what file to copy and create. "Computer\HKEY_CLASSES_ROOT\.odt\LibreOffice.WriterDocument.1\ShellNew\FileName" contains the path to the Libreoffice installation folder and the the libreoffice installer is not language-specific, libreoffice handles locale defaults at first start but does not change the file in the installation folder (which is hard because changing them requires administrator privileges). Maybe LO could put a file into the installation folder's "share\template\shellnew" that is somemarked as unlocalized so it can detect that when opening the file and set the configured locale when the file is first opened (which would again have the downside that the file is changed and the user would have to save even if nothing is changed). Not sure how other applications handle the case.
Hi, I have just reproduced this on my partner's new windows 10 computer (fresh windowsn installation). - Windows 10 64bit, latest version and updates - German (Germany) locale in the windows system Since you asked for a more precise reproduction flow @Buovjaga: * download libreoffice https://www.libreoffice.org/download/download/ (latest, tested with 6.3.4) * run installer, leave all standard settings * start libreoffice writer from start menu * type "Rice Reis" ("reis" is german for rice) -> "rice" underlined by spell checker, i.e. libreoffice finds the english spellling not OK but the german one OK. * close libreoffice * open windows explorer * navigate to documents folder * right click/tap in folder, choose "Neu -> OpenDocument Text" in context menu ("neu" is german for "new") * type a file name, press return * double click the file, opens in libreoffice * type "Rice Reis" -> "Reis" underlined by spell checker, i.e. libreoffice finds the german spelling not OK but the english one OK. Expected behavior in last step: "Rice" underlined in spell checker because all defaults should be properly set to the system locale on a fresh install. I chose the spell checker because it's an obviously visible use case. But the document created via the context menu in the explorer is overall not set to the standard locale. --- My guess / gut feeling about the issue: The problem is that creating a new file via the context menu in the windows explorer is happening without any software interaction with libreoffice. Windows solely relies on the registry information to decide what file to copy and create. "Computer\HKEY_CLASSES_ROOT\.odt\LibreOffice.WriterDocument.1\ShellNew\FileName" contains the path to the Libreoffice installation folder and the the libreoffice installer is not language-specific, libreoffice handles locale defaults at first start but does not change the file in the installation folder (which is hard because changing them requires administrator privileges). Maybe LO could put a file into the installation folder's "share\template\shellnew" that is somemarked as unlocalized so it can detect that when opening the file and set the configured locale when the file is first opened (which would again have the downside that the file is changed and the user would have to save even if nothing is changed). Not sure how other applications handle the case. This issue could be tagged with a 6.x version istead of 4.x to increase visibility.
(In reply to Nikolaus Kühn from comment #6) > This issue could be tagged with a 6.x version istead of 4.x to increase > visibility. Please ignore that statement, I forgot that the version tag refers to the earliest affected
(In reply to Nikolaus Kühn from comment #6) > Not sure how other applications handle the case. From other applications I know the following solution: Right-click function in the explorer just creates an empty (0 Bytes) file. The applications generates the propper file as soon as you open it. regards Bernhard
(In reply to Bernhard from comment #8) > > Not sure how other applications handle the case. > > From other applications I know the following solution: I just tested MS Office 2010, it does an interesting mix. * A new Word File is an empty file * a new Powerpoint file is an actual presentation XSLX including my user as the creator and the actual creation date in the metadata inside the generated zipped archive XSLX * a new Excel file is an actual spreadsheet with my user as the creator but some 2006 date as the creation date in the created metadata. Not very insightful but the powerpoint file shows that there seems to be a way to dynamically do something inside a file when it's created. In the registry, Word doesn't have a "FileName" Value, it has an empty "NullFile" value only which seems to trigger windows to create an empty file. PPTX has a "FileName" value which just contains "pwrpnt12.pptx" (not a full path, not sure what that means).
Dear Bernhard, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Tested with Version: 7.3.5.2 (x64) / LibreOffice Community Build ID: 184fe81b8c8c30d8b5082578aee2fed2ea847c01 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL Actual result: New document has default document language New document doesn't have a template Expected result New document has default document language New document should use the default template => First problem mentioned in original report is fixed, seco nd probelm still remains => This is bug 139962 *** This bug has been marked as a duplicate of bug 139962 ***