If you’re using a standard installation afaik you don’t have to do anything with the bbpress file. Have a look at the translations page on this website (under Codex) and see what other people have done.
5402929Inactive
Looking forward to help on the language’s. I’ve got buddypress translated to dutch and that works fine. After that I activated bbpress but cannot figure out where the language files for bbpress go ?
bb-config says: * bbPress Localized Language, defaults to English.
*
* Change this to localize bbPress. A corresponding MO file for the chosen
* language must be installed to a directory called “my-languages” in the root
* directory of bbPress. For example, install de.mo to “my-languages” and set
* BB_LANG to ‘de’ to enable German language support.
*/
define( ‘BB_LANG’, ‘nl_NL’ );
Where is the root directory of bbPress when one installed it with the one-click install from within buddypress ? e.g. where does the .mo file go ?
Got it working, hacked bp-core.php and made it a static link (to the .mo file).
In continuation of this, I ran into a fatal error on the buddypress settings page in the admin area.
Fatal error: Call to undefined function bp_core_get_buddypress_themes() in /customers/xevodesign.nl/xevodesign.nl/httpd.www/talkmore/wp-content/plugins/buddypress/bp-core/bp-core-admin.php on line 105
Edit: Nevermind, using “define ( ‘BP_IGNORE_DEPRECATED’, true );” in your wp-config isn’t allowed apparently..
Check your messages, I figured it out.. but it wasn’t easy… I think we should write a new tutorial of how to translate for BP because information about this is quite hard to find and not well documented.. I’ll try to write a quick tutorial for this soon 
Just tagged version 0.1.3
* Fixed bug where Comments was not showing up in link list nav bar
* Many l10n fixes, big props to Chouf1
* Added support to control voting behavior with config constants and filters
* Added Spanish translations, props to laloma
* Improved Fotoglif support due to changes to their API
need help to support these, DJPaul ?!… i’m available… and i will provide a translation in the next days for french language too… would be good if you provide a .pot … thanks!
Haha this is weird.. I was trying to help you solve the problem and googled for the line:
missing `msgstr[]’ section
Came across this post.. I’m glad you found it, because I was about to give up.. Now when I select the language in WPMU it does not seem to work..
Found the buggy lines, kind of weird because poEdit said that I was done translating. Anyway, edited them and now I can easily open it.
Now just finding out why buddypress doesnt copy the wpmu language setting.
These kinds of errors can also be caused by forgetting the variables (%s, %d, %1$s, etc…)
If the original string has those, the translated string must have them also. The numbers in the error messages are which lines in the po file contain the errors. Open the .po in something that has line numbers and see what’s broken in them.
Xevo, it is written: missing `msgstr[]’ and found 9 fatal errors
This means that you forgot to translate 9 strings ! The lines are indicated in the warning.
Sometimes strings have plural form and you did’nt see that beacause the poEdit window is too small by default on his bottom frame…
To be sure, open the po file in a text editor, it’s easier to read and to search the lines (poEdit did’nt search lines). When found the errors, do the correction and save. Open in poEdit and save also to generate a new mo file.
If you need a dutch translation MrMaz just send me the translation file and I’ll be happy to translate it for you!
french version is avaible here
Some files have been modified to allow translation and the .pot file is also a bit modified (due to missing strings at this time) from the original file in 0.1.1
@21cdb:
Thanks for the kind words!
There is another developer, GIGALinux, from #buddypress-dev that is working on a German translation already! Maybe you can contact him and work on it together?
Also a word of caution that this plugin is still in heavy development, so please don’t put your reputation on the line with it yet! I do plan to create different branches if development could introduce instability or backwards compatibility issues, so you are probably safe from a theming standpoint.
If you find any layout or CSS issues while theming, please let me know so we can make improvements!
Translation is actually not working with your locale function “bp_links_load_textdomain()” in bp-links.php line 138
Instead of the function, a simple if statement is enough and works
if ( file_exists( WP_PLUGIN_DIR . '/buddypress-links/languages/buddypress-links-' . get_locale() . '.mo' ) )
load_textdomain( 'buddypress-links', WP_PLUGIN_DIR . '/buddypress-links/languages/buddypress-links-' . get_locale() . '.mo' );
If you wanna translate:
Erase (or comment) the function and use the code above instead
Name your .mo file buddypress-links-xx_XX.mo (xX are your country code)
Hi, if you send me (arjdan@gmail.com) the pot file I’ll make italian translation for your link plugin.
Thanks
Daniele
JJJ,
I read your post about i18n, and followed it to the letter Thank you for saving me the leg work.
Every string is already in the text domain ‘buddypress-links’ (great minds think alike). I guess it must be up to the translators to use their translation tools in a way that avoids duplicate work, because it seems like a tall order for a plugin developer to monitor which strings are duplicates and constantly add and remove strings from their custom domain as the parent plugin changes (in this case BuddyPress and WordPress).
I really need to read up on this, lol.
-M
MrMaz, if you need help getting your plugin i18n friendly, let me know, I’m happy to kick through the code and clean it up.
Basically just make sure all of your text uses a textdomain like “bp-links” or “buddypress-links” then use a program like po-edit to comb through the source folder and it will sniff the strings and compile them into the po/mo/pot file.
Textdomains are important because if you use “buddypress” for your textdomain, and the buddypress-en_US.po/mo file doesn’t have a translation for it, it won’t get translated. It’s important to use your own. The only reason NOT to use your own is if the string matches EXACTLY the BuddyPress or WordPress strings already.
@Chouf1:
I am happy that you are interested in helping with the translation of BuddyPress Links. I am new to i18n and I want to make sure I am doing it right.
I have a .pot file, but many of the strings are the same as the ‘buddypress’ text domain. Is there a way to avoid this when generating the .pot file, or do the translation tools automatically ignore these overlapping strings?
I would like to send you the .pot file so you can go over it and give feedback, what is the best way to get you the file?
Hi, great work !
Is it possible that you provide a .pot file for further translation work ?
Found out how it works in poEdit, this’ll make my job easier.
Instead of the full 100%, I only have to do about 30% translation.
If you need any help translating let me know, I’ll be glad to help I also have no idea how the translation stuff works, but that shouldnt be so hard?!
It has both his po and mo, so what do I do now? I’m new to translating. And since I’m also planning on translating both bbpress and wpmu. I’m eager to learn.
And btw, I also use Poedit.
@xevo
If the dutch language pack comes with both po’s and mo’s, then you can rescan the buddypress directory with poedit, update the database from the source, and then proceed with your changes.
If not, then you’re sort-of out of luck I think. I haven’t found a tool to merge an existing mo into a new po, so it would be a manual process of copy and pasting each preexisting translation.
