#3456 closed defect (bug) (fixed)
Filter and localize pagination prev and next text
Reported by: | r-a-y | Owned by: | |
---|---|---|---|
Milestone: | 1.5 | Priority: | normal |
Severity: | minor | Version: | 1.1 |
Component: | Core | Keywords: | has-patch |
Cc: |
Description
Attached patch is against r4947 and allows theme developers and translators to modify the paginated "prev_text" and "next_text" values.
By default, these values are ←
and →
respectively.
Patch also removes a bunch of whitespace in these files.
Attachments (1)
Change History (6)
#2
@
13 years ago
Everything going through gettext can already be filtered (for example).
#3
@
13 years ago
- Milestone changed from Awaiting Review to 1.5
I'm going to put this patch in, minus the extra filters, and we can re-open the ticket if there's a particularly good reason :) Thanks for the patch, r-a-y
#5
@
13 years ago
Wasn't aware of the 'gettext' filter until just now! This is great!
http://codex.wordpress.org/Plugin_API/Filter_Reference/gettext
We do filters + localization in:
- Activity 'Read More' text - http://buddypress.trac.wordpress.org/browser/tags/1.5-beta-2/bp-activity/bp-activity-filters.php#L189
- BP core time since - http://buddypress.trac.wordpress.org/browser/tags/1.5-beta-2/bp-core/bp-core-functions.php#L610
- No-reply email address - http://buddypress.trac.wordpress.org/browser/tags/1.5-beta-2/bp-core/bp-core-filters.php#L53
- A few activity actions
Might want to change these as well?
Thanks, r-a-y. What's the justification for l18n + filters? Do we do something similar elsewhere in BP?