fix(i18n): resolve Display Language placeholder

The keyword expansion keys are case-sensitive. Several translations referenced %{Display language}, but the catalogue key is Display Language, so the placeholder was left unresolved in the affected languages. Reference the existing key and rebake the generated catalogues.
This commit is contained in:
Chihiro WATANABE committed 2026-10-30 16:54:46 +09:00
1 parent e5f17a2d36
commit a5232e08d6
11 files changed
+15 -15

No files matched your search

+1 -1
View File
@@ -203,7 +203,7 @@
"Device Setup Method": "Device Setup Method",
"Devices:": "Devices:",
"Diagnostic RTCPeerConnection is enabled": "Diagnostic RTCPeerConnection is enabled",
"dialog.yourLanguageAvailable": "Self-hosted LiveSync had translations for your language, so the %{Display language} setting was enabled.\n\nNote: Not all messages are translated. We are waiting for your contributions!\nNote 2: If you create an Issue, **please revert to %{lang-def}** and then take screenshots, messages and logs. This can be done in the setting dialogue.\nMay you find it easy to use!",
"dialog.yourLanguageAvailable": "Self-hosted LiveSync had translations for your language, so the %{Display Language} setting was enabled.\n\nNote: Not all messages are translated. We are waiting for your contributions!\nNote 2: If you create an Issue, **please revert to %{lang-def}** and then take screenshots, messages and logs. This can be done in the setting dialogue.\nMay you find it easy to use!",
"dialog.yourLanguageAvailable.btnRevertToDefault": "Keep %{lang-def}",
"dialog.yourLanguageAvailable.Title": " Translation is available!",
"Diff": "Diff",