You can review how GlotPress works here: http://en.support.wordpress.com/glotpress/

Please also refer to the Polish terminology guide for consistency with previous translations: http://codex.wordpress.org/pl:Konwencje_przyj%C4%99te_w_polskim_t%C5%82umaczeniu_WordPressa

It was compiled by the current Polish validator (waclawjacek), who I believe will be reaching out to you directly.

Thanks for contributing and let me know if you have any more questions!

This lead to me wondering, perhaps there no active Polish validators, then?

Correct, the current Polish validator seems to be inactive. I reached out to him to get a status update and will let you know once I hear back. We can always try to get another validator (can be more than one), so that the translation project does not stagnate.

You can get started here: http://translate.wordpress.com/projects/wpcom/as/default

(wp.org translations import is a good place to start)

There are over 1 400 strings translated as of today but they are all somehow stuck in a queue, waiting to be approved. As far as I understand – please, bear with me, I have only discovered GlotPress yesterday – new translations are only implemented if there is a group of at least 200 validated, warning-free strings. This lead to me wondering, perhaps there no active Polish validators, then? It is not like the phrase I wanted to translate needs to implemented right away, I just got a bit worried about all that volunteer work going to waste.

Perhaps someone could explain the situation to me or maybe this post will just bring someone's attention to the matter :-)

When translating WordPress.com, it is best to translate strings in the order of priority. High priority strings are those that are associated with the new features or more visible elements of the interface, low priority strings are less visible/important, and hidden strings are generally not shown to regular WordPress.com users.

Hidden strings, however, are included in .po export files (it would be ideal to exclude them from export, but right now we don't have a way to do that automatically). Normally they are placed in the end of the file. So if you are a validator using an external tool like Poedit and then re-importing , make sure that you are translating the strings from the beginning of the file, rather than the end. We all want your translations to be visible and useful for as many users as possible!

I recently noticed a high number of hidden/low-priority strings for the following languages: Swedish, Thai, Turkish. Something to keep in mind, so that you spend your translation time most effectively.

As usual, thank you very much for your time and help translating, and if you have any questions or suggestions about GlotPress, string context, or translation best practices, don't hesitate to share them in this forum.

It looks like the current Romanian validator was no longer active, so I removed them and gave you the validator permissions. There are quite a few strings pending approval, so maybe better translations have already been suggested there.

There is a lot of relevant information about the translation process in this support article, and we also encourage you to get in touch with the Romanian WordPress.org team (you might want to kick things off by importing their latest translation).

Read also > http://en.blog.wordpress.com/2011/04/13/security/

As you know, WordPress.com is translated using the GlotPress platform. In order to keep spam out of the translations, and also to keep them correct and coherent, all strings suggested by users need to be validated before being shown live.

However, of all the languages that WordPress.com supports, a few have no validators at all, which means that users suggest strings that are never shown live, and that makes us sad.

This is thus a plea for all those who speak one (or several) of the languages below, or know someone who does (or know someone who knows someone...;) ), to consider applying for validator permissions for your language, by creating a topic on this very translations forum. What it entails is explained here:

http://en.forums.wordpress.com/topic/on-validator-profiles-in-the-translation-platform-1

And here are the languages which have no validators:

• Assamese
• Asturian
• Belarusian
• Bulgarian
• Catalan
• Catalan (Balear)
• Estonian
• French (Canada) - ok :)
• Georgian
• Icelandic
• Kannada
• Latvian
• Lithuanian
• Malayam
• Marathi
• Mirandese
• Mongolian - ok :)
• Nepali
• Occitan
• Pashto
• Punjabi
• Sinhala
• Slovak - ok :)
• Slovenian
• Tagalog
• Telugu - ok :)
• Ukrainian
• Vietnamese - ok :)
• Yiddish

Finally, a few notes:

• If you do want to become a validator, we strongly recommend that you get in touch with the WordPress.org translators for your language. If you have no success in contacting them, drop us a line on the WordPress.org Polyglots blog.
• I'll be publishing a similar post here, for the languages which haven't been validated in a very long time, or which have a large number of strings pending validation.
• This sticky post is closed to comments on purpose, to encourage you to start a new topic for your language.

(As a side note, if you want to get in touch with the wordpress.org translators, you might want to check http://codex.wordpress.org/WordPress_in_Your_Language#Galician_-_Galego_.28gl_ES.29)

What is a validator?

The translation platform is open for any wordpress.com user to suggest a new translation. When they do, that leaves those strings with a status of "suggested". In order to transform them into "approved" strings (which are the only ones that get deployed), a validator needs to accept (or reject) those suggestions.

In addition to these permissions, a validator can also upload external files (typically, but not only, the .org translations) and discard warnings.

A string translated by a validator is automatically approved (but will still generate all applicable warnings)

[/update]

Requesting access

A few words on requesting a "validator" profile for your language, on http://translate.wordpress.com:

There is no technical limit on how many users can be validators, however, translation communities should only have a couple of validators so that we can keep track of who to talk to should the need arise. I suggest that you work it out among each other who the two or three should be who can validate, and have all others who want to collaborate organized in these forums. Feel free to create a new thread for your locale, but try to use English as the language for discussion as the items you debate might be relevant to others.

I would also like to strongly encourage all translators (particularly validators) to get in touch with their respective .org translation community, so that consistency can be maintained across versions.

(adapted from http://lists.automattic.com/pipermail/wp-polyglots/2009-October/003706.html )