BuddyPress.org

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?

Changing words with the translation file is best practice, so you haven’t to modify anything in a core file.

If you want to modify template files, you do that with a child-theme and by respecting the same directory structure as in bp-legacy/buddypress/…/file_name.php:

wp-content/themes/your_child_theme/buddypress/…/file_name.php

1000 times explained and detailed on this forum and documented on Codex.

I’m not familiar with japanese, sorry. But it could be possible that .ja uses
1) another plural form (the one in the example is for fr and some other occidental languages)
2) another charset as utf8

Read on WordPress Codex where you find more information arond these settings.

Additionaly you can also get in contact with the japanese WP translation team, for better guidance for this very specifif problem or ask for that on the WPpolyglot blog.

bp-languages folder is removed since 2.1
Translations are from now on automatically uploaded from GlotPress, like the WP translation.

Aside this improvement, they are some little bugs, but nothing crucial, which will probably sbe olved in 2.1.1

@oshimamasara7,

I translated buddypress.pot from English to Japanese.(about 80%)

Guess you translated the wrong file.
Must be buddypress.po, not buddypress.pot. And you have to compile the po file into mo.

In the header information, they’re missing keywords. You have only
“X-Poedit-KeywordsList: _;＿;_e\n”

Should be
“X-Poedit-KeywordsList: __;_e;__ngettext:1,2;_n:1,2;__ngettext_noop:1,2;”
“_n_noop:1,2;_c,_nc:4c,1,2;_x:1,2c;_nx:4c,1,2;_nx_noop:4c,1,2;_ex:1,2c;”
“esc_attr__;esc_attr_e;esc_attr_x:1,2c;esc_html__;esc_html_e;esc_html_x:1,2c\n”

1. Rename the file to buddypress-ja.po
2. Add the above keywordlist manually, with a text editor.
3. Open the file with poEdit and run “update” from source or from a blank pot file (yours contain a translation, you’ll have to get a new virgin copy)
4. Translate !

@leighgregg,

you jumped into an over 18 mounths old thread titled How To Limit/Hide The “Friends” Tab and you speak about translation….
Please open a new topic and give details about your issue, BP version and theme.

Hello,

Is this still a viable script? I have tried it, but I get no effect.

Pobpob.com

I have changed the friends to connections in translation, but I guess that isn’t going to effect the core elements here.

Many Thanks

Leigh

Yes it is weird ! And it is not a buddypress issue but a translation issue.

The glotpress po file is uncomplete and contains many errors.
Not sure if it can have an influence on the automatted language upload, but the header is missing the language parameter. (@r-a-y, @boone)

I first tested it “as is” and got same errors as you.
I applied patch #5887… nothing
I used the function mentionned by @r-a-y… nothing
I added the mo into suggested /wp-content/languages/plugins/buddypress/bp-languages/buddypress-es_ES.mo… nothing

So i went back to my original config and used the same settings i usually use for my fr_FR BP version (/wp-content/languages/plugins/buddypress-es_ES.mo)… nothing !

WTF ? 👿 #grumbl…@?/;rrrrr !

So i decided to make a new po by updating the one found on glotpress. (i’m working with poEdit)
This resulted in around 1300 (a little more) new lines and over 100 deprecated lines… and a lot of approximative strings….

In these approx, i found groups, activity and all other strings you mentionned not getting translated. I simply reverted them to valid and bam, the translation worked.

I suggest the following:

• revert back to standard config (no language patch, no language custom functions, no extra language folder) and po/mo in wp-content/languages/buddypress-xx_XX.mo
• download the po from glotpress
• open the file with a text editor and remove the header and replace it with this one:

