Created attachment 136284 [details] Strings shown untranslated in Upper Sorbian LO Hi, I'm LO translator for Upper Sorbian (hsb) amd Lower Sorbian (dsb). I completed the translation of LO 5.4.1.* into Upper Sorbian for a long time and it is included in the stable release now. But, there are some strings untranslated: 1. In the sidebar (and maybe somewhere else as well), some strings are shown in English (see screenshot in attachment) 2. Some strings are taken from OS, so they appear in OS language. For Sorbian languages they appear in German, see bugs https://bugs.documentfoundation.org/show_bug.cgi?id=103417 and https://redmine.documentfoundation.org/issues/2334 Please update the English strings and fix the bug with OS strings.
Created attachment 136296 [details] Panel Hello, This Seem to be translated in LO 5.4.1.2 (x64) ID zestajenki: ea7cb86e6eeb2bf3a5af73a8f7777ac570321527 CPU-niće: 2; Dźěłowy system: Windows 6.1; UI-render: standard; Narodna šema: hsb-DE (fr_FR); Calc: CL Cordially
Merci, Jacques. :-) Yes, thus it must look. And you see the OS strings which are in French with you and in German with me. But this is another bug ticket.
Hi Jacques, the strings are still untranslated in 5.4.2.1 (pre-release). They are translated for a long time, why it is not possible to update the Upper Sorbian locale?
Any update with last LO version? On pc Debian x86-64 with master sources updated some days ago, sidebar is quite different from yours.
Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Created attachment 144403 [details] Untranslated strings in Upper Sorbian Writer sidebar
Hi, I think this bug can be marked as resolved. I didn't find untranslated strings in LO 6.2.0.0 beta anymore.
Closing a RESOLVED WORKSFORME then...
Hi Xisco, I've downloaded LO 6.1.4.1 today. There this is not fixed yet. I don't know if it is still worth fixing this bug for LO 6.1.5 and LO 6.1.6.
Oh, sorry, I tried a new profile and all is correct now. The bug can be definitely marked as resolved now.