Localization (was Re: [buddypress-dev] Re: buddypress-dev Digest,
Vol 3, Issue 7)
kingler at 72pines.com
Sat Jun 14 20:29:26 GMT 2008
Actually, since BuddyPress is more like a plugin for WPMU, the textdomain
probably should be different from the default WPMU. It simply means that
_e("text"), it is better to use _e("text", "buddypress");
This way, translators can do WPMU translation and BuddyPress translations
separately. And the buddypress translation can be made available for
download with the BuddyPress package.
Just my 2 cents. Once it is ready, Nikolay can probably setup an automatic
POT file generation script for BuddyPress as well. :)
On Sat, Jun 14, 2008 at 10:48 AM, Andy Peatling <andypeatling at automattic.com>
> On 14-Jun-08, at 10:09 AM, Beau Lebens wrote:
> From what I've seen in the code, all output is using WordPress' built in
>> localization functions, so you should be able to create .MO files just like
>> for WordPress for the BuddyPress UI and have it work the same way.
> Exactly, we've used localization functions everywhere so language support
> should work the same way it does for WordPress.
> On Jun 14, 2008, at 2:44 AM, #FN$# wrote:
>> Hi to all!
>>> As I can see,the whole project goes great!(Thanx to Andy and anyone else
>>> who've helped and is still helping!)
>>> BUT,I don't remember anything about the "subject" localization...
>>> Will BP be available on other languages?...
>>> If so,can we help to the translation?...
>>> Thank you for your time!
>>> Keep up!
>>> buddypress-dev mailing list
>>> buddypress-dev at lists.automattic.com
>> buddypress-dev mailing list
>> buddypress-dev at lists.automattic.com
> buddypress-dev mailing list
> buddypress-dev at lists.automattic.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the buddypress-dev