feat(i18n): wrap user-facing strings across the editor

[surajshetty3416]

Translation support landed with only four demonstration strings, which left
visible inconsistencies: the sidebar rendered a translated "All Pages"
directly above an untranslated "Settings".

Wraps label, tooltip, placeholder, title and Tooltip text attributes along
with toast, confirm and alert messages, taking the catalog from 163 to 337
entries. The extractor reads __() from both the template and the script
block of a .vue file, so both forms reach the POT.

Only prose is wrapped. Bindings, interpolated values and the "Builder"
product name are left alone, and nothing compares a label against a literal
anywhere in the frontend, so no behaviour depends on these strings.

Continuation of #706

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains; the previously reported commented-out strings are no longer extracted.

_{Reviews (4): Last reviewed commit: "feat(i18n): translate template text node..." | Re-trigger Greptile}

[codecov]

Codecov Report

❌ Patch coverage is 40.00000% with 9 lines in your changes missing coverage. Please review.
✅ Project coverage is 66.05%. Comparing base (326ff03) to head (3f6590a).

Files with missing lines	Patch %	Lines
builder/api.py	16.66%	5 Missing ⚠️
builder/ai_page_generator.py	0.00%	3 Missing ⚠️
...ilder/builder/doctype/builder_page/builder_page.py	0.00%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop     #721      +/-   ##
===========================================
+ Coverage    66.01%   66.05%   +0.04%     
===========================================
  Files           37       37              
  Lines         4976     4982       +6     
===========================================
+ Hits          3285     3291       +6     
  Misses        1691     1691              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[mardausdennis]

I checked the normal dashboard/editor journey at the current head (c70379e) and found a few remaining rendered strings that still cannot reach the POT:

• Dashboard/page lifecycle: DashboardContent.vue still has the initial no-pages message and Load More; DashboardHead.vue, DashboardSidebar.vue, PageActionsDropdown.vue, PageCard.vue, PageListItem.vue, and utils/dialogs.ts retain normal filter, sort, folder, status, and page-action prose.
• Editor/publish: BuilderToolbar.vue, MainMenu.vue, and PublishButton.vue still leave basic tool/menu labels plus Publish, Publish Changes, Version History, and Unpublish literal.
• Upload: ImageUploadInput.vue, Controls/ImageUploader.vue, and utils/helpers.ts retain image-fit choices and upload progress/success/error text.
• Restore/errors: VersionHistory.vue still has the empty state and restore confirmation; pageStore.ts retains page open/duplicate/delete/revert messages; BuilderPageRenderer.validate_access() still raises Please log in to view this page. without translation.

The existing unpublish source correctly preserves its quotes and {0} placeholder. Dynamic delete/page-metadata prose should likewise use stable {0} sources rather than interpolated literals. I limited this pass to the normal customer path and excluded AI, developer, analytics, and custom-domain surfaces.

[stravo1]

This will collide with #715 . We need to decide which one makes more sense to merge first.

[greptile-apps]

Too many files changed for review (177 files, 100 file limit).

Bypass the limit by tagging @greptile-apps to review.

[mardausdennis]

Thanks for rebasing this onto the registry refactor. I rechecked the normal customer path at b2dd2f9; many of the earlier items are fixed, but a few rendered strings still bypass translation:

• Dashboard: the initial no-pages state, No folders yet, the folder-delete confirmation, New, and the dynamic edited/created metadata.
• Registry toolbar/editor: remaining literals in BuilderToolbar.vue, ToolbarItems/PageTitlePopover.vue, ToolbarItems/ReadOnlyBadge.vue, ToolbarItems/ToolbarActions.vue, Commands/index.ts, and the normal PageBuilder.vue fallbacks.
• Upload/restore: upload progress and result messages, plus the Version History restore confirmation and Version fallback.
• Page operations/dialogs: duplicate/delete/revert messages and the default Confirm / Alert titles.

Dynamic prose such as Edited {0}, Last updated {0} by {1}, Uploading {0}%, and the delete confirmation should use stable placeholder sources.

[surajshetty3416]

@mardausdennis give it a try again?

[mardausdennis]

Rechecked at 38d68fd. The normal customer path reads much better now: folder delete, version restore, revert, delete/unpublish prompts, dashboard states, publish controls, upload progress and Version History all come through the catalog, and the dynamic ones use stable placeholders.

A few rendered strings are still unwrapped:

• Components: stores/componentStore.ts — Save Component, the delete-component confirmation, and the three sync toasts (Syncing component in all the pages..., Component synced in all the pages!, Error syncing component in all the pages!).
• Route tree: RouteTreeView.vue — Loading pages…, Load {n} more, ({n} remaining); the latter two also in RouteTreeNode.vue.
• Editor shell: PageBuilder.vue — Screen too small and Please switch to a larger screen to edit; PageOptions.vue — the URL Variables section name.
• Command palette: CommandPalette.vue — Search..., Search commands..., No results for "{query}" (the quotes are part of the rendered string), No commands found.
• Toolbar: ToolbarItems/ViewerAvatars.vue — the & {n} others summary.

The count-bearing ones would need stable sources like the ones you already introduced elsewhere: Load {0} more, ({0} remaining), & {0} others, the delete-component prompt, and the palette query.

One thing worth keeping in mind for future callsites: confirm() and alert() translate their default titles and buttons, but pass message through unchanged, so each caller has to wrap its own message.

[mardausdennis]

Opened #746 with the rest of them, including the settings surfaces that earlier sweeps hadn't reached — domains, redirects and users were still almost entirely English.

Two things I left out and explained in the description rather than guessing: the permission messages passed to has_page_write / has_page_read, since a decorator argument resolves at import time, and the gradient/page preset names, which are emitted to callers.

[github-actions]

🎉 This PR is included in version 1.33.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