Bug 7270 - client isn't translated when connected on macOS
Summary: client isn't translated when connected on macOS
Status: CLOSED FIXED
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VNC (show other bugs)
Version: 1.3.1
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.14.0
Assignee: Pierre Ossman
URL:
Keywords: relnotes, samuel_tester
: 7523 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-11-01 14:57 CET by Pierre Ossman
Modified: 2021-11-22 17:13 CET (History)
2 users (show)

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Pierre Ossman cendio 2018-11-01 14:57:32 CET 
The translations on macOS work fine in the login window (tlclient), but not once connected (vncviewer).

Haven't determined why, but I suspect the nested bundling is an issue where vncviewer fails to find the .mo files.
Comment 1 Pierre Ossman cendio 2021-11-17 16:28:09 CET 
*** Bug 7523 has been marked as a duplicate of this bug. ***
Comment 2 Pierre Ossman cendio 2021-11-17 16:29:46 CET 
It looks like we've simply forgotten about macOS when we compute the location of the locale dir. We only have code paths for Windows and "other", which seems to assume the Linux directory layout.
Comment 4 Samuel Mannehed cendio 2021-11-22 17:13:18 CET 
Works well. I could reproduce the issue on macOS 11.6 using Swedish system language and the 4.13.0 client. The F8 menu and Options were not translated once connected.

Verified that things are properly translated when using the nightly (build 2271) client on the same machine.

Code changes and release notes look good.
Note You need to log in before you can comment on or make changes to this bug.