Make WordPress Core

Opened 5 years ago

Closed 3 years ago

#10679 closed enhancement (wontfix)

Need filter to catch untranslated strings

Reported by: sirzooro Owned by: nbachiyski
Milestone: Priority: normal
Severity: normal Version: 2.8.4
Component: I18N Keywords: has-patch needs-testing 2nd-opinion
Focuses: Cc:


Currently I am translating many WP plugins to my language. Sometimes it is a bit difficult to find correct context for translated strings, so I decided to simplify things a bit and write plugin which will append "@@" at beginning of untranslated strings. I can do this using gettext filter, but this solution has one drawback - I cannot distinguish when there is no translation from when translated text is the same as original. Therefore I am asking for new filter used for untranslated strings only, or for new param for existing one - I am not sure which will be better from performance perspective (keep in mind that many plugins are used without translations available).

Attached patch adds new filter.

Attachments (1)

translations.php.diff (614 bytes) - added by sirzooro 5 years ago.
New filter in wp-includes/pomo/translations.php

Download all attachments as: .zip

Change History (3)

sirzooro5 years ago

New filter in wp-includes/pomo/translations.php

comment:1 ryan4 years ago

  • Milestone changed from 2.9 to Future Release

comment:2 scribu3 years ago

  • Milestone Future Release deleted
  • Resolution set to wontfix
  • Status changed from new to closed

I don't think the potential usefulness of such a filter is worth the performance penalty.

Note: See TracTickets for help on using tickets.