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

Dear Polyglots,

The last strings for 4.8.1 have been imported to the development project and that means no strings will change anymore before Tuesday, August 1st, the expected release date for WordPress 4.8.1.

If your locale is not yet at 100%, it means there are still some things to do for you as GTE:

  1. Please check the WordPress 4.8.1 status and translate or approve the remaining strings. To qualify for an automatic release, you need to have all strings translated.
  2. (If needed) Prepare the SVN directory for your locale for automated packages.

If you have any questions, you can find us of course on Slack.


This is also a global ping for GTEs for locales that are currently at more than 50% and less than 100%.
Currently 22 locales at 100%, congratulations and thank you !

Dev between 95% and 100% (50)

#sq@besnik
#ar@alex-ye, @rasheed
#eu@elurnet, @hey_neken, @ikusimakusi, @erralin, @murgilduta, @sergixnet, @unaizc
#bel@agfare
#bg_BG@tyxla, @nofearinc, @nbachiyski, @petya, @silvinafurnadzhieva, @kldn, @vloo
#zh_CN@jiehanzheng, @jimmyxu
#zh_TW@mrmu, @bibi-wang, @sandwich1168, @carrielis, @s9011514, @esofthard, @iamafu, @kaiconan, @pseric
#hr@yuraz, @mirta, @vipteam
#da_DK@ellegaarddk, @georgwp, @intoxstudio, @koesterandersen, @culturemark, @thomasdk81, @tohevi
#en_NZ@jjripikoi, @wealthy, @ryanhellyer, @tareiking, @toherangi, @webaware
#en_ZA@andrewza, @hlashbrooke, @nickduncan, @seags, @travislima
#et@erkoristhein, @uncleowl, @mstannu, @petskratt, @priiduonu, @ragulka, @ristoniinemets
#fi@arhipaiva, @daniel-koskinen, @arkimedia, @teemusuoranta
#fr_CA@fgienr, @jsmoriss, @martinbouillaud, @mialevesque, @choumich, @rhialto
#ka_GE@dimitrigog
#el@dyrer, @kosvrouvas
#gu@afzalmultani, @chandrapatel, @dipeshkakadiya, @krupajnanda, @mehulkaklotar, @pranalipatel, @sanjaydabhoya, @sanketparmar, @shahpranaf, @ashokrane
#he_IL@ramiy, @yoavf
#hi_IN@ankit-k-gupta, @gagan0123, @gyan, @hardeepasrani, @juhise, @monikarao, @rahul286, @rajeevbhandari, @saurabhshukla, @1anand
#hu_HU@balcsida, @csurga, @djzone, @fgywp, @wphuorg, @tojgli
#is_IS@birgire, @egill, @gudmundur, @valurthor
#id_ID@sofyand, @ekajogja, @hudatoriq, @ivankristianto, @johanbun, @qzoners, @tfirdaus
#ja@extendwings, @tai, @nao, @odysseygate, @tenpura, @takayukister
#kab@yacine2953
#ko_KR@chris_dev, @drssay, @martian36
#lv@armandsdz, @capsx, @edzuss99, @elvisandersons, @grivitis, @p0stman, @karlismaj, @karlisupitis, @kskaredovs, @maris-o, @mikslatvis, @orvils, @peteris, @rmkapins, @timlatvia, @rolandinsh, @unigunde, @veisis, @webhaus
#lt_LT@ideag, @jonasltu, @pokeraitis
#mk_MK@kuzmanov, @chombium, @gocemitevski
#ms_MY@webgrrrl, @mohdrafie, @zeo, @tarmiziaffandi
#mr@fitehal, @mkrndmane, @rahul286, @codexdemon, @patilswapnilv
#ary@sa3idho
#ne_NP@rabmalin, @shivashankerbhatta, @meissudeep
#nb_NO@bjornjohansen, @peterhoob
#nn_NO@chriscena, @meinmycell, @hgmb, @peterhoob
#fa_IR@gonahkar, @mani_monaj
#pl_PL@aleksanderkuczek, @eclare, @iworks, @szymon-skulimowski, @waclawjacek
#ro_RO@adrianpop, @deconf, @dancaragea, @jnhghy
#sr_RS@dimadin, @lanche86
#sk_SK@kavoros, @savione, @xkatka
#sl_SI@hekos
#es_CO@andrescifuentesr, @leoland, @yvallejo
#es_GT@xicoofficial, @wowdevshop
#es_MX@hiwhatsup, @marcozink
#es_VE@jordicuevas, @dragondeluz
#th@dussarong, @kazama, @mennstudio
#tr_TR@wordpress-tr, @m_uysl, @selmankandeniz, @trkr
#uk@romanbon, @sergeykovalets
#ur@mrahmadawais, @hibashaikhpk, @farhandanish1, @sajidzaman, @saqibameen
#uz_UZ@ulugov, @azamat88
#cy@carlmorris, @gruffprys, @gwgan

