Fonts Library: Fix translatable strings and enforce l10n best practices #58201
Labels
[Feature] Font Library
[Feature] Typography
Font and typography-related issues and PRs
l10n
Localization and translations best practices
[Status] In Progress
Tracking issues with work in progress
[Type] Bug
An existing feature does not function as intended
Description
Splitting this out from #58110 / #58117
There's a couple places in the Fonts Library user interfaces where translatable strings are less than ideal and are hardly translatable:
gutenberg/packages/edit-site/src/components/global-styles/font-library-modal/font-card.js
Lines 59 to 64 in 50fa46b
and
gutenberg/packages/edit-site/src/components/global-styles/font-library-modal/local-fonts.js
Lines 34 to 38 in 50fa46b
To recap some of the l10n best practices, which are better detailed in the WordPress handbook:
sprintf()
and placeholders when appropriate.__()
function. These cases need to be handled either bu providing separate strings or by using the_n()
function.Step-by-step reproduction instructions
N/A
See code snippets linked above.
Screenshots, screen recording, code snippet
No response
Environment info
No response
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes
The text was updated successfully, but these errors were encountered: