Prepare your locale for 4.1.1 – Update: WordPress 4.1.1 has been released

Translate WordPress

You can help translate WordPress to your language by logging in to the translation platform with your WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ account and suggesting translations (more details).

Want to help in managing and validating translations? Get in touch with the existing language team and follow the glossaries & style guides if the team has them.

Don’t see your language? You can request support for it.

Edit: WordPress 4.1.1 has been released. Packages are currently build every ~~hour~~ 6 hours.

WordPress 4.1.1 will be released in the next 24 hours. In order to benefit from the automated release process it could be possible that you have to prepare your 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/ first.

Translations must be at 100%

(This includes wp/dev, wp/dev/admin and wp/dev/admin/network.)
Currently 39 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 at 100%, 10 locales are at 99%. Most of them don’t have translated the two new stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. in 4.1.1, see String changes in WordPress 4.1.1. Please check also for existing waiting strings and clear them out, otherwise the build will be skipped.
(Also do not forget about the default themes and Akismet project.)

Update version in readme.htmlHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites.

(For these locales: ar, bs_BA, cy, de_DE, de_CH, en_CA, eo, es_PE, eu, fi, fr_FR, he_IL, it_IT, nb_NO, pt_BR, pt_PT, ro_RO, sv_SE, th, and tr_TR.)

If you have custom changes on i18n.svn.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ and you are using branches/4.1 to release your package you only have to change the version in readme.html.
If you’re using tags/4.1 you have to create a new tag for 4.1.1 first. It’s just a copy of trunk/ or tags/4.1 and the version change to readme.html.
If you have tags/4.1 and branches/4.1, but no tags/4.1.1 the build will use branches/4.1.

If you have any questions just comment here or 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.” me @ocean90 on Slack #polyglots.

#announcement

Rami Yushuvaev 11:00 am on February 18, 2015

In hebrew (he_IL), I removed the wordpress version number from the README.TXT file. This way i don’t need to update the file in each new vesion.
- Dominik Schilling (ocean90) 11:13 am on February 18, 2015
  
  Works too, but then you should use branches/4.1 instead of tags/4.1 like you have currently.
- Dominik Schilling (ocean90) 1:53 pm on February 22, 2015
  
  @ramiy Would you like to change that? 🙂
petskratt 11:03 am on February 18, 2015

Could it be possible to bring release requirement down for `et` and publish without `wp/dev/admin/network` ?

As nobody seems interested in network version here it is bound to be dragging behind in future… which has currently resulted in also the main translation lagging behind couple of releases (and `et` has never reached the official multilingual installer if I’m correct).
- Dominik Schilling (ocean90) 11:14 am on February 18, 2015
  
  I can create a language pack for you, yes. But you still have to build a 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. by yourself.
Stefano Aglietti 11:08 am on February 18, 2015

it_IT ready for relase
Nick Weisser 12:12 pm on February 18, 2015

de_CH ready for release, too.
Birgit Olzem 12:19 pm on February 18, 2015

de_DE ready to go
Petya Raykovska 3:36 pm on February 18, 2015

bg_BG is done too, had one waiting stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. in Admin.
Mattias Tengblad 7:37 pm on February 18, 2015

sv_SE ready
Rafa Poveda 9:42 pm on February 18, 2015

es_ES ready
Victor J. Quesada 11:56 pm on February 18, 2015

gl_ES ready
- Dominik Schilling (ocean90) 12:08 am on February 19, 2015
  
  gl_ES can’t benefit of an autogenerated 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. because there is no tags/4.1.1 and branches/4.1 includes a custom wp-admin/setup-config.php file (which is not needed?).
Kazama 6:24 am on February 19, 2015

th was released 😛
Gwgan 2:00 pm on February 19, 2015

WordPress 4.1.1 cy has appeared on my WordPress websites but not as a download available at cy.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/. Do I need to take further action or will this appear within a short while?
Thanks
- Dominik Schilling (ocean90) 2:05 pm on February 19, 2015
  
  You have to take further action, please read the “Update version in readme.htmlHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites.” section. tags/4.1.1 does not exists for cy.
  - Gwgan 12:58 pm on February 22, 2015
    
    Is there an optimum set-up we should aim for? it_IT and de_DE have the following set-up:
    
    tags/new 4.1.1 folder/dist/readme.htmlHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites., wp-config-sample.php
    trunk/dist/readme.html, wp-config-sample.php
    
    Is this what we’re aiming at? Thanks.
    - Dominik Schilling (ocean90) 1:04 pm on February 22, 2015
      
      If you have translated both files, yes, that would be the right setup.
Hugh 8:52 am on February 22, 2015

New here, Question: is there a way to get a feed of some kind of the 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/ that WP supports? I mean this is a shifting number/set, as various versions of WP evolve. So, I am wondering if there is a feed for the ones at 100%.
- Dominik Schilling (ocean90) 1:02 pm on February 22, 2015
  
  See the table on https://make.wordpress.org/polyglots/teams/.