Dev between 90% and 95% (2)

#bn_BD@wzislam, @badsha_eee, @tareq1988
#oci@cedric3131

Dev between 50% and 90% (30)

#hy@aaleksanyants, @progmastery
#az@muhsinmushviq
#bs_BA@kenan3008
#ceb@undefinedmj
#cs_CZ@kalich5, @neoen, @pavelevap, @mobby2561
#haz@tohave
#kk@iakkz, @kaznet, @uki2017
#km@so_vichet, @vannkorn
#ckb@sia-neriman
#lo@defagoart, @douangtavanh
#ml_IN@abhilashenair, @mbigul, @harishanker, @jagadees, @jayeshsan, @manojkmohan, @nejwrks, @nitkr
#mn@gansukh, @uranbold
#my_MM@dennismaang, @minnkyaw, @herzcthu
#ps@sajadsafi, @msadat
#pa_IN@kuldeepsidhu88, @pikasingh
#sah@bacr, @halantul
#gd@akerbeltzalba, @alasdairmaccaluim, @macmhicheil
#szl@gkkulik
#si_LK@anandawardhana, @bckurera, @chevindu, @dazunj, @himasha, @malinthe, @mohanjith
#azb@tohave
#es_CL@bredebs, @ejner69
#es_PE@reyson
#sw@mrfroasty
#tl@carl-alberto, @krzheiyah, @kel-dc
#ta_IN@arunprakash, @farookibrahim, @hareesh-pillai, @imanickam, @menakas, @simplysaru, @varunms, @venkatsr
#ta_LK@bagerathan
#tt_RU@qdinar
#te@veeven
#bo@bhod, @krishnann, @sonamdawa, @tenim, @tibetanitech, @wpwalker, @zangkar-tsultrim, @bumpagyal
#ug_CN@alim-ahat, @moorshidi, @sepra

The release is due on Tuesday, August 1st, which makes this a little bit of a short notice so thank you in advance to everyone who makes time to get their locale to 100%.

Happy translating <3

Pascal.

#announcement #hard-freeze #wordpress-4-8-1

Hello Polyglots, I am the…

