Replace hardcoded "Loading..." strings with i18n keys

[kanweiwei]

Several components have hardcoded English "Loading..." strings instead of using i18n translation keys.

Known locations:

• web/src/components/file-viewer/FilePreview.tsx line 296: <div>Loading...</div>
• web/src/components/plugins/PluginHTMLRenderer.tsx line 188: {isReady ? 'Ready' : 'Loading...'}
• web/src/components/plugins/PluginHostAPI.tsx line 1134: {isReady ? 'Plugin Ready' : 'Loading...'}

What to do:

1. Find all occurrences of hardcoded "Loading..." in web/src/components/
2. Replace each with the appropriate i18n key (e.g. t('common.loading') or t('plugins.loading'))
3. Add any missing keys to all 4 locale files in packages/i18n/src/locales/

Skills needed: TypeScript, basic grep/search

Estimated time: 30 minutes

[snakefood3232]

I'll replace those hardcoded "Loading..." strings with proper i18n keys. I'd handle this by first finding all occurrences in web/src/components/, then adding the appropriate keys to all four locale files. Can have a PR up in a few hours—I regularly implement i18n in TypeScript/Next.js projects.

[snakefood3232]

I’ll replace all hardcoded “Loading…” strings in web/src/components/ with i18n keys. I’d handle this by searching for occurrences, mapping them to appropriate keys, and updating all four locale files. Can have a PR up in a few hours—I regularly work with TypeScript and i18n in Next.js projects.

[snakefood3232]

I can replace those hardcoded "Loading..." strings with proper i18n keys. I'll grep through web/src/components/ to find all occurrences, replace them with t() calls, and add the necessary keys to all four locale files. I can have a PR ready within an hour.

[snakefood3232]

I'll replace those hardcoded "Loading..." strings with proper i18n keys. I'd handle this by first finding all occurrences in the components directory, then implementing the translations across all four locale files. Can have a PR up in a few hours—I've worked on multiple i18n implementations in Next.js projects.