BuddyPress.org

Here what i have on my test install, 2012 + wp+bp in spanish

as you see, the wp part IS in spanish, and most of the bp items are in english, and some are in spanish.

Guess you have to review the whole translation manually with poedit or at least try to setup your site to another spanish format, so that bp could use that one. With a little chance, one of them is correctly translated.

Open the po file with poedit and update it with the POT file shipped with BP 2.2.1.
And complete/modify the translation, save and add the mo file to live site languages/plugins/ directory.

I can’t help you for a premium theme as i have no access to it without paying.
See theme’s support for that.

But before, let’s try something other.

Set your site language to italian and save. WP will upload the italian translation. If not, do it manually from glotpress and see that you have wp-content/languages/it_IT.mo

Your site is now in italian. Verify the menu translation. If it’s still in english, deactivate your theme and activate 2014 or 2015. The menu should be now in italian.

If it is the case, set site language to spanish and check the menu. Should be in spanish. If ok, reactivate your theme.

If the menu remains in english, contact the theme support.

bp-languages folder doesn’t exist in BP 2.x

If your WP use hungarian language, when you install BP, the BuddyPress translation comes automatically from translate-wordpress.org into wp-content/languages/plugins/, which contains also by default the askimet translation.

Also, php gettext use the compiled mo format to show a translation. The po file is only used to translate.

Much more about translation in this topic.

@numumar Sorry, something may be getting lost in translation. Could you please clarify what you mean?

@marketraisen,

the original code is %s posted an update
To modify this the right way, you have to use the language file and an appropriate compilator such as poEdit to generate the mo file.

Don’t know what solution you didn’t found, guess you have to search this forum for translation related topics.

A very dirty solution would be to use this snippet and add it to your child-theme functions.php

function marketraisen_change_bp_update_text( $translated, $original_text, $domain ) {
		
	if ( 'buddypress' !== $domain )  
	return $translated; 
	
	switch ( $original_text ) {
		case '%s posted an update':
		return '%s posted on';
				
		default:
		return $translated;
	}
}
add_filter( 'gettext', 'marketraisen_change_bp_update_text', 10, 3 );

danbp – You’re right. My technique will work, but would get overwritten when translations are automatically updated.

I just checked and WordPress saves automatic translations to /wp-content/languages/plugins/ so we should be safe if custom BP translation files are saved to /wp-content/languages/buddypress or /wp-content/languages.

WordPress might say that there is a new BuddyPress translation, but if you’re using the custom method, then you can ignore the notice as BuddyPress will keep using the custom translation file.

To tell WordPress to stop fetching automatic translations for BuddyPress, see:
https://buddypress.org/support/topic/disable-automatic-translation-updates/#post-234528

@r-a-y

guess you’re wrong !

Put your language file here:
/wp-content/languages/buddypress/
And you will not have to worry about upgrades removing your language file.

/wp-content/languages/buddypress/ is the directory where glotpress uploads the BP translation file.

– when the directory is empty ( a first install for example)
– when the mo file is old
– the file is also checked when you modify your site language

To test, make main site to english, throw an old BP .mo into that directory
Revert site language to fit this mo and you’re immediatly invited to update your translation.

The place to put a custom po/mo is /wp-content/languages/
buddypress.mo in this directory is not overwriten.

But it’s unclear to me (for the moment) if this directory is completly overwriten when WP updates ?
But i’m sure it was not the case in the past < BP 1.9/WP 3.9 😉

You have to merge your .pot file with the latest one located in /wp-content/plugins/buddypress/buddypress.pot.

Read the “Updating your custom language file” section of this codex article:

Customizing Labels, Messages, and URLs

—

For other plugins, placing your custom translations in /wp-content/plugins or /wp-content/languages/plugins/ should work.

Hi @kkradel

Sorry to hear you’re having problems with 2.2. How has it broken Featured Posts — can you explain what you’re seeing, and also what you expect to see?

Did you update any other plugins, translations, or core files at the same that you updated BuddyPress?

I guess something is not translated, but in this case, the email text should come in english.

If yo use an “old” translation from a previous version, it is possible that something is missing in your translation.

After checking both portugese version on GlotPress, (pt_PT and pt_BR) it appears that pt_PT is not translated for 2.1.x and to 38% for pt_PT in the dev version – the one actualy used by BP 2.1.1

https://translate.wordpress.org/projects/buddypress/dev

If you use an email plugin, ensure it is matching with WP’s mail action. Or if your theme has is own mail function, check that he uses the same wording as BP (and particulary the $s var) who fires the link.

Code in 2.1.1 looks like this

%1$s,\n
\n
\n
\n
Thanks for registering! To complete the activation of your account and blog, please click the following link:\n
\n
%2$s\n
\n
\n
\n
After you activate, you can visit your blog here:\n
\n
%3$s

Look the Codex up. There is a section on using custom stubs/ translations using .po and .mo files. That should do it.

The pot file doesn’t contain the translation, only the strings you can translate.

The translation is done in po (not pot) file and compiled to a mo file. buddypress-de_DE.mo is the file you have to use.

As you can see in the BP source (2.1),
$nav_name = sprintf( _x( 'Notifications <span class="%s">%s</span>', 'Profile screen nav', 'buddypress' ), esc_attr( $class ), number_format_i18n( $count ) );

This string in po. is outdated: Notifications <span class=\”count\”>%s</span>

You have to open your actual po file with poEdit (or similar translation tool) and update it with the pot file comming with latest BP version. (/buddypress/buddypress.pot)

Once updated the string to translate will be:
Notifications <span class=\"%s\">%s</span>
who should be translated to:
Benachrichtigung <span class=\"%s\">%s</span>

Be aware that poEdit uses different colors to indicate you the translated strings, the untranslated strings AND the fuzzy strings wich are approximative translation. These fuzzy strings must be double checked and validated or modified to work.

Example: difficult to see sometimes the subtle difference between “%s” and “count” when reading too fast ! 😉

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/