BuddyPress.org

@micasuh _e( $text ) will search for the translation of $text and print it to screen. If a translation doesn’t exist, it’ll print $text. You might also come across __( $text ). This does the same but it returns instead of printing.

So yeah, these functions are definitely related to translating.

@micasuh the .mo file is most likely being loaded from your theme’s functions.php file. Alternatively, it may be loaded from a plugin. Or, maybe even bp-custom.php (if you have one of those).

Look for something such as the following and try removing it to see if it resolves the issue:

if ( file_exists( WP_LANG_DIR . '/buddypress-en_US.mo' ) ) {
    load_textdomain( 'buddypress', WP_LANG_DIR . '/buddypress-en_US.mo' );
}

If it doesn’t resolve the problem then we know your translation file is OK.

If you still believe the issue is a virus in your database then you could try rolling back. Do you keep database backups? But, to be honest, I’m more inclined to think this is occurring as a result of some rogue theme or plugin code.

Hi @rutzki,

are you responding to yourself ?
i dont find, where i have put in the german translation in the po file.
😀

If you use poEdit, you can create your own copy of de_DE.po directly from the source on your local buddypress copy.

The .po file header information necessary to get all translatable strings:

msgid ""
msgstr ""
"PO-Revision-Date: 2014-08-06 02:16+0100\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-Generator: Poedit 1.5.7\n"
"Project-Id-Version: BuddyPress 2.0.2\n"
"POT-Creation-Date: \n"
"Last-Translator: \n"
"Language-Team: \n"
"Language: de\n"
"X-Poedit-SourceCharset: UTF-8\n"
"X-Poedit-Basepath: .\n"
"X-Poedit-KeywordsList: __;_e;__ngettext:1,2;_n:1,2;__ngettext_noop:1,2;"
"_n_noop: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-Poedit-SearchPath-0: ..\n"

https://codex.buddypress.org/developer/translations/

Hi,

i have the same problem, that notification etc. is not translated and i dont find, where i have put in the german translation in the po file.

Can u upload your file, or copy and paste the few lines here?

cheers,
Patrick

@henrywright
Nothing in /wp-content/languages is touched during an upgrade just as a child theme also is not touched during a parent theme upgrade. Whomever conveyed using a language file is bad practice for translation is terribly misinformed. You are right by not agreeing Henry. The fact is this particular files directory has to be created by the admin in cpanel, ftp, or whatever they use for their server and is not replaced nor overwritten with core upgrades.

see here the answer from @shanebp.
He listed all notification instance in the po file

Maybe you have an idea what that could be?

You give the answer: once translated to German and once not.
Guess if something is not translated, you can’t see it. 😉

It could also to be that if you added the header infos to your po, that your translation plugin found immediatly some forgotten strings or new ones and added them, so you saw those unstranslated strings.

I suggest you to update the po file from the source using poEdit locally, for example from within bp-languages/buddypress-de_DE.po, to ensure that you have all 1476 strings of BP 2.0.2

Once done, you remove the po/mo from bp-languages and put them into wp-content/languages/plugins/

Hallo @findolfin,

Effectively, many peoples are claming about de_DE translation issue.

As the german translation for BuddyPress awaible on GlotPress is only translated to 52% (58% for 1.9!), the only other source to get po/mo files is deckerweb who provides 2 versions, Du and Sie version for BP 1.9 (latest in january 2014)

I downloaded the Sie version and opened the po. This file doesn’t contain any header information. So i guess gettext can’t read it correctly. And if you use this file it could be at the origin of your issue.

Here are the whole header informations, including the whole keywords list like _x which you need to add into your german buddypress-de_DE.po
Open the file with a text editor (notepad++ or similar) and paste it at the beginning of the file.

Once done, you must open the modified po with poEdit and save it again, to generate the mo file which is in fact the compiled format of the translation used by gettext.

msgid ""
msgstr ""
"PO-Revision-Date: 2014-08-08 09:45+0100\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-Generator: Poedit 1.5.7\n"
"Project-Id-Version: BuddyPress 2.0.2\n"
"POT-Creation-Date: \n"
"Last-Translator: \n"
"Language-Team: \n"
"Language: de\n"
"X-Poedit-SourceCharset: UTF-8\n"
"X-Poedit-Basepath: .\n"
"X-Poedit-KeywordsList: __;_e;__ngettext:1,2;_n:1,2;__ngettext_noop:1,2;"
"_n_noop: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-Poedit-SearchPath-0: ..\n"

Check this first and if it does not work, give feedback. And also theme name in case of. 😉

Please read here:

BuddyPress in Your Language

https://codex.buddypress.org/developer/translations/

Before installing any plugin, consider this translation into persian from the official translation repo for WP/BP/bbP
https://translate.wordpress.org/projects/buddypress/dev/fa/default

You can also contribute to this persian translation. Everithing to do so is explained on Goltpress.

Hi @noyzen,

if you only updated BuddyPress, it’s possible that the translation file contains an error.

Check your .po file for any strings looking like this one

https://buddypress.trac.wordpress.org/browser/tags/2.0.1/bp-languages/buddypress.pot#L3464

Example: Groups <span class=\"%s\">%s</span> or Members <span class=\"%s\">%s</span>
If correctly translated, perhaps is something wrong in your theme or child theme or even a plugin.
in this case, you should check the file indicated above the string to translate.
%s is very important to stay in the translation and in the original file to get the count

read:
https://buddypress.org/support/topic/translation-fails-only-at-sitewide-activity/

it’s not the theme
it’s not the translation
seems to be somthing unstable with bp-loader
sometimes i have things translated, sometimes not ! Stuning ! 👿

@shanebp,
forcing a translation is not the best solution, even if it is a solution.
Mine by hacking the core file is not better, as we loose it at the next update.
Your function won’t be loosed, but it should be used by caution, as gettext pass a second time on ALL strings. It’s not dramatical to force the translation for one string, but what will happen if someone use this trick for 20, 50 or more strings ? Performance trouble !

I’ll track this further before opening a ticket.

https://codex.wordpress.org/Plugin_API/Filter_Reference/gettext
https://codex.wordpress.org/Plugin_API/Filter_Reference/gettext_with_context