I’ve a couple of doubts:
In Aragonese team, we have completed and validated the core strings: translate.wordpress.org/projects/wp/dev/an/ , continents & cities as well as 2010, 2011 and 2012 themes… (admin, and network/admin will arrive later). Does it makes sense to import them into ver 3.3 (especially if most strings were common) to try and have a 3.3 package?
I’ve also come across this glotpress instance at wordpress.com where one can translate “wordpress.com” http://translate.wordpress.com/projects/wpcom . I understand we’re localizing the software at wordpress.org, and in wordpress.com one translates the strings of the “website” wordpress.com , so that one can access wordpress.com through the interface in one’s language. Am I right? But still I wonder if wordpress.com allows to use all available languages, or it is necessary to have wp.com translated into one language before users can use it in their blogs hosted in wp.com.
juanpabl76 are discussing. 
juanpabl76 4:26 pm on March 11, 2012 Permalink |
I found a clarification on my second question on: http://en.support.wordpress.com/translation-faq/ .
Zé 10:35 am on March 15, 2012 Permalink |
It only makes sense if you plan on releasing a 3.3.x package (3.4 isn’t scheduled for right now, and there’s always the possibility of 3.3.2, etc.). That said, the import process should take care of almost all strings automatically.