BuddyPress.org

Have you added a bp translation manually to another folder ? If yes, delete it.

If you use WP since a while and updated it recently, search a line containing define(‘WPLANG’, ‘xx_XX’)- xx_XX is a lang iso code, in wp-config.php. If you find one, delete it as it is no more used in WP 4.1

Control via FTP that bp translation is in wp-content/languages/plugins/buddypress-fr_FR.mo
If not there, ensure that /language/ and /plugins/ have their write access set to 755
The mo file should be 644.

Hi,

it is a custom string, you will not find it in the po file. So you can translate it directly in the function.

'%1$s created a new Project, %2$s'

'%1$s your translation, %2$s', where first variable is the username and the second the project name

You could also do differently and add this custom string to your po file, but in this case, you have to take care that your translation is not overiden by the next language update.

Spanish po/mo is only translated to 87% on glotpress and this phrase is actually not translated in the avaible version.

It seems you use wordpress-language plugin, who automatically upload the mo file for you and who probably overides your work.
Deactivate this plugin first, do your translation with poEdit, and add manually by FTP the po/mo files to wp-content/languages/plugins/buddypress-es_ES.mo

For more details and answers, read the longest BP topic about language:
https://buddypress.org/support/topic/buddypress-2-1-bp-language/

Your po/mo files should be added to this path (create it if it doesn’t exist):

wp-content/languages/plugins/buddypress-xx_XX.mo (where xx is the lang ISO code) For english, en_EN or en_US…

If you need more details how translation are working, search for “translation” or “language” on the forum.

Be carefull and keep a copy of these files localy ! 😉

Polylang plugin is intended to translate your site content

To translate BuddyPress you have to use the translation support shipped with the plugin (buddypress.pot in bp-languages folder) and create your own version of po/mo files.

Or to get a ready to use BP translation in your language, check out from here
For any hints about translation, or to contribute, see here.

Please use the code button to format code you paste into this forum.

To remove the count…
Assuming you aren’t using a language translation file, try this in your bp-custom.php file.

function john_gettext( $translated, $original_text, $domain ) {

    if ( 'buddypress' !== $domain )  
           return $translated;

    switch ( $original_text ) {
        case 'All Members <span>%s</span>':
            return 'All Members';

        default:
            return $translated;
    }
}
add_filter( 'gettext', 'john_gettext', 20, 3 );

We can’t help with validating the translations on translate.wordpress.org. I am not sure who manages the Persian translations. If you can’t find out either, ask on https://make.wordpress.org/polyglots/

Thank you for contributing translations to BuddyPress 🙂

@sadeghr Thank you for your contribution. I have updated the codex page based on what I assumed you meant. Please let me know if there are any changes to the text.

Contribute to the translation on https://translate.wordpress.org/projects/buddypress/dev and then, eventually, your WordPress will download the updated translation automatically. 🙂

@tsabar,

the widget remain in english because the translation is missing.

The hebrew version on GlotPress, where BP picks the automatic translation in your language is not completly translated (64%).

Download it and finish the translation on your computer. BP comes with a buddypress.pot file which you must use to do this. And use poEdit or a similar software.

Concerning the widget, you have to translate this string in the po file:
<a href=\"%s\" title=\"Register for a new account\">Register</a>

Aside, bp and po files are always in UTF8.
If you save a po file in ANSI, you have to use exclusively ANSI without BOM (.txt format and evtl. change the file extension to your need)

To generate the mo file, you must use a compiler like poEdit.

Also avoid to hack core files and don’t make a translation on the admin side.

I’ll find more details around how to translate in some previous topics, since 2.1 is out.

@mineo

there are always difference between two BuddyPress version…. If you use a custom translation, you must update your version at each BP update. This is how translating a plugin or a theme works and has nothing to do with php files or studying the support.

Version 2.0

Version 2.0.1

Version 2.0.3

Version 2.1

and so on…

For example, the difference between 2.0.1 and 2.1 is not the translation itself, but the translation comments who where added for better disambiguation.

So for example the word “activity’ in bp 2.01 is written in the po file like this:

#: bp-activity/bp-activity-loader.php:165
#: bp-activity/bp-activity-loader.php:276
msgid "Personal"
msgstr ""

and in BP 2.1, you see this:

#: bp-activity/bp-activity-loader.php:277
msgctxt "My Account Activity sub nav"
msgid "Personal"
msgstr ""

A comment was added who look like this: msgctxt "My Account Activity sub nav"

Because of this comment, even if the phrase is already translated, poEdit consider that there is a modification and mark this phrase as fuzzy. And because it is fuzzy, gettext doesn’t use it and the word stays in english.

In 2.1 “activity” remains 9 times alone, with 9 different disambiguation context, in difference to older versions where “activity” was used indifferently for any context.

So if you didn’t take care of such difference, you can think your word is translated. It is, but outside of the context.

msgctxt "Page title for the Activity directory."
msgid "Activity"

msgctxt "Activity items per page (screen options)"
msgid "Activity"

msgctxt "Admin Dashbord SWA page title"
msgid "Activity"

msgctxt "Admin Dashbord SWA menu"
msgid "Activity"

etc
This means of course that you have to translate “activity” 9 times, instead one time, but the avantage to write it differently, depending your language and the context where the word is used.

And again, modifying a po file with a text editor without compiling it into mo format is unuseable. You must use a compiler like poEdit, as gettext use .mo file to translate.

Po/pot files are only working files, not system files like mo is.

@mineo

Slovak BuddyPress lang community declares that the files are fully translated.

False ! According to the GlotPress stats, the buddypress translation is only 64% translated.

You have to finish the translation.
Download the po from glotpress
Update that file from the pot file who comes with BP 2.1

Use poEdit to do this.

https://buddypress.org/support/topic/buddypress-2-1-bp-language/

Ok if you disable however you are loading the translation – that might be deactivating WPML – so that everything goes back to the default English, do the tabs work?

It’s a matter of finding the exact syntax.
This works in the function I provided.

        case 'Friends <span class="%s">%s</span>':
            return 'Connections <span class="%s">%s</span>';

A gettext filter is a reasonable approach if there are one or two labels that need to be changed.
But there are so many different places where ‘Friend’ or some variation is used that in your case you should definitely use a .mo file.
Read:

Customizing Labels, Messages, and URLs

Often there is confusion re the Sources Keywords section of PoEdit, so after you read the above, take a look at http://www.cssigniter.com/ignite/wordpress-poedit-translation-secrets/
especially the section titled ‘Keywords lists, WordPress functions, whaaaaaa?’.

I assume you are using a .mo translation file – are you?. If you remove it (so it goes back to English), does the problem still remain?