Skip to content

Move "Wrap text" and "Break text" translations to core#20157

Merged
jacek-cke merged 2 commits into
masterfrom
ck/move-wrap-break-text-translations-to-core
May 15, 2026
Merged

Move "Wrap text" and "Break text" translations to core#20157
jacek-cke merged 2 commits into
masterfrom
ck/move-wrap-break-text-translations-to-core

Conversation

@jacek-cke
Copy link
Copy Markdown
Contributor

@jacek-cke jacek-cke commented May 15, 2026

🚀 Summary

  1. Move shared Wrap text and Break text translations to core via pnpm run translations:move.
  2. Run pnpm run translations:synchronize to synchronize translations.

🧾 Checklists

Use the following checklists to ensure important areas were not overlooked.
This does not apply to feature-branch merges.
If an item is not relevant to this type of change, simply leave it unchecked.

Author checklist

  • Is the changelog entry intentionally omitted?
  • Is the change backward-compatible?
  • Have you considered the impact on different editor setups and core interactions? (e.g., classic/inline/multi-root/many editors, typing, selection, paste, tables, lists, images, collaboration, pagination)
  • Has the change been manually verified in the relevant setups?
  • Does this change affect any of the above?
  • Is performance impacted?
  • Is accessibility affected?
  • Have tests been added that fail without this change (against regression)?
  • Have the API documentation, guides, feature digest, and related feature sections been updated where needed?
  • Have metadata files (ckeditor5-metadata.json) been updated if needed?
  • Are there any changes the team should be informed about (e.g. architectural, difficult to revert in future versions or having impact on other features)?
  • Were these changes documented (in Logbook)?

Reviewer checklist

  • PR description explains the changes and the chosen approach (especially when performance, API, or UX is affected).
  • The changelog entry is clear, user‑ or integrator-facing, and it describes any breaking changes.
  • All new external dependencies have been approved and mentioned in LICENSE.md (if any).
  • All human-readable, translateable strings in this PR been introduced using t() (if any).
  • I manually verified the change (e.g., in manual tests or documentation).
  • The target branch is correct.

Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 4123176. Configure here.

Comment thread packages/ckeditor5-core/lang/translations/en.po
@jacek-cke jacek-cke requested a review from pomek May 15, 2026 08:07
@jacek-cke jacek-cke merged commit f9d5d95 into master May 15, 2026
12 checks passed
@jacek-cke jacek-cke deleted the ck/move-wrap-break-text-translations-to-core branch May 15, 2026 08:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants