fix: Telegram plugin shows raw i18n keys instead of translated text

[ankittroy-21]

Description

After opening the Telegram plugin in the sidebar, the QR login screen displays raw translation keys instead of actual text. It looks like the telegram.* namespace is missing from the locale file (or wasn't registered), so the app falls back to showing the keys themselves.

Steps to reproduce

1. Open OmniGet v0.8.1 (Windows, x64)
2. Click Telegram in the sidebar under Plugins
3. Observe the QR code screen

Expected behavior

Proper localized text should appear, e.g. a title like "Log in to Telegram," QR scan instructions, an "or" separator, and a "use phone number" button.

Actual behavior

The following raw keys are shown as literal text instead of translated strings:

• telegram.title
• telegram.qr_title
• telegram.qr_instruction
• telegram.or_separator
• telegram.use_phone

Environment

• OmniGet version: v0.8.1 (omniget_0.8.1_x64-portable.exe)
• OS: Windows
• Language setting: English (ENG/IN)

Screenshot

Additional notes

The QR code image itself renders fine — this appears to be purely a missing/unregistered translation issue in src/lib/i18n/en.json for the Telegram plugin, likely introduced in this release since the plugin/feature looks new.

[tonhowtf]

@ankittroy-21 Thanks for the detailed report — the screenshot and exact keys made this fast to pin down.

Confirmed. Root cause: en.json ended up with two root-level "telegram" objects after the Direct Uploader work in #197 — one with the 65 login/chats/media keys, and a second one appended at the end with the 37 uploader keys. JSON parsing is last-key-wins, so the entire first block gets silently dropped at runtime. Worse, our locale-sync tooling then ran against the broken parse and stripped those 65 keys (and their real translations) from all 9 non-English locale files and from the generated keys.ts.

So it's wider than the QR screen and not just English — the entire Telegram plugin UI (login, 2FA, chat list, media browser, batch download) shows raw keys in every language on 0.8.0/0.8.1.

The good news: the pre-#197 translations are all recoverable from git history, so this comes back fully translated, not just fixed in English. PR #266 addresses part of this and I've reviewed it there; the fix lands in the next patch release.

[tonhowtf]

This shipped in v0.8.5, just published — the full Telegram UI is translated again in all 11 languages, with the original translations restored (not English placeholders). Thanks again for the report, and credit to @ManoloZocco for the fix in #266. If any raw key still shows up after updating, reopen with a screenshot.