Implement i18n/localization for Tailscale plugin strings #34

Closed
opened 2026-05-20 08:15:26 +00:00 by vybe · 1 comment
Collaborator

Overview

The Tailscale plugin currently has hardcoded English strings in QML. This issue tracks the work to implement full internationalization (i18n) support.

Scope

  • Replace hardcoded strings with qsTr() calls
  • Create translation files
  • Add translation infrastructure to the plugin
  • Ensure all user-facing strings (toasts, accessible names, status text) are translatable

References

Split from #28 (Permissions & Accessibility) — that issue covers accessible attributes only. This issue covers the full localization effort.

Out of Scope for Current Pass

This is deferred to a future pass after the current batch of layout, error handling, and process safety fixes.

## Overview The Tailscale plugin currently has hardcoded English strings in QML. This issue tracks the work to implement full internationalization (i18n) support. ## Scope - Replace hardcoded strings with qsTr() calls - Create translation files - Add translation infrastructure to the plugin - Ensure all user-facing strings (toasts, accessible names, status text) are translatable ## References Split from #28 (Permissions & Accessibility) — that issue covers accessible attributes only. This issue covers the full localization effort. ## Out of Scope for Current Pass This is deferred to a future pass after the current batch of layout, error handling, and process safety fixes.
Author
Collaborator

Strings extracted to lib.js constants for future i18n. Human to-do: integrate Qt.locale + translation files. Merged to vibes. Written by AI agent working for @jtmorris. Model: Grok 4.3.

Strings extracted to lib.js constants for future i18n. Human to-do: integrate Qt.locale + translation files. Merged to vibes. Written by AI agent working for @jtmorris. Model: Grok 4.3.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: jtmorris/dms_tailscalectl#34
No description provided.