Bug 458199

Summary: Welcome Screen doesn't follow the Language setting
Product: [Applications] okular Reporter: Enrico <enricobe>
Component: generalAssignee: Okular developers <okular-devel>
Status: RESOLVED WORKSFORME    
Severity: normal CC: aacid
Priority: NOR    
Version First Reported In: 22.04.3   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: okular welcome screen error

Description Enrico 2022-08-23 09:18:35 UTC
Created attachment 151518 [details]
okular welcome screen error

SUMMARY
Hello,
I changed the Okular language from IT to en_GB, but the welcome screen is still in the original language. It seems that the welcome screen language is not changed when you set the en_GB language.

I've tried the following combinations:
Italian -> en_GB > welcome screen in Italian (ERROR)
Italian -> fr > welcome screen in French (OK)
French -> en_GB > welcome screen in Italian (ERROR)
English -> ca > welcome screen in Catalan (OK)
Catalan -> it > welcome screen in Italian (OK)
Italian -> en_GB > welcome screen in Italian (ERROR)

STEPS TO REPRODUCE
1. Open Okular in any language (not en_GB)
2. Change the language to en_GB from Settings -> Configure Language

OBSERVED RESULT
The welcome screen is not in en_GB. I can't understand the exact behavior because it seems to happen also with "ga" language.

EXPECTED RESULT
Welcome screen should be in the language set from the Settings

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.25
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.5
Kernel Version: 5.15.0-46-generic (64-bit)

ADDITIONAL INFORMATION
See attachment for the example
Comment 1 Albert Astals Cid 2022-08-23 21:03:52 UTC
Can't reproduce with 22.0.8 please update and  if you still have this problem please reopen the bug.
Comment 2 Enrico 2022-08-24 09:53:51 UTC
(In reply to Albert Astals Cid from comment #1)
> Can't reproduce with 22.0.8 please update and  if you still have this
> problem please reopen the bug.

Hello,
I confirm that on 22.0.8 this bug doesn't happen. I unfortunately reported it just the day before receiving the update to 22.0.8