#40763 closed defect (bug) (fixed)
Use placeholders in translation strings
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 4.9 | Priority: | normal |
| Severity: | normal | Version: | |
| Component: | I18N | Keywords: | has-patch |
| Focuses: | administration | Cc: |
Description
The attached patch replaces URLs and HTML tags in translation strings with %s placeholders to make it easier to translate the string.
Attachments (1)
Change History (13)
#2
@
8 years ago
- Milestone changed from Awaiting Review to Future Release
- Type changed from defect (bug) to enhancement
- Version trunk deleted
This ticket was mentioned in Slack in #core-i18n by ramiy. View the logs.
8 years ago
#4
@
8 years ago
- Milestone changed from Future Release to 4.9
- Owner set to SergeyBiryukov
- Status changed from new to reviewing
#6
@
7 years ago
- Keywords needs-refresh added
I think we should take the opportunity to improve the phrasing of these instructions.
- References to
ctrl+Ashould be removed (re-phrase to simply say something along the lines of "select all") - The use of
weandusis bizarre. Let's re-word the affected sentences to remove the need to reference the little people who live inside WordPress.
#7
@
7 years ago
- Keywords needs-refresh removed
@johnbillion Good feedback but those text-changes can be done in separate tickets (use the Text Changes Component).
The scope of this ticket is moving HTML tags, URLs, and other variables outside of translations strings, replacing them with %s placeholders.
This ticket was mentioned in Slack in #core by jeffpaul. View the logs.
7 years ago
Note: See
TracTickets for help on using
tickets.
@ocean90 It's not an enhancement, it's a simple search&replace fixing translation strings. We have several tickets that do the same, they are all defined as defect/bug, let's be consistent.