msgid ""
msgstr ""
"Project-Id-Version: BuddyPress 2.1\n"
"POT-Creation-Date: 2014-09-26 13:34+0100\n"
"PO-Revision-Date: 2014-09-26 14:19+0100\n"
"Last-Translator: \n"
"Language-Team: \n"
"Language: es_ES\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=n != 1;\n"
"X-Poedit-SourceCharset: UTF-8\n"
"X-Poedit-KeywordsList: __;_e;__ngettext:1,2;_n:1,2;__ngettext_noop:1,2;"
"_n_noop:1,2;_c,_nc:4c,1,2;_x:1,2c;_nx:4c,1,2;_nx_noop:4c,1,2;_ex:1,2c;"
"esc_attr__;esc_attr_e;esc_attr_x:1,2c;esc_html__;esc_html_e;esc_html_x:1,2c\n"
"X-Textdomain-Support: yes\n"
"X-Poedit-Basepath: .\n"
"X-Generator: Poedit 1.5.7\n"
"X-Poedit-SearchPath-0: ..\n"

• create a folder in BP called bp-languages-ES (or whatever)
• add the po to this folder
• open the file with poEdit
• update the catalog from source

Now you can see all untranslated lines, the one who are approximative and the one who are already translated.

At this stage, the file is translated to 53% and you’ll have to translate around 770 strings (of 2668).

You also have to check each string containing count variables like %s or %1$s (many are old and must be modified). You’ll find also some plural strings. This is particulary true for approximative strings, who may be similar to the english phrase, but aren’t. Needs good eyes and slow checking ! 😉

Once finished, save your work and copy the mo file into the appropriate language folder:

/wp-content/languages/plugins/buddypress-es_ES.mo (if you want to use your custom translation only)
/wp-content/languages/buddypress-es_ES.mo – if you want automagical 👿 glotpress updates (when avaible, complete and without errors of course).

Hello,

I’m suffering a lot of issues too with the translation into Spanish, in such a way that I had to patch it several times after trying different configurations.

So! To the point. It works for me now and I explain here my current configuration:

1. I’ve downloaded the BuddyPress translation package from https://translate.wordpress.org/projects/buddypress/ and contributed with some translations (specifically for Spanish: https://translate.wordpress.org/projects/buddypress/dev/es/default)

2. Saved the .mo and .po files in /wp-content/languages/plugins as recommended by the Moderators: https://translate.wordpress.org/projects/buddypress/dev/es/default.
And configured the site in Spanish (particularly I tried to do it dinamically)

3. Becuase I try to change the language dinamically according to the browser preferred language I use the xili-language plugin, which “helps” you to manage in what language you’ll display your WordPress, but I’m no sure if it is decisive for the BuddyPress translation. In this plugin there’s a configuration to mention and not enough documented. In case you use the plugn, in the tub “Settings for expert” there are rules to specify. My configuration is:
Wordress rule –> translation in local
BuddyPress rule –> no modification

5. At this point the translation didn’t work correctly or I didn’t succeed in translating some strings that remained in English (like: “Members”, “Groups”, “Notifications”, “Activity” in the BuddyPress navigation menu and others). So, I edited the .po file with PoEdit and updated it with the BuddyPress catalog “buddypress.pot”:

Customizing Labels, Messages, and URLs

6. I updoaded the modified .po and .mo files to the mentioned folder /wp-content/languages/plugins and didn’t change a thing. I read then in forums the different issues with translations, for example:

https://buddypress.org/support/topic/translation-fails-only-at-sitewide-activity/
https://buddypress.trac.wordpress.org/ticket/5655
https://buddypress.org/support/topic/buddypress-2-1-bp-language/
https://buddypress.trac.wordpress.org/ticket/5887
https://buddypress.org/support/topic/buddypress-2-1-known-issues/ (here there’s another workaround)

7. And I added the following lines to the file functions.php of my child theme:

function igf_my_child_theme_setup() {
load_child_theme_textdomain( ‘my_child_theme’, get_stylesheet_directory() . ‘/languages’ );
load_plugin_textdomain(‘buddypress’, false, basename( dirname( __FILE__ ) ) . ‘/languages/’ );
}
add_action( ‘after_setup_theme’, ‘igf_my_child_theme_setup’ );

And it begans to translate correctly! I’m sorry I really don’t understand why. Furthermore I thought that the buddypress textdomain was set by the plugin xili-language but, as I said, I’m not clever enough or it is not well documented.

I know there’s a lot of steps to do, I was really frustated with it, but if you try something like this

Anyway, as this is my first post, I have to thank to the developers for the software and the great effort, of course; it has helped me a lot too.

Regards.