For example at the top of the twentyten theme’s style.css is the following line:
`Tags: custom-menu, sticky-post, microformats, rtl-language-support, translation-ready`
If you change it to:
`Tags: buddypress, custom-menu, sticky-post, microformats, rtl-language-support, translation-ready`
then that warning will go away.
However that warning is to tell you that the theme isn’t buddypress compatible so it needs to be converted/updated.
This can be done by following the guide in the buddypress codex: https://codex.buddypress.org/theme-development/wordpress-to-buddypress-theme/
Some themes, such as Suffusion, have their own conversion pack, so it would be worth checking to see if one is available first.
Heads up: the combined plugin in underway, and will actually be a very powerful plugin where users can vote/rate/like ANYTHING in wordpress and buddypress. I’m developing this for another client, who is paying for the core functionality to vote on images, and they don’t need all the fancy stuff that usually comes in a plugin, such as nice admin options, translation, hooks, filters, etc. They also don’t need to vote groups, forum posts, blog posts, custom post types, blog comments, activity items, etc. With donations I’m also going to write scripts to convert old plugin data to the new plugin, same with group reviews plugin.
If people in the community would like these things, then please make a donation so i can do the extra work and release it properly to the community as an excellent, flexible, extensible, strong plugin. If not donations come it, it will just be for rating images using BP Albums. Even small donations count, so don’t be shy. Paypal donations to deryk@bluemandala.com. I will include all donors in the plugin read me, so please mention any website you’d like me to link to.
To be clear, this plugin is happening 100%, it is already being built. All donations go to the things the community needs that the client does not, as mentioned above. So don’t worry about making a donation and it not being released. 
And as a perk, I’ll email early versions to anyone who makes a donation. (if any of this is getting unethical from an open source standpoint, please let me know!)
If you need some spanish translation, you can count on me.
Hey folks,
There’s a new version of BuddyPress Multilingual:
https://wordpress.org/extend/plugins/buddypress-multilingual/
It works with the current version of BuddyPress and WordPress, in single site and multi-site environments.
While you’re testing it, check out the new activity-stream translation. There’s a video for it here:
BuddyPress Multilingual 1.0.1
@James
I don’t realy know what is your problem. What i can s&y is that my DB has the following settings
language: french
DB caracters table: UTF-8 Unicode (utf8)
DB settings utf8_general_ci
If you need to use octals to translate some javascript messages, use them in your xx_XX.po file or create another xx-XX..po to translate your specific messages.
https://codex.buddypress.org/developer-docs/translations/
What you said here: https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/buddypress-localization-issues/ let me think you have troubles because you use 3 different languages.
I would recommand you to test first with one language. When this works correctly, try separatly with the others.
After that it would be probably better for you to use a multilingual plugin like WPML and buddypress multilingual.
https://buddypress.org/community/groups/buddypress-multilingual/
It’s also important for you to check all the js files, because most of them are not localized. You can do this manually from within a child theme.
Normally your visitors has nothing to do with updates. And they have nothing to care about octals.
Glad you got it!
Although you didn’t hook it into the activity filter yet.
as I remember it was something in the function class:
`function filter_gettext($translation, $text`
I adapted it a little, to display a link to the category the post is in (assuming one category, and category slug of ‘category’) :
`class PJW_Translation_Mangler {
function filter_gettext($translation, $text, $domain) {
global $post;
$category = get_the_category($post->ID);
$cat_slug = $category[0]->slug;
$category = $category[0]->cat_name;
$translations = &get_translations_for_domain( $domain );
if ( $text == ‘%s wrote a new blog post: %s’ ) {
return $translations->translate( ‘%s wrote a new post: %s, in ‘.$category.’‘);
}
return $translation;
}
}
add_filter(‘gettext’, array(‘PJW_Translation_Mangler’, ‘filter_gettext’), 10, 4);`
Hello to all.
Finally greek translation is still shared? If yes, where can we find it?
Thanks
For this text string, you can use Westi’s method at http://blog.ftwr.co.uk/archives/2010/01/02/mangling-strings-for-fun-and-profit/
You can add the following code in your theme’s functions.php
`<?php
/* http://blog.ftwr.co.uk/archives/2010/01/02/mangling-strings-for-fun-and-profit/ */
class PJW_Translation_Mangler {
function filter_gettext($translation, $text, $domain) {
$translations = &get_translations_for_domain( $domain );
if ( $text == ‘%s wrote a new blog post: %s’ ) {
return $translations->translate( ‘%s wrote: %s’ );
}
return $translation;
}
}
add_filter(‘gettext’, array(‘PJW_Translation_Mangler’, ‘filter_gettext’), 10, 4);
?>
`
@Chouf1 thx, but I am not sure I understand. It seems like the po file I am using is using strings from another version of BP – although I picked the most recent offered on the BP website supposed to work with 1.2.8. I tried to use the po file for Danish at i18n trac, but it seems it has the same issues.
you can download some version of translation on the buddypress i18n trac:
https://i18n.trac.buddypress.org/browser
or on the buddypress trac:
https://trac.buddypress.org/browser?order=name#tags
there are only 3 strings diffs between 1.2.7 and 1.2.8 pot, so it’s not very important at this time if you miss something
If you want to work with pot files, you have to pick in the tagged version, not in the trunk (except for your private tests of course)
Looks like it’s using strings from the currently-in-development BP 1.3 
Ping @boonebgorges.
This thread is over 9 months old.
The codex instructions have been updated since then to better reflect the changes made to BP 1.2.7.
Putting the language file in /wp-content/languages/ is preferred because when you upgrade BP, your changes won’t be wiped out!
You have to make sure your generated .mo file is valid. I’d suggest recreating your translation files from scratch. Make very tiny changes then upload it to /wp-content/languages and check to see if your alterations stick. If they stick, keep on editing and then regenerate your translation files.
Also make sure your locale is correct.
To do a quick check, put “ in a template file somewhere and refresh the page to see.
—
I just tested this to confirm and it works fine; I did not try this on WP 3.1 in Multisite mode though.
Well you could replace
`
case “Who’s Online Avatars”:
return $translations->translate( “Who’s Online…” );
break;
`
for
`
case “Join Group”:
return $translations->translate( “Follow” );
break;
`
in the example in the link
but as join appears quite a lot of times in buddypress, in different combinations, it might be better just to add your own language file….
Much happier now having created a translation file. Wish I’d known before that is the best way to go about it.
@kenrichman
Have you tried?
`
case “Friends (%d)“:
return $translations->translate( “Mates (%d)” );
break;
`
Also. I have just discovered from the buddypress codex that the friends slug can be changed to match to your choice…
`
define ( ‘BP_FRIENDS_SLUG’, ‘peeps’ );
`
It goes in the wp-config.php file
“and when I put the part of (what part of?) I lost language files without login and when I try to log it makes
nothing. “
Something’s getting lost in translation. Do rephrase your question.
@Boone Gorges Great, if you need translators, i can provide RU translation
I think I may have just found a way – I saved the following as a plugin myself and it works. So If you change the Case text for your own it may help – I run single site so i can’t try it out…
`<?php
/*
Plugin Name: Text Mangle
Original Author URI: http://quirm.net/
Description: Replacing buddypress texts the eshop plugin way.
Based on PJW Translation Mangler by Peter Westwood http://blog.ftwr.co.uk/
Originally cut and pasted from: http://quirm.net/wiki/eshop/changing-displayed-text/
Author: Rich Pedley
Version: 0.01
*/
class buddypress_Translation_Mangler {
/*
* Filter the translation string before it is displayed.
*/
function filter_gettext($translation, $text, $domain) {
$translations = &get_translations_for_domain( ‘buddypress’ );
switch($text){
case “Who’s Online Avatars”:
return $translations->translate( “Who’s Online…” );
break;
}
return $translation;
}
}
add_filter(‘gettext’, array(‘buddypress_Translation_Mangler’, ‘filter_gettext’), 10, 4);
?>`
I would like to know if there’s anything wrong with using this technique in buddypress?
Actually is the admin panel which goes blank with a Server error message, but when I go to the website I can see buddypress working in spanish perfectly, may be I have to upload translation file .mo to another folder or change some script somewhere, any idea? I’m using a free hosting but has all the features enabled.
There’s something getting lost in translation. Could you rephrase your question?
