Created attachment 64355 [details] example template showing the bug. Problem description: Due to this bug, it is possible to create a template which looks completely different depending on which user interface language is set. This is highly problematic as you have no guarantee that a template will look the same on all office installations. Steps to reproduce: 1. Change interface language to German and restart office. 2. Create a new document, add some text. 3. Add a new user defined style called "Default". Change its font to "Verdana". Note that this don't change anything in your document as in german the default style is called "Standard". 4. Save the document as .ott. 5. Change interface language to English and restart office. 6. Open the .ott file. Your document default style now has "Verdana" set as font. Current behavior: Predefined styles are named differently depending on user interface language. Opening a template with a different user interface language set than it was created opens the possibility that there are name conflicts between user defined styles and predefined styles. This leads to different styles being used depending on which language is set. Expected behavior: It should not be possible to define user defined styles which conflict with predefined style names. Platform (if different from the browser): Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20100101 Firefox/13.0.1
Same problem reported to OpenOffice.org here: https://issues.apache.org/ooo/show_bug.cgi?id=120311
I could not reproduce it with LO 4.1.4.2 (Win8). Maybe I am doing something wrong. Could you please give more information about the steps especially step 3. Does this issue still also persit for you with the latest release of LO?
I can confirm that this issue still exists in the current 4.1.4.2 release. Apparently the default style in LibreOffice was renamed from "Default" to "Default Style" since this bug reported in LibreOffice 3.5.5.3. In order to reproduce this bug with the new version, a slight modification to the above "Steps to reproduce" is required: 1. Change interface language to German and restart office. 2. Create a new text document, add some text. 3. Add a new user defined style called "Default Style". Do this by opening the "Styles and formating" window (F11). Right click on the style called "Standard" and click "New..." ("Neu..." in german). Set the style name to "Default Style". Then change this new style's font to "Verdana". Note that this don't change anything in your document as in german the default style is called "Standard". 4. Save the document as .ott. 5. Change interface language to English and restart office. 6. Open the .ott file. Your document default style now has "Verdana" set as font.
Created attachment 91369 [details] example update for 4.1.4.2 Also note that the attached example file does not show the error due the rename of "Default" style to "Default Style", so I've attached a new version that shows the error with LibreOffice 4.1.4.2. Just compare the document with english and german interface languages set. In german, the template will display correctly with "Times New Roman" text. With english as interface language, the same document will show in Verdana Bold instead.
Confirmed using Version: 4.2.0.1 Build ID: 7bf567613a536ded11709b952950c9e8f7181a4a and FR lang pack. Set to New Sophie
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (4.4.2 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-05-02
Confirmed using Version: 4.4.2.2 Build ID: c4c7d32d0d49397cad38d62472b0bc8acff48dd6 and DE lang pack.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Confirmed using Version: 5.2.1.2, Build ID: 5.2.1-2 OS Version: Linux 4.7, Locale: de-DE (de_DE.UTF-8)
Reproduced with Version: 5.4.0.3 Build ID: 7556cbc6811c9d992f4064ab9287069087d7f62c CPU threads: 8; OS: Windows 6.2; UI render: default; Locale: de-DE (de_DE); Calc: CL And in my test it doesn't matter whether the saved file is an odt or an ott.
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Reproduced with Version: 6.1.1.2 Build-ID: 6.1.1-3 CPU-Threads: 8; BS: Linux 4.18; UI-Render: Standard; VCL: gtk3_kde5; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group threaded
Dear Michael P., 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Reproduced with Version: 6.3.2.2 Build ID: 6.3.2-2 CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: kde5; Locale: de-DE (de_DE.UTF-8); UI-Language: en-US Calc: threaded
The bug can be reproduce only if we rename the style "Default Paragraph Style". Meanwhile, the default paragraph style have been renamed: "Default Paragraph Style". I supose no one will create a new style exactly with this long name. Everyone should create styles based on what they want to create. Indeed, IF someone with any other language creates a new style with the name "Default Paragraph Style" and change to English user interface, the bug persist. But who would do that? I understanded when was a short name, like "Default". But now? Tested with Version: 7.5.0.1 (X86_64) / LibreOffice Community Build ID: 77cd3d7ad4445740a0c6cf977992dafd8ebad8df CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded
Thanks for the heads-up. So the old repro attachment will not work anymore due to another rename of the style. Note that I reported the issue because this bug actually occurred in practice at a company that used LibreOffice. So this not a theoretical issue. Maybe it becomes less likely the more complicated the default names become, not sure. Ideally, style identification would be decoupled from localization. However I'm no expert here, maybe someone else has an idea.