Created attachment 93139 [details] See the un-localized strings marked with red. Using 4.2.0.4 64-bit on OS X with Slovenian langpack - there is a special entry in the Settings windows at the end, totally unlocalized, although these strings were already localized. They are settings for English sentence checking, see attached screenshot.
Not confirmed with FR langpack and 4.2.0.4 64-bit on Ubuntu 13.10, the tab is correctly translated - Sophie
Martin: one for you?
What do you mean, one for me?
In LO 4.2.1.0.0+ with FR UI and Grammalecte grammar checking installed, I have this tab localized, but the category name (Language Settings) is not. Best regards. JBF
This is a weird bug.
miles: sorry for this! I had just taken a look to https://wiki.documentfoundation.org/Language_Teams and didn't even realized it was you! :-) Just forget my previous comment :-)
Can't confirm on Debian Linux (32-bit) with Estonian nor Slovenian language pack.
This works with Slovenian 4.2.4 RC1, so I am closing this as Resolved.
This reappeared in 4.3.0.beta1 on OS X 64-bit Slovenian, probably also on other systems. Reopening.
(In reply to comment #9) > This reappeared in 4.3.0.beta1 on OS X 64-bit Slovenian, probably also on > other systems. > > Reopening. 4.3 has not received translation updates yet.
Markus, yes it has, Slovenian is not using Pootle and it was checked in last Sunday, and compared to actual beta1 strings there are only 75 fuzzy and 3 untranslated strings in the official 4.3.0.0.beta1 Slovenian packs, and none of these strings is from this dialog. We have done our math.
Created attachment 99699 [details] screenshot with slovenian UI on master sources On pc Debian x86-64 with master sources updated yesterday + slovenian UI, I don't reproduce the problem.
I can confirm this again on OSX with 4.3.0.1 64-bit build (RC1). I even deleted the installed version and the application settings in the Library folder and reinstalled from scratch, but still see these strings.
Andras: Do you know if there's a problem with Pootle for slovenian part? I don't understand why my screenshot could show slovenian translations and not the 4.3.0.1 from Miles.
(In reply to comment #14) > Andras: Do you know if there's a problem with Pootle for slovenian part? I > don't understand why my screenshot could show slovenian translations and not > the 4.3.0.1 from Miles. Slovenians don't use Pootle. You use Linux. The bug occurs on OS X.
Created attachment 101892 [details] screenshot on Mac with master sources On MacOs 10.9.3 with master sources updated yesterday, it seems ok. Of course, master sources are not 4.3 Andras: I didn't think translation could work on a platform and not on another one. I'll try to keep this in mind :)
(In reply to comment #16) > Created attachment 101892 [details] > screenshot on Mac with master sources Same here. The problem is with the release builds. I did not have time to debug.
I don't know why it was in NEEDINFO but if someone knows, just explain and put back to NEEDINFO.
** 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.0.0.5 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-09-03
** 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
Seems to have been fixed, closing.