It was a slow week for GlotPress.
The only changes were language variants standardizations and plural forms fixes, contributed by Zé. All variants language names are now in the form Main language (Region). Example: Spanish (Chile).
Monthly Archives: February 2010
The GlotPress Report #1 (Feb 5 – Feb 18 2010)
Before diving into specific features and bug-fixes, this week’s news it that translate.wordpress.org was launched. It is a GlotPress install, which allows all WordPress translators to collaborate and will host the translations of all the projects in the family like bbPress and BuddyPress.
- In [407] – [410] we added proof-of-concept JSON API for the translations page. Just prepend
/apiin front of the URL. For example/projects/wp/dev/de/defaultgets you the HTML page for German translations and/api/projects/wp/dev/de/defaultwill return the same information, but in JSON. - Since [411] and [412] GlotPress can be installed in a directory different from the user-facing GlotPress URL. The purpose of that is mainly to have it as an svn external.
- In [419] – [421] project pages got visual fixes: description is now shown, the text for no translations isn’t show if there are sub-projects.
- [422] fixed a serious bug, which prevented users with approval access to discard warnings.
The GlotPress Report #0 (Jan 29 – Feb 5 2010)
Here is the zeroth edition of the GlotPress report. This series of posts will give you an overview of what happened with GlotPress in the last week.
- In [401] we added a button to fill-in the current translation field via Google Translate:
- In [404] we added bulk translation via Google Translate. It affects only strings without translation and if the translation was successful sets their status to
fuzzy. - In [404] we simplified the bulk menu: no more radio buttons for both approve and reject. Now there are two separate buttons:
GlotPress 