#30762 closed defect (bug) (fixed)
Missing context for Next
Reported by: | pavelevap | Owned by: | SergeyBiryukov |
---|---|---|---|
Milestone: | 4.1.1 | Priority: | normal |
Severity: | normal | Version: | 4.1 |
Component: | I18N | Keywords: | has-patch i18n-change fixed-major |
Focuses: | template | Cc: |
Description
There was "Next" string used for button during installation (with meaning "Continue"). Recently was the same string used for get_the_posts_pagination()
(with different meaning "Next post"). We should add context, but I am not sure in which occurence...
Attachments (1)
Change History (11)
#3
@
10 years ago
- Owner set to SergeyBiryukov
- Resolution set to fixed
- Status changed from new to closed
In 31071:
#4
@
10 years ago
- Keywords fixed-major added
- Resolution fixed deleted
- Status changed from closed to reopened
#7
@
10 years ago
Another idea without changing any string: We could use "Continue" instead of "Next" (we are using it in similar cases). And for "Next" and "Previous" there is no need for other context. So in the end, there is one more string less and no change for translators... Should I reopen?
#8
@
10 years ago
"Continue" would need a context too. It's currently only used in the admin and would be translated differently in Russian when used for posts.
The change is already announced on Polyglots, and Next/Previous (with a context) seems consistent to me, so I would leave it as is for now.
#9
@
10 years ago
SergeyBiryukov: Sure, no problem. We can have context, which is better, but "Next" (without context) could be still removed? I did not find any occurence of "Continue" for posts? "Continue" is used only for buttons to continue some action and it would fit to replace our remaining "Next" (without context)?
#10
@
10 years ago
Ah, I see what you mean. "Next" (without context) is only used in signup_user().
Yep, I guess we could replace it with "Continue", let's create a new ticket for that.
We could *possibly* do this in 4.1.1.