Through the previous days, several small to big changes happened on localize.drupal.org, so I thought it would be a good idea to write a quick post summarizing the changes.

Localize.drupal.org opened up

Localize.drupal.org opened up to anonymous visitors! This means people can visit the front page and all overview and group pages, check out project translation stats, localization source code parsing warnings and so on. This lets you subscribe to a feed of your translation team posts or check out your module's translation status without even being logged in. (Contributing will always require an account and we are working on supporting translating pulling from localize.drupal.org via static file dumps). Work is ongoing to cross-link drupal.org projects with localize.drupal.org translation pages, see: http://drupal.org/node/591840

Wiki pages added, more formatting allowed

Due to popular request to manage local documentation for translation teams, a wiki page content type was added. The main difference to stories is that anyone can edit wikipages anytime. There is also a new "Rich HTML" markup option which adds support for tables and headers for longer and more data intensive documents. This will help some teams previously documenting their dictionaries / word lists via simple pages outside localize.drupal.org. Discussion is ongoing at http://localize.drupal.org/node/162 to formulate a requirements list for a more intelligent wordlist/dictionary feature.

Bugfixes rolled out for duplicates and empty data in UI entry, imports and remote submission

The localization server package got fixes to treat empty string submissions and duplicates the same way regardless of the input mechanism. Duplicates are now checked with the right leading and trailing whitespace applied from the source string and translations or suggestions are only saved if they are not among the active suggestions or not equal to the active translation of a string. This should help reviewers to avoid having to review the same suggestion from multiple people and should help us maintain the server, since it avoid some extraneous data entry. This was in part result of the investigations we are doing to figure out the somewhat mysterious 503 errors on .po file imports. Part of the reason for the slow-going team approval is that the more active you are at importing your previous translations on team creation, the more errors you face. We are on it. More info at http://drupal.org/node/581512

Better error messages for remote submissions

A few people attempted to use localization client with localize.drupal.org. We've got multiple reports of the strings not getting through and in all cases, it turns out it was a client configuration problem. You need to set up localization sharing globally at the Administration » Site configuration » Languages (in Drupal 6), but that is not enough in itself. To be able to track credit on the submitted string, you also need to set up your own API key. Go to your client site's My account page and find your personal API key request link there. Copy over your personal API key and then start using remote string submission. To help avoid bad configurations, the server now gives more detailed error messages trying to point clients to the missing configuration steps when possible.

Comments

It would be nice if group admins could sticky wikis to the group frontpage. That way a group can use one of these as reference for the translations team, for visitors of that particular language, etc.

How would you set that up (without hopefully adding 3 more modules and without giving everybody node admin rights :)?

This may be a stupid question, but how do I add a wiki page to the Danish group (node/add only has an entry for the story content type)?

...but it seems it is now gone. :-o

The team sidebar should have "Create Story" and "Create Wiki page" listed. There are a few wiki pages already, so this seems to have been working for others.

For example, I was able to create a wiki page, the option to do so was available in the team sidebar.

But now, I cannot see the option in the team sidebar, and if I try using the URL node/add/wiki?gids[]=xx, I get access denied error.

Right, I found the error and fixed (the content type was renamed since then and the permissions were not updated, erm). Should work from now. Sorry for the issue.

Thanks! :)