## Summary

Please provide a supported localization mechanism for Omarchy's shell UI and its plugin ecosystem.

## Scope

This request is mainly about:

- Built-in shell plugins and panels.
- The Omarchy menu and other shell-owned UI.
- A translation helper/API that third-party Omarchy plugins can use.

It is not a request to translate every application shipped with the distribution.

## Motivation

A number of visible strings in the shell and built-in plugins are currently hardcoded in QML, for example search placeholders, empty states, dialog buttons, panel labels, and menu messages. Third-party plugins also have to implement their own translation systems from scratch.

For users who want Spanish or another language, this means maintaining local patches that can be overwritten by Omarchy updates, or translating each plugin independently.

## Suggested approach

- Add a small localization helper available to shell code and plugins.
- Store first-party translations in language files, with English as the fallback.
- Add a locale setting in the Omarchy configuration.
- Allow user overrides under `~/.config/omarchy/locales/` so custom translations survive updates.
- Document how third-party plugins can declare and load their translations.
- Keep stable translation keys instead of making plugins search and replace visible English strings.

This could cover shared UI components, the bar, panels, notifications, the Omarchy menu, and plugin manifests/settings while leaving the choice of translations to contributors.

## Example

A user could select Spanish once in Omarchy and have the shell and compatible plugins use it automatically. A user or contributor could then add or override a missing string without editing files under `/usr/share/omarchy/`.

This would make localization maintainable for both Omarchy itself and the plugin ecosystem.

> Note: This issue was drafted with assistance from AI.