Also, the name of your file should be of the format bbpress-de_DE.mo not simply de_DE.mo

Actually that has changed now. If you download the file from http://translate.wordpress.org/projects/bbpress/plugin/ then it will have the correct name already, which would be in the format bbpress-plugin-de.mo

e.g. Polish, Romanian, French and Czech have 0% translation completed, but almost 100% strings in "waiting".

So how do we move strings from "waiting" to "translated"?

I see no everything is translated, so i guess I'll have to support with more translations.

Thanks!

Where can I activate the spanish version then?

Any help will be much appreciated.

use the "file" unix command to check the content of the .mo file. e.g.
$ file wp-content/languages/bbpress/bbpress-fr_FR.mo
GNU message catalog (little endian), revision 0, 732 messages

by using the default export, I was only retrieving one message, and thus nothing was translated...

I want to contribute ukrainian translation. But I don't see ukrainian language at http://translate.wordpress.org/projects/bbpress/plugin, and there is no possibility to add it.

How to add Ukrainian to the list of translations?

I just noticed that the "Docs" tab above has a different destination http://codex.bbpress.org/

On the page it says "you are welcome and invited to modify any of the pages you see here."

Question is - how? I don't see any "Edit" links on any of the pages...

Can someone please explain what it is and how it works in layman terms? Details are a bit sketchy at http://glotpress.trac.wordpress.org/

Will the translations be pulled live from a web service? Or will every update to the language push .mo .po files to the bbPress installation, and these files will continue to be stored locally? Or is it something entirely different?

Also, in what sort of timeframe/milestone is bbPress planning to make a switch to GlotPress automatic mechanism? I know that the translations are already available at http://translate.wordpress.org/projects/bbpress/plugin/

And about standalone package idea, I disagree with it since as part the wp plugin is the best reason I going to use it.

But I have to second the standalone package idea. That sounds like it would open up very interesting possibilities.

I can do some simple PHP, mostly without the classes/objects stuff (I'm currently in the process of learning PHP, so would really like some practical experience other than tweaking plugins).

I'm better with MySQL. I can devote perhaps 2 to 3 hours a day.

I'm located at the UTC+8 timezone (although I probably can't get up at 5 AM to attend the dev meeting).

Angela

https://core.trac.wordpress.org/ticket/19961

https://core.trac.wordpress.org/ticket/19958

http://bbpress.trac.wordpress.org/ticket/1737

http://bbpress.trac.wordpress.org/ticket/1738

http://bbpress.trac.wordpress.org/ticket/1739

http://bbpress.trac.wordpress.org/ticket/1740

http://bbpress.trac.wordpress.org/ticket/1741

http://bbpress.trac.wordpress.org/ticket/1742

http://bbpress.trac.wordpress.org/ticket/1743

http://bbpress.trac.wordpress.org/ticket/1744

http://bbpress.trac.wordpress.org/ticket/1745

http://bbpress.trac.wordpress.org/ticket/1746

http://bbpress.trac.wordpress.org/ticket/1747

http://bbpress.trac.wordpress.org/ticket/1748

http://bbpress.trac.wordpress.org/ticket/1749

http://bbpress.trac.wordpress.org/ticket/1750

http://bbpress.trac.wordpress.org/ticket/1751

Standalone bbPress

I appreciate the reason why you sought to create a standalone version of bbPress.

The plugin makes sense because it provides access to a large captive base of WordPress users. But on the other hand it ties bbpress down to WordPress, making it usable *only* with sites that use WordPress.

What if someone who doesn't use WordPress wants a forum software?

Well, I have a suggestion. bbPress should ONLY be developed as a WordPress plugin (as I believe it is now).

However, a standalone package should be available at bbpress.org. This would basically be a bundle of WordPress and bbpress, where bbpress is active by default.

Additionally, by default, the forum root would be selected as the static page that appears as home. You will need some help from your colleagues at WordPress for this...at the moment only pages (and not custom post types) are allowed to be selected as home. (update: https://core.trac.wordpress.org/ticket/19958 )

To sum up, it will still be WordPress with a bbPress plugin, but would be *sold* as forum software. The distinction being target market. bbPress plugin is targeted and marketed to people who use WordPress and are LOOKING for a forum software that integrates with it. The standalone package is targeted and marketed to people who are looking for forum software.

You might think this is a zany idea, and it probably is. It just might work, though.

However, bbPress is already a very good script. Some of my suggestions e.g. #1 #2 and #5 are almost completely non-technical and basically require some manual labor, which I am happy to provide.

I beg to differ with you on documentation. You are right that technical documentation, esp. for plugin developers etc would require an understanding of the codebase. However, I am talking about end-user documentation...in moving to bbPress, that is one of the hurdles I faced. I have also noted a pattern of big concerns of prospective and new users, both here and on WordPress.org

I think if the non-technical parts are dealt with, along with ONE technical part (migration), that would make an immense difference to the adoption of the software. And, of course, a significant number of users will generate interest among developers.

It's hard if you can't code, since the things you're mostly emphasizing are things that need to be coded, or documentation that requires understanding the code base. It's one of those times where there's no shortage of opinions and ideas, but there's a huge shortage of labor.