Add hook for translating English

[Viper007Bond]

I want to be able to make __('foo') return bar, even if the blog is in English. If WordPress is in any other language besides English, I think you can just use the "gettext" filter to do this. However, my blog is in English, so you can't.

Attached patch adds a backwards compatible pre-translating hook for allowing plugins to switch phrases before they are translated.

It also passes the domain to "gettext" filter for the hell of it.

[westi]

Can you not create a translation file even for an English blog.

i.e set WP_LANG to en_Viper and have a en_Viper.mo file.

[pishmishy]

Agreeing with Westi here. Nothing forces you not to use English in translation files. Since there's no response I'll presume that you've tried this method and been successful. Please let us know if there's problems with this approach though.

[Viper007Bond]

Sorry, seemed to be missed westi's response.

I'm talking about a plugin here, not my own personal blog.

However, I honestly can't remember what I was trying to do at the time. I think I was trying to use the default widgets page for managing the dashboard and didn't want to use an output buffer.

So yeah, reopening for feedback, but not hard set on wanting it as I can just use an output buffer to modify strings. Still though, having a pre-filter much like you can do with get_option() would be handy and I don't see any harm except maybe extra CPU cycles.

[pishmishy]

I don't see the harm either, but not convinced I see the need =)

[caesarsgrunt]

I have wanted this on a few occasions too, so as to avoid output buffering to change strings without filters such as the comments page header.
PLEASE include this, I've been wanting it for ages! :)

[westi]

(In [9211]) Allow plugins to mangle translations of english strings as well as translated strings. Fixes #6742.

[westi]

Slightly different change there but that now passes all strings through the one filter so plugins can have there way translation or no translation.