ismailhaddouche
## Problem SQLTools currently displays its contributed UI in English even when VS Code is configured to use another display language. The extension manifest and runtime code do not currently use VS Code localization APIs. For example, with VS Code running in Spanish, the SQLTools activity view still shows: - `Connections` - `No connections found.` - `Add New Connection` - `Bookmarks` - `Query History` The same applies to command titles, configuration descriptions, notifications, quick picks, connection forms, and other runtime messages. ## Proposed approach Use the native VS Code localization mechanisms: 1. Extract manifest strings from `packages/extension/package.json` into `package.nls.json`. 2. Add `package.nls.es.json` with Spanish translations. 3. Gradually replace runtime user-facing strings with `vscode.l10n.t(...)`, including strings in the extension and plugin packages. 4. Add validation to keep locale keys, placeholders, Markdown links, and command URIs synchronized with the English source. A manifest-first PR would immediately localize the activity views, commands, welcome content, and settings shown in VS Code. Runtime localization could follow in smaller, reviewable PRs. ## Scope observed The extension manifest currently contains roughly 199 user-facing values, and additional hard-coded messages exist throughout `packages/extension`, `packages/plugins`, and `packages/vscode`. I can contribute the localization infrastructure and the complete Spanish locale. Would maintainers prefer: - one PR covering manifest localization first, followed by runtime localization PRs, or - a single PR introducing both manifest and runtime localization? I searched existing issues and pull requests and did not find an existing general localization proposal.