Skip to content

Conversation

@fredrikekelund
Copy link
Contributor

Related issues

p1767093925737899-slack-C06DRMD6VPZ

Proposed Changes

Minor translation tweaks to ensure consistency and good translations.

Testing Instructions

Code review should suffice

Pre-merge Checklist

  • Have you checked for TypeScript, React or other console errors?

@fredrikekelund fredrikekelund requested a review from a team January 2, 2026 13:48
@fredrikekelund fredrikekelund self-assigned this Jan 2, 2026
@wpmobilebot
Copy link

wpmobilebot commented Jan 2, 2026

📊 Performance Test Results

Comparing 040e0ec vs trunk

site-editor

Metric trunk 040e0ec Diff Change
load 5640.00 ms 6166.00 ms +526.00 ms 🔴 9.3%

site-startup

Metric trunk 040e0ec Diff Change
siteCreation 9073.00 ms 9073.00 ms 0.00 ms ⚪ 0.0%
siteStartup 3942.00 ms 3951.00 ms +9.00 ms 🔴 0.2%

Results are median values from multiple test runs.

Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change

Copy link
Contributor

@katinthehatsite katinthehatsite left a comment

Choose a reason for hiding this comment

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

This looks good to me, I only reviewed the phrases that were changed in this PR and not all the comments from the Slack thread though 👍

showLabels
valueLabel={ formattedSize }
limitLabel={ formattedLimit }
// translators: %s is a filesize string. This label is displayed if a sync archive is larger
Copy link
Contributor

@nightnei nightnei Jan 5, 2026

Choose a reason for hiding this comment

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

NIT I am thinking, does it make sense to add an example with such a "translators" comment?
e.g::

Suggested change
// translators: %s is a filesize string. This label is displayed if a sync archive is larger
// translators: %s is a filesize string, e.g. "1.3GB over". This label is displayed if a sync archive is larger

Of course, it's obvious, but if we go this way with "translators", maybe we could have it as an agreement for the future cases. Current one is preety good w/o it.

Copy link
Contributor

@nightnei nightnei left a comment

Choose a reason for hiding this comment

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

LGTM 👍

Copy link
Contributor

@nightnei nightnei left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@fredrikekelund fredrikekelund merged commit f684371 into trunk Jan 6, 2026
8 of 9 checks passed
@fredrikekelund fredrikekelund deleted the f26d/translation-tweaks branch January 6, 2026 11:38
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.

5 participants