We’re in hard string freeze for 4.6 – Prepare your locales for the the release

Dear Polyglots,

A little while back the WordPress 4.6 hard string freeze was announced and that means no stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. will change anymore before August 16th, when WordPress 4.6 will be released.

That means there are two things for all GTEs to do now:

1. Translate the 4.6 project, Admin, Network admin and Continent & cities

The release will hit on Tuesday, August 16th. It’s time to head to translate.wordpress.org and finish translating the last batch of new strings.

Please don’t forget that in order to qualify for an automatic release, you need to have all strings in the following projects translated 100%:

• WordPress
• WordPress Administration
• WordPress Network admin
• Continents and cities

2. Prepare the SVN directory for your locale for automated packages

Handbook page for reference: Automated release packages

Does my localeLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ qualify for automated release?

• If all you have is a license, readme, and wp-config-sample.php (or no custom changes at all), everything will be automated for you if you follow the instructions above. Both language packs and release packages will automatically be created. If you are not at 100% at that time, then language packs and release packages will be created when you reach 100%. If you are later modify a translation (to fix a typo, for example), your language pack and release packageRelease package A release package is a packaged version of WordPress. That is, a ZIP file consisting of WordPress in its entirety, along with PO and MO files for core, the PO and MO files of default themes and Akismet, and any custom changes a locale has. In the past, most locales built their release package using the form in Rosetta’s dashboard. will be regenerated.
• If you have extensive custom changes, you will need to manually create a package via RosettaRosetta The code name of the theme for the local WordPress sites (eg. bg.wordpress.org is a “Rosetta” site). All locale specific WordPress sites are referred to as “Rosetta sites.” The name was inspired from the ancient Rosetta Stone, which contained more or less the same text in three different languages. as you have done in the past.

On Slack, watch out for messages like this one:

Your locale is good to go if you see your locale in the “x release packages for y were built” message.

This is a global pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” for all General Translation EditorsTranslation Editor Translation editors can approve translations for projects. The GTE (General Translation Editor) and LM (Locale Manager) roles can add new users with the "Project Translation Editor" role that can approve translations for specific projects. There are two different Translation Editor roles: General Translation Editor and Project Translation Editor whose localesLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ are more than 50% and less than 100% translated:

18 locales are already at 100%, well done and thank you!

• #hr
• #en_AU
• #en_CA
• #en_NZ
• #en_GB
• #eo
• #fr_FR
• #de_DE
• #hi_IN
• #id_ID
• #it_IT
• #ja
• #ko_KR
• #mr
• #nb_NO
• #pt_BR
• #sl_SI
• #sv_SE

Dev between 95% and 100% (35)

• #sq – @besnik
• #eu – @elurnet, @hey_neken, @ikusimakusi, @erralin, @murgilduta, @unaizc
• #bn_BD – @wzislam, @badsha_eee, @tareq1988
• #bg_BG – @tyxla, @petya, @kldn, @vloo
• #ca – @cubells, @domenec, @dverger, @hervada, @marcqueralt, @mgrau226, @msoravil, @nuria_trad, @txanny, @xavivars
• #da_DK – @georgwp, @intoxstudio, @culturemark, @tohevi
• #nl_NL – @chantalc, @imazed, @mbootsman, @mpol, @defries, @rubenw, @tacoverdo
• #et – @erkoristhein, @uncleowl, @mstannu, @petskratt, @ragulka
• #fi – @arhipaiva, @daniel-koskinen, @arkimedia
• #fr_BE – @casiepa, @pauldewouters
• #fr_CA – @fgienr, @jsmoriss, @martinbouillaud, @mialevesque, @choumich, @rhialto
• #ka_GE – @dimitrigog
• #el – @dyrer, @kosvrouvas
• #he_IL – @ramiy, @yoavf
• #hu_HU – @csurga, @djzone, @fgywp, @wphuorg, @tojgli
• #is_IS – @birgire, @egill, @samueljon, @valurthor
• #lt_LT – @ideag, @jonasltu, @pokeraitis
• #ms_MY – @webgrrrl, @mohdrafie, @zeo, @tarmiziaffandi
• #oci – @cedric3131
• #pl_PL – @eclare, @iworks, @waclawjacek
• #pt_PT – @alvarogois, @goblindegook, @nbar, @pedromendonca, @vanillalounge
• #ro_RO – @adrianpop, @deconf, @jnhghy
• #ru_RU – @atrax, @jenia, @sergeybiryukov
• #sr_RS – @dimadin, @lanche86
• #sk_SK – @angeloverona, @johnnypea, @savione
• #es_AR – @andrezrv, @battaglr, @eliorivero, @fgilio, @gustavodc, @juanfra, @kilinkis, @nicosantos, @ricardoaiello
• #es_CL – @bredebs, @ejner69
• #es_GT – @wowdevshop, @xicoofficial
• #es_ES – @balfer, @fernandot, @koke, @jconti, @luisrull, @bi0xid, @_dorsvenabili
• #es_VE – @jordicuevas, @dragondeluz
• #tr_TR – @wordpress-tr
• #ug_CN – @alim-ahat, @moorshidi, @sepra
• #uk – @kovshenin, @romanbon, @webbistro, @zanatoly
• #vi – @htdat, @huynetbase, @thachpham92, @philiparthurmoore, @tonybui-1, @rilwis, @tucq
• #cy – @carlmorris, @gruffprys, @gwgan

