I just saw the bbPress translations being updated while updating to WordPress 3.9.1 which made me very happy. When I then updated a multi-site instance to 3.9.1 (with also bbPress activated in the network) there were no updates of the bbPress language files.
Any idea why I would have two different outcomes?
If you have a few minutes please fill out this survey about WordPress Contributor Experience
Your feedback will help. Spread the word and link to anyone who participates in making WordPress great and that includes all you fine i18n folk 🙂
We’ve been hammered with spam on the Dutch forum lately and that has resulted in a not so flattering tag cloud http://i.remk.us//ej/vzrof9qfscgkc.png
Recounting via the bbPress tool results in a internal server (500) error. Please advise sir @nacin 🙂
Hey @vanillalounge ,
Can you please deploy Rosetta Forum to the Dutch forums please? I know it’s not finished yet, but we’re working on that.
This is where GlotPress keeps weirding me out: http://cl.ly/0520243U2f0Q021B2006 Every single view shows there a no strings left to translate, but yet it keeps nagging me about 5 untranslated strings. Is this a cache issue or a bug @nacin?
We are finishing up the Dutch translation for Jetpack – finally – but we have one request. Currently an empty
jetpack-nl.po is added to the download where this should be
Is there something I can do to have this changed properly or … 😉
I noticed today that upgrading TwentyTen and TwentyEleven to their 1.3 version make said themes loose their translations if they previously had some. Any idea who to talk to about this and / or where. Perhaps you know @nacin ?
Is there a way, other than asking here, to update the po/mo on the nl.wordpress.org site to the latest 3.3 version? I want to make a new screenshot but it looks rather silly with New in the toolbar instead of Nieuw 😉
How can we have the translations updated on our xx.wordpress.org sites? I’d love to see the fruits of my labor in fy.wordpress.org and nl.wordpress.org. As long as we don’t have any language packs just yet, the only thing I can do is bug you @vanillalounge ?
When I look at the current NL Credits page I see myself and four other people as with Gravatar above ‘rest of the translators’. I assume that’s because somehow those usernames have validators or something, but none of them are (anymore). So please @vanillalounge please remove usernames edde, grizzler, mklijmij and basszje from the validator list and add afoka and rubenw to that list.
I’m the only one that is on that list and supposed to be. Could also because of something @nacin did not panning out perfectly though. Either way, the four mentioned above should be removed regardless.
Would you please add: defries, afoka and rubenwoudsma ( or rubenw, I’m not sure ) to the bbPress GlotPress project.
I’m guessing that with the release of the bbPress 2.0 beta plugin the translation will soon be added to translate.wordpress.org?
We talked earlier about updating the xx.wordpress.org sites to a more current WordPress version and a new theme. We were told that we needed to wait ’till 3.1 dropped and this is me checking in again 🙂
Anynews on this?
When I build a the new 3.1.1 version now and choose the following in Rosetta:
Locale branch: Tags/ 3.1.1
Project 3.1 and 3.1.x
WordPress Revision: HEAD
WordPress version: 3.1.1
I end up with a 3.1.2-alpha version which obviously is not what I should be getting. Is there a way to select to get the 3.1.1 tag from SVN?
If you want to build a proper 3.1 version now, there’s no way of doing so via GlotPress, at least not that I am aware of. Is it perhaps now time to create a 3.1 tag there instead of using the development tag (which is already at 3.2 bleeding alpha..) ?