[wp-trac] [WordPress Trac] #18495: human_time_diff() localization
WordPress Trac
wp-trac at lists.automattic.com
Tue Aug 23 06:52:04 UTC 2011
#18495: human_time_diff() localization
--------------------------+------------------------------
Reporter: pavelevap | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: I18N | Version: 3.2.1
Severity: normal | Resolution:
Keywords: |
--------------------------+------------------------------
Comment (by pavelevap):
SergeyBiryukov: Yes, it would be partial solution, but it is not possible
to change "5 days" to "5 days ago" in bbPress and so translation is
nonsense even if I change "Freshness". I will try to use ngettext hook to
change it (I am not sure if it can be done conditionally only for bbPress
plugin?).
But generally, it would be helpfull to have for example optional parameter
(or something else) to use human_time_diff() in different ways. It is not
always possible to change meaning in which it is used in different plugins
(or use ngettext filter). There are two common meanings (old and ago)
which should be probably handled differently...
--
Ticket URL: <http://core.trac.wordpress.org/ticket/18495#comment:3>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list