i18n(hi): add Hindi (हिन्दी) translations

[ankit-fastcurveservices]

What does this PR do?

Adds Hindi (हिन्दी / hi) translations for the EmDash admin UI.

All 1,938 translatable strings are translated with ICU placeholders preserved, plural forms validated, and consistent Hindi terminology (e.g. पुनर्निर्देश for redirects, कूड़ेदान for trash, फ़ील्ड for schema fields). The locale is enabled in the admin UI.

Follows the same pattern as #872 (Indonesian).

Type of change

• Bug fix
• Feature (requires maintainer-approved Discussion)
• Refactor (no behavior change)
• Translation
• Documentation
• Performance improvement
• Tests
• Chore (dependencies, CI, tooling)

Checklist

• I have read CONTRIBUTING.md
• pnpm typecheck passes
• pnpm lint passes
• pnpm test passes (or targeted tests for my change)
• pnpm format has been run
• I have added/updated tests for my changes (N/A — translation only)
• User-visible strings in the admin UI are wrapped for translation
• I have added a changeset
• New features link to an approved Discussion (N/A — translation)

AI-generated code disclosure

• This PR includes AI-generated code — model/tool: Claude (Cursor), Google Translate API (batch translation), with manual ICU syntax and terminology fixes

Test output

pnpm locale:extract → hi: 1938 total, 0 missing
pnpm locale:compile → Done
msgfmt --check --check-format → OK
msgcmp --use-untranslated → OK
pnpm lint:quick → clean
pnpm format → clean

Notes

• Hindi (hi) is LTR — no dir property needed
• All placeholders ({0}, {email}, etc.) preserved unchanged
• Plural forms use one / other with Hindi inner text
• Native Hindi review welcome before merge

Made with Cursor

[changeset-bot]

🦋 Changeset detected

Latest commit: 33de59c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 17 packages

Name	Type
@emdash-cms/admin	Patch
emdash	Patch
@emdash-cms/cloudflare	Patch
@emdash-cms/sandbox-workerd	Patch
@emdash-cms/plugin-mcp-smoke	Patch
@emdash-cms/fixture-perf-site	Patch
@emdash-cms/perf-demo-site	Patch
@emdash-cms/cache-demo-site	Patch
@emdash-cms/do-demo-site	Patch
@emdash-cms/do-solo-demo-site	Patch
@emdash-cms/auth	Patch
@emdash-cms/blocks	Patch
@emdash-cms/gutenberg-to-portable-text	Patch
@emdash-cms/x402	Patch
create-emdash	Patch
@emdash-cms/auth-atproto	Patch
@emdash-cms/plugin-embeds	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

Scope check

This PR changes 8,865 lines across 3 files. Large PRs are harder to review and more likely to be closed without review.

If this scope is intentional, no action needed. A maintainer will review it. If not, please consider splitting this into smaller PRs.

See CONTRIBUTING.md for contribution guidelines.

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[emdashbot]

This PR follows the established translation-only pattern: it adds a complete Hindi PO catalog, enables hi in locales.ts, and includes a patch changeset for @emdash-cms/admin. The approach is sound and fits EmDash’s i18n architecture — there are no code behavior changes outside the admin locale list, so SQL, authorization, content-table filters, and logged-out route queries are all unaffected.

I spot-checked the new catalog against the English source: all ICU tags and placeholders are preserved, plural/select argument names match, and there are no fuzzy or obsolete entries. There are no new tests (correctly marked N/A for a translation), and the changeset package/version bump is appropriate.

The one concrete issue is that four translated strings drop the leading whitespace that exists in their source msgid. These spaces are functional — the strings are concatenated immediately after values or other text — so omitting them produces visible spacing regressions such as slug-अतिथि, filename(चयनित), etc. Fixing those four msgstr lines is the only blocker before I’d be happy to approve.

[emdashbot]

[needs fixing] The msgid is " - Guest" with a leading space, but the translation msgstr "- अतिथि" drops it. The calling code concatenates this directly after item.slug (packages/admin/src/routes/bylines.tsx:446), so the slug will abut the hyphen in Hindi (e.g. my-slug-अतिथि). Preserve the leading space from the source string.

Suggested change

	msgstr "- अतिथि"
	msgstr " - अतिथि"

[emdashbot]

[needs fixing] The source " - Linked" includes a leading space for the same inline concatenation as " - Guest" (packages/admin/src/routes/bylines.tsx:446). The translation should keep that space so the slug does not run into the hyphen.

Suggested change

	msgstr "- जुड़ा हुआ"
	msgstr " - जुड़ा हुआ"

[emdashbot]

[needs fixing] The source " (opens in new window)" begins with a space because it is rendered right after a menu label (packages/admin/src/components/MenuEditor.tsx:521). The current translation will appear attached to the preceding text; keep the leading space for consistent spacing.

Suggested change

	msgstr "(नई विंडो में खुलता है)"
	msgstr " (नई विंडो में खुलता है)"

[emdashbot]

[needs fixing] This string is interpolated into an aria-label as ${item.filename}${selected ? t (selected) : ""} (packages/admin/src/components/MediaPickerModal.tsx:867,950). Dropping the leading space produces filename(चयनित) for screen-reader users. Restore the leading space.

Suggested change

	msgstr "(चयनित)"
	msgstr " (चयनित)"