Hello Polyglots, I am the plugin author for PantherMedia Stock Photo (https://wordpress.org/plugins/panthermedia-stock-photo/).
The following user is our main-translator for our plugin and coordinator of external translators. Please give him the rights to set our plugin translation in all translations.

We need:

This languages are part of our website language and we will use them in also in future.

If you have any questions, just comment here. Thank you!

#editor-requests

Per-locale Slack channels

Not sure if this has been discussed already, but what would you guys say about per-locale Slack channels on the Making WordPress Slack? Such as #polyglots-pl_PL?

Hi everybody, could someone please…

Hi everybody, could someone please add @jacekws as translation editor for Hestia theme for language #pl_PL.

There are some strings pending already: https://translate.wordpress.org/locale/pl/default/wp-themes/hestia

#pl_PL@jacekws (@waclawjacek)
Thanks.

#editor-requests

Hello Polyglots, I translated Social…

Hello Polyglots, I translated Social Warfare into polish.
Need editor to check it 🙂
@gwin could you verify my translation?
#pl_PL

#editor-requests

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

Dear Polyglots,

The last strings for 4.7 (the about page strings) have been imported to the development project and that means no strings will change anymore before Tuesday, December 6th, the expected release date for WordPress 4.7.

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

1. Translate the 4.7 project, Admin and Network admin

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%:

There is also a new default theme that comes with 4.7 – Twenty Seventeen which can also use some of your time.

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

Handbook page for reference: Automated release packages

Does my locale 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 later modify a translation (to fix a typo, for example), your language pack and release package will be regenerated.
  • If you have extensive custom changes, you will need to manually create a package via Rosetta as you have done in the past.

On Slack, watch out for messages like this one:

translation-bot

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


This is also a global ping for GTEs for locales that are currently at more than 50% and less than 100%.

4 locales are already at 100% – thank you!

Dev between 95% and 100% (15)

Dev between 90% and 95% (14)

Dev between 50% and 90% (51)

The release is due on Tuesday, which makes this a little bit of a short notice so thank you in advance to everyone who makes time to get their locale to 100%.

Happy translating <3

Petya

#announcement

#hard-freeze, #wordpress-4-7

WordPress 4.7 is in soft string freeze

Hello everyone,

WordPress 4.7 RC1 was announced on Friday and with it, all the strings in this release with the exception of the About page strings are now effectively frozen. A soft string freeze means they won’t be changed and no new ones will be added before the release in the first week of December.

Translate the 4.7 project, Admin, Network admin, Continent & cities and Twenty Seventeen

If your Development project is not translated to 100%, this is a good time to take care of that. Head to translate.wordpress.org and translate:

20 locales are already at 100%, very well done! Here’s a ping for the GTEs of locales that are at more than 50% right now.

Dev between 95% and 100% (15)

Dev between 90% and 95% (14)

Dev between 50% and 90% (51)

Upcoming hard string freeze

According to the development schedule, hard strings freeze should come on November 29th (+1d) and the release is expected on December 6th (+1d). There will be another post here and a global ping when that happens.

Thank you all for your hard work!

#soft-string-freeze, #wordpress-4-7

Help us validate 5 WooCommerce extensions in 24 locales

Thanks to GoDaddy’s initiative to support localization of WordPress plugins & themes, we at Automattic received translations of 5 plugins in 24 locales.

  1. WooCommerce
  2. Storefront Product Pagination
  3. Storefront Product Sharing
  4. Storefront Sticky Add to Cart
  5. WooCommerce Gateway Stripe

Validation process (2 options)

There are two ways you can use the translation files we have.

1. Review the translation using the PO files, then import them (you will receive credits).

OR

2. Review Waiting strings on translate.wordpress.org. I will import everything in one week (in case GTEs prefer the method 1) as Waiting status.

  • Please feel free to leave a comment if you want the import to happen sooner for your locale.
  • If you don’t have time to validate, the translations will just stay as “Waiting”. There is no time limit to review them.

Locales

Note to validators

  • There may not be all 5 translation files for your locale. That’s because some of the plugins are 100% completed already.
  • Preparing these files involved a bit of manual work on my side, so if you see any technical flaws it’s probably my fault. Please don’t hesitate to point them out, and I’d be glad to fix/investigate the cause.
  • Thanks in advance for your help!

Notes from the Polyglots chat on September, 7th

Locale stats

Releases: 162 locales. 64 locales up to date. 0 locales behind by minor versions. 10 locales behind by one major version. 20 locales behind more than one major version. 60 locales have a site but never released. 8 locales don’t have a site.

Translations: 162 locales. 61 locales at 100%. 6 locales have more than 95%. 6 locales have more than 90%. 28 locales have more than 50%. 53 locales have less than 50%. 8 locales don’t have a WP project.

Polish and Estonian are at 99%. @waclawjacek @iworks @petskratt are kindly asked to get in contact with Petya (@petya) as we can release for 4.6 even with the missing translations.

Vietnamese and Uighur are currently inactive even though they’re 97% translated – these are the two locales we need to get released soon.

Congratulations go to the Tibetan team (@tibetanitech & team) who brought their language to 100%. Our thanks also go to the Urdu team (@codemovement.pk & team): Urdu is currently growing by 10% each week.

Technical update

A minor release WordPress 4.6.1 is scheduled for today, 15:00 UTC.
This release has no new strings to translate. Release leads should make sure to update their SVN if necessary.

New text strings have been added in O2, P2 Breathe and Forums.

  • Forums: https://translate.wordpress.org/projects/meta/forums
  • P2 “Breathe” – https://translate.wordpress.org/projects/meta/p2-breathe
  • O2 – https://translate.wordpress.org/projects/meta/o2

The rollout of o2 for the community pages is about to begin. Rosetta sites will also get a new user role Locale Manager which is basically the current Editor role.

A summary of the chat from the GlotPress office hours can be found at https://blog.glotpress.org/2016/09/06/office-hours-recap-september-6/. The introduction of Global Glossaries is planned for version 2.3. or 3.0 (above mentions summary contains a roadmap).

Technical details for Cross-Locale Project Translation Editors will be discussed today (September 7th) at 13:00 UTC in #meta-i18n.

Handbook update

Petya (@petya) has added several of the new articles in the planning spreadsheet, some pages will be removed.

Pascal (@casiepa) suggested we have a section for General Translation Editors in the handbook. Petya is looking forward to read his onboarding document for nl_BE GTEs in English, so we can migrate some of it to our own handbook.

Petya reminds everyone to check if their local information is correct on https://make.wordpress.org/polyglots/handbook/tools/local-slacks/ and https://make.wordpress.org/polyglots/handbook/tools/list-of-glossaries-per-locale/

Global WordPress translation day 2 survey

The tentative date for Global WordPress Translation Day 2 has been set to November 12th, 2016. Petya will soon start a survey for everybody who registered for the event on the website and will post about it on make.wordpress.org/polyglots to ask people to fill in before we make final decisions how to continue.

Open discussion

Pascal (@casiepa) has added a list of the top 120 plugins to his website: http://wp-info.org/plugin-top120. Users can select a locale and in return see the amount of waiting text strings and direct links to the plugin page on translate.wordpress.org.


ToDo for Petya:

  • list of stats we need,
  • post them on make/polyglots to gather anything missed so we can prioritize
  • Create/post survey for GWTD2
  • Create issues for adding the stats to make/polyglots (or as separate plugins)

#weekly-meeting-notes

Behind one or two major versions – releasing 95%+ locales for WordPress 4.6

Hey everyone,

It’s been a week since 4.6 and it’s amazing that we’ve got 60 locales released for it. I’d like to suggest that we release the 95% + locales as well, especially those who are behind more than one major version.

If you’re receiving this post in an email, you’re a Global Translation Editor for one of these locales. Please follow the instructions for a manual release in the handbook to create a package for your language.

Locales Behind more than one major versions

NB! That means your translation is inactive and your language IS NOT available for download or select on install anymore! A manual release is highly encouraged.

When a translation goes behind more than one major version it disappears for new users. That’s why it is highly recommended that locales translated 90%+ and previously active release now even though their translations need a bit more work to get to 100%. I’m including three locales at 85% + as well.

Behind one major version – recommended release

If you have any questions regarding the manual release, please post them as a comment here or ping the #Polyglots channel on Slack to get some help.

Thank you in advance and shout out if need a hand <3

P.S. Completing your translations to 100% will trigger an automatic release for most of these locales so that’s another way of releasing if you’re not keen to go for the manual process.

#inactive-locales, #inactive-translations, #releases, #wordpress-4-6

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 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%:

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

Handbook page for reference: Automated release packages

Does my locale 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 package will be regenerated.
  • If you have extensive custom changes, you will need to manually create a package via Rosetta as you have done in the past.

On Slack, watch out for messages like this one:

translation-bot

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 ping for all General Translation Editors whose locales are more than 50% and less than 100% translated:

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

Dev between 95% and 100% (35)

Dev between 90% and 95% (15)