[GH-ISSUE #1067] "Version History" button cannot be localized #636

New issue

Closed

opened 2026-05-05 06:25:17 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 06:25:17 -06:00

Owner

Originally created by @isametry on GitHub (Jun 5, 2022).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1067

Describe the bug

The string for the "Version History" button shown is excluded from all localization files, and thus always stays in English:

Steps to reproduce

Menu → Check for Updates…

or alternatively:

Menu → Preferences → About → Check for updates…

Expected behavior

The "Version History" button string should be localized, according to the espective lproj.

Environment Information

- macOS version: macOS 12.4
- Mac model: MacBook, Late 2020
- MonitorControl version: 4.1.0 Build 7034
- Monitor(s): —
- Apple Silicon/M1 (yes or no): yes

Originally created by @isametry on GitHub (Jun 5, 2022). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1067 ### Describe the bug The string for the "Version History" button shown is excluded from all localization files, and thus always stays in English: ![Snímek obrazovky 2022-06-05 v 14 32 35](https://user-images.githubusercontent.com/46103746/172050869-0e900787-ab12-4e8f-a352-62842a4be092.png) ### Steps to reproduce `Menu → Check for Updates…` or alternatively: `Menu → Preferences → About → Check for updates…` ### Expected behavior The "Version History" button string should be localized, according to the espective lproj. ### Environment Information ```markdown - macOS version: macOS 12.4 - Mac model: MacBook, Late 2020 - MonitorControl version: 4.1.0 Build 7034 - Monitor(s): — - Apple Silicon/M1 (yes or no): yes ```

gitea-mirror closed this issue

2026-05-05 06:25:18 -06:00

gitea-mirror commented

2026-05-05 06:25:21 -06:00

Author

Owner

@waydabber commented on GitHub (Jun 14, 2022):

The reason for this is that it is part of Sparkle which is a third party component. You might want to contribute to that project: https://github.com/sparkle-project/Sparkle

If they release an update, it will eventually find it's way to MonitorControl. :)

@waydabber commented on GitHub (Jun 14, 2022): The reason for this is that it is part of Sparkle which is a third party component. You might want to contribute to that project: https://github.com/sparkle-project/Sparkle If they release an update, it will eventually find it's way to MonitorControl. :)

gitea-mirror referenced this issue

2026-05-05 07:05:50 -06:00

[PR #636] [MERGED] Update German Translation #1140