Dev between 90% and 95% (15)

• #ar – @alex-ye, @rasheed
• #az – @muhsinmushviq
• #bs_BA – @kenan3008
• #zh_CN – @jiehanzheng, @jimmyxu
• #zh_TW – @bibi-wang, @sandwich1168, @carrielis, @s9011514, @esofthard, @pseric
• #en_ZA – @hlashbrooke, @brandbrilliance
• #gl_ES – @egalego
• #de_CH – @aliyanage, @swissky, @openstream, @swissspidy, @grapplerulrich
• #mk_MK – @server986, @kuzmanov, @chombium, @gocemitevski, @jjanev86, @l10n
• #ary – @sa3idho
• #nn_NO – @chriscena, @meinmycell, @hgmb, @peterhoob
• #fa_IR – @gonahkar, @mani_monaj
• #es_MX – @hiwhatsup, @marcozink
• #es_PE – @reyson
• #th – @dussarong, @kazama, @mennstudio

Dev between 50% and 90% (29)

• #af – @ggericke, @henkvorster, @hugmin42, @jbrink, @kobusb, @kokkieh, @plusplugins, @semblance_er, @snapalot, @festaans
• #hy – @aaleksanyants, @progmastery
• #ceb – @undefinedmj
• #cs_CZ – @neoen, @pavelevap
• #gu – @bisag, @chandrapatel, @healing-tomato, @kirtan95, @krupajnanda, @mehulkaklotar, @sanketparmar, @shahpranaf
• #haz – @tohave
• #ga – @brianrourkeboll, @maccoisdealbha
• #kab – @yacine2953
• #km – @so_vichet
• #ckb – @asos99, @sia-neriman
• #lo – @douangtavanh
• #lv – @grivitis, @p0stman, @mikslatvis, @orvils, @rolandinsh
• #ml_IN – @abhilashenair, @harishanker, @jagadees, @jayeshsan, @manojkmohan, @mbigul, @nejwrks, @nitkr
• #mn – @gansukh, @uranbold
• #me_ME – @aidvu, @vaera
• #my_MM – @minnkyaw, @herzcthu
• #ne_NP – @nhuja, @rabmalin
• #ps – @sajadsafi, @msadat
• #pa_IN – @kuldeepsidhu88, @pikasingh
• #rhg – @haroonyousuf
• #gd – @akerbeltzalba, @alasdairmaccaluim
• #si_LK – @anandawardhana, @bckurera, @chevindu, @malinthe, @mohanjith
• #azb – @tohave
• #tl – @krzheiyah, @kel-dc
• #ta_LK – @bagerathan
• #te – @veeven
• #ur – @techwhiz, @codemovementpk, @sajidzaman
• #uz_UZ – @ulugov, @avazbek, @azamat88, @mashrab

Thank you to everyone who’s already helping bring WordPress to more than 100 languages worldwide.

We’re not allowed to be biased but this release is really special because we’ve got this guy leading it. Let’s make him proud and break a new record releasing on Tuesday, Aug 16th, with 60+ locales. I know we can do it.

Happy translating ❤️

Petya

#announcement