Skip to content

chore(translations): order units the same as the English catalogues - #3810

Closed
Vondry wants to merge 1 commit into
bolt:6.1from
Vondry:chore/translation-order
Closed

Vondry wants to merge 1 commit into
bolt:6.1from
Vondry:chore/translation-order

Conversation

@Vondry

@Vondry Vondry commented Sep 25, 2026 •

Copy link
Copy Markdown
Contributor

Follow up of #3753

Reorders the units in every locale file (translations/*.xlf) to follow the order of the matching English file (messages.en.xlf, security.en.xlf, validators.en.xlf). This makes the catalogues easier to compare side by side and keeps future diffs aligned across locales.

  • Units that don't exist in the English file are kept and moved to the end of the file.
  • Nothing was removed, added or edited - only moved

Reorder the units in every locale file to follow the order of the
matching English file. Units without an English counterpart are kept
and moved to the end of the file. Only the position of the units
changes; ids, names, sources, targets, states and notes are untouched.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copilot review overview

🟡 Changes recommended

Critical ordering and duplicate-entry issues remain in the French messages and Spanish validators catalogues.

Review effort: Lite
Findings: 2 High severity

Open (2)
What changed in this PR

Reorders translation catalogue units to match the corresponding English catalogues.

Changes:

  • Reordered messages, security, and validators units.
  • Preserved locale-specific entries at the end.
  • Corrected ordering without intended content changes.
File Description
translations/​validators.zh_CN.xlf Reordered validator units
translations/​validators.hu.xlf Reordered validator units
translations/​validators.es.xlf Reordered validator units; duplicate altered entry requires correction
translations/​validators.de.xlf Reordered validator units
translations/​security.de.xlf Reordered security units
translations/​messages.zh_CN.xlf Reordered message units
translations/​messages.uk.xlf Reordered message units
translations/​messages.tr.xlf Reordered message units
translations/​messages.ru.xlf Reordered message units
translations/​messages.it.xlf Reordered message units
translations/​messages.hu.xlf Reordered message units
translations/​messages.fr.xlf Reordered message units; extra entries require contiguous placement
translations/​messages.el.xlf Reordered message units
translations/​messages.cs.xlf Reordered message units
translations/​messages.bg.xlf Reordered message units

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment on lines +2764 to +2769
<unit id="z0k8hRg" name="9fb3e6e">
<segment>
<source>9fb3e6e</source>
<target><![CDATA[Ce site est <a href='https://boltcms.io' target='_blank' title='Sophisticated, lightweight & simple CMS'>Construit avec Bolt</a>.]]></target>
</segment>
</unit>
Comment on lines +34 to +36
<unit id="7smtimf" name="0d999f2">
<segment>
<source>You must select at least {{ limit }} choice.|You must select at least {{ limit }} choices.</source>
<source>0d999f2</source>

@bobvandevijver bobvandevijver left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Looks like both comments from copilot are valid, so those will need to be adjusted.

@bobvandevijver

Copy link
Copy Markdown
Member

Hmm, I wonder whether this will cause merge conflicts with 6.2 due to #3773 being merged.

@bobvandevijver bobvandevijver added topic: Multilingual 🌐 Language, i10n, i18n, translations 🧹 Chore labels Sep 26, 2026
@bobvandevijver bobvandevijver added this to the Bolt 6.1 milestone Sep 26, 2026
@Vondry

Vondry commented Sep 28, 2026

Copy link
Copy Markdown
Contributor Author

Hmm, I wonder whether this will cause merge conflicts with 6.2 due to #3773 being merged.

Yep, there will most likely be some conflicts. Should i redo it on 6.2?

@bobvandevijver

Copy link
Copy Markdown
Member

Hmm, I wonder whether this will cause merge conflicts with 6.2 due to #3773 being merged.

Yep, there will most likely be some conflicts. Should i redo it on 6.2?

Yeah, let's do that 👍🏻

@Vondry

Vondry commented Sep 28, 2026

Copy link
Copy Markdown
Contributor Author

Redone for 6.2 in #3812

@Vondry Vondry closed this Sep 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🧹 Chore topic: Multilingual 🌐 Language, i10n, i18n, translations

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants