WordPress 4.9.3 has been released

WordPress 4.9.3 has been released. It’s a maintenance release with a few string changes.

WordPress 4.9.3 Maintenance Release

In order to benefit from the automated release process, make sure your locale is prepared.

#4-9, #announcement, #release

New Strings for WordPress 4.9.3

Hello everyone, WordPress 4.9.3 is scheduled for Monday, February 5th. It’s a maintenance release with a few new strings in WordPress dev and Administration projects.

Happy translating!

#4-9, #announcement

WordPress 4.9.1 has been released

It is a security and maintenance release. There are no string changes except one new string in 4.3 in wp/4.3.x/admin.

WordPress 4.9.1 Security and Maintenance Release

In order to benefit from the automated release process it could be possible that you have to prepare your locale first.

Also released: 4.8.4, 4.7.8, 4.6.9, 4.5.12, 4.4.13, 4.3.14, 4.2.18, 4.1.21, 4.0.21, 3.9.22, 3.8.24, and 3.7.24.

#announcement, #release

WordPress 4.9 should be released today – prepare your locales

WordPress 4.9 should be released today – prepare your locales

Dear Polyglots,

The last strings for 4.9 have been frozen since November 9th and WordPress 4.9 is about to be released.

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

1. Translate the 4.9 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%:

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

26 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 today and this is a very short notice, a last minute string was added yesterday as well so thank you in advance to everyone who makes time to get their locale to 100%. For those who don’t the next couple of weeks are a great time to get this done as well so no stress and happy translating!

Petya

#announcement

#hard-freeze, #wordpress-4-9

4.9 String Freeze

Hi Polyglots team!

Wanted to post up a reminder that strings are officially frozen for 4.9. ❄️

You can find the new strings in the Development project at https://translate.wordpress.org/projects/wp/dev. Stoked to see how many languages are already at 100%!

If you think a string is incorrect or unclear, please don’t hesitate to ask for help in the #polyglots channel on Slack.

Thanks for all your great work 👏

#4-9 #announcement

New WP.org Theme Ready for Translations!

As a first step in the effort to bring the wordpress.org homepage to Rosetta sites, we built a new theme to take advantage of the modularity of the WordPress.org base theme and make it easier to later add the enhancements mentioned in #2861-meta.

We tried to lighten the load for translators by importing existing translations from the current rosetta and plugin directory theme, which covered 50% of strings for the more active locales. The project is available at:

https://translate.wordpress.org/projects/meta/wordpress-org

We also decided to keep the design as close to the existing Rosetta theme as possible for now. So while you’ll see some changes—primarily in font size and margins—the overall look and feel should not be too far off. The goal was not to revolutionize the way international sites look, but rather to bring the design closer to parity with the root wordpress.org site.

Newly created locale sites will automatically use the new theme. Once the theme is translated to 100% for an existing locale, it will be activated for its Rosetta site. If you do encounter bugs or unforeseen behavior, please leave a comment on #2861-meta.

Thanks to @ocean90 for raising the issue and for his continued feedback on this effort.

#announcement

#2861-meta

Start translating WordPress 4.9

WordPress 4.9, planned for November 14, 2017, is now ready to be translated on translate.wordpress.org!

WordPress 4.9 Beta 1

You can find the new strings (~300) in the Development project at https://translate.wordpress.org/projects/wp/dev. Note that 4.9 is still in development so some strings still may change over time. Strings for WordPress 4.8 have been moved to https://translate.wordpress.org/projects/wp/4.8.x.

Soft string freeze is planned for October 30 and hard string freeze for November 6, 2017.

If you think a string is incorrect or unclear, please don’t hesitate to ask for help in the #polyglots channel on Slack

Happy translating! 🌏🌍🌎

#4-9, #announcement

WordPress 4.8.1 has been released….

WordPress 4.8.1 has been released. It is a maintenance release and there were a few string changes.

WordPress 4.8.1 Maintenance Release

In order to benefit from the automated release process make sure that your locale is prepared.

#4-8, #announcement, #release

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

New Strings For WordPress 4.8.1

Hello everyone, WordPress 4.8.1 is scheduled for Tuesday, August 1st. The minor release has a few new strings for changes to the text widget and a new HTML widget.

The new strings are now available on translate.wordpress.org in the WordPress dev project.

Happy Translating!

 

Please note that due to technical limitations there won’t be new language packs for the current 4.8 release until 4.8.1 has been released.

#4-8-1, #announcement

Start translating WordPress 4.8

WordPress 4.8, planned for June 8, 2017, is now ready to be translated on translate.wordpress.org!

WordPress 4.8 Beta 1

The strings are in the Development project at https://translate.wordpress.org/projects/wp/dev. The strings for WordPress 4.7 have been moved to https://translate.wordpress.org/projects/wp/4.7.x.

So far there are only ~160 string changes. Happy translating! 🌏🌍🌎

#announcement #4-8

Locale Glossaries on translate.wordpress.org

GlotPress 2.3 “Statler”, the software behind translate.wordpress.org, introduced a long requested feature, Locale Glossaries.

A locale glossary is a glossary for all projects of one locale. Since a few days the new type of glossary is also available on translate.wordpress.org.

Link to a locale glossary on locale project overview

You’ll find a link to a locale glossary in the locale box on project pages like you can see in the screenshot above.

All project glossaries that were previously at projects/wp/dev/<your locale>/glossary have been moved to the new locale glossary. You don’t have to do anything. To prevent showing a 404 error, a redirect has been set up which redirects to the new URL (Example).

Locale glossaries can be edited by General Translation Editors while project glossaries can also be managed by Project Translation Editors. Terms of a locale glossary are merged with a project glossary (if one exists) and highlighted with a little bubble.

The handbook has been updated to include more information about locale glossaries.

👉 Now it’s time to review your glossary to provide consistent translations across core, plugins, themes, and the other projects.

#announcement

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

Notice of Password Deactivation

Hello everyone, some of you will have the following email in your inbox:

[WordPress.org] Notice of Password Deactivation

Your password on WordPress.org has been deactivated, and you need to reset it to log in again.

We discovered internally a bug in the API used by our open source translation software, GlotPress, that could have potentially exposed user data, including email address and encrypted/hashed password string.

Based on our analysis of the logs, we don’t think this happened, but out of an abundance of caution we’re proactively disabling the passwords on a couple hundred translation volunteer accounts, one of which is yours.

We apologize for this. When you reset your password, please choose a new one, and as always we discourage using the same password across multiple services.
To reset your password please follow the ‘Lost password?’ link on the login page.

Username: ###USERNAME###
Email: ###EMAIL###

Again, we apologize for this. If you have any questions don’t hesitate to post them in the comments or contact me @ocean90 on Slack.

#announcement

Strings for WordPress 4.7 are available for translation

WordPress 4.7 Beta 1 was released a few days ago and now you can start translating WordPress 4.7 on translate.wordpress.org!

WordPress 4.7 Beta 1

The strings are in the Development project at https://translate.wordpress.org/projects/wp/dev. The strings of WordPress 4.6 have been moved to https://translate.wordpress.org/projects/wp/4.6.x.

Stats:

  • wp/dev: 415 new strings added, 1477 updated, 29 fuzzied, and 30 obsoleted.
  • wp/dev/admin: 27 new strings added, 1116 updated, 54 fuzzied, and 29 obsoleted.
  • wp/dev/admin/network: 6 new strings added, 273 updated, 8 fuzzied, and 2 obsoleted.

WordPress 4.7 will also introduce a new default theme, Twenty Seventeen. You’ll find its strings at https://translate.wordpress.org/projects/wp-themes/twentyseventeen.

There are a few fuzzy strings which are a good starting point for WordPress 4.7.

WordPress 4.7 is planned for December 6th.

Happy Translating!

#4-7 #announcement