New Strings For WordPress 4.8.1

Hello everyone, WordPress 4.8.1 is scheduled for Tuesday, August 1st. The minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. has a few new stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. for changes to the text widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. and a new 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. widget.

The new strings are now available on translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins. 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.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins.!

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 stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. changes. Happy translating! 🌏🌍🌎

#announcement #4-8

Locale Glossaries on translate.wordpress.org

GlotPress 2.3 “Statler”, the software behind translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins., introduced a long requested feature, 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/ 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 URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org (Example).

Locale glossaries can be edited by 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 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 coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., 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 stringsString A string is a translatable part of the software. A translation consists of a multitude of localized 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 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 later modify a translation (to fix a typo, for example), your language pack and release packageRelease package 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:

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 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 GTEs for 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 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

#release

Notice of Password Deactivation

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

[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/] 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 APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. used by our open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. translation software, GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org., that could have potentially exposed user data, including email address and encrypted/hashed password stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings..

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 SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

#announcement

Strings for WordPress 4.7 are available for translation

WordPress 4.7 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 was released a few days ago and now you can start translating WordPress 4.7 on translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins.!

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 stringsString A string is a translatable part of the software. A translation consists of a multitude of localized 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

New Team o2s

Two weeks ago we’ve rolled out 11 team o2s for testing. Today we’re pleased to announce that all 71 locales with a current release now have a team o2p2 "p2" is the name of the theme that blogs at make.wordpress.org use (and o2 is the accompanying plugin). When asked to post something "on the p2" by a member of the Polyglots team, that usually means you're asked to post on the team blog https://make.wordpress.org/polyglots/..

What should you use the o2 for?

A team o2 can be used for whatever your local community needs. For example, you can use it to talk about WordCamps, meetups, translations, support, documentation, meeting summaries, discussions about new ideas and the likes – in your language.

It can be a great platform for new people who would like to join your translation team. Or a great place to post about upcoming events and invite people to suggest topics. Basically, it’s an open wall for your community to discuss local issues. An official one, on your official local 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/ site.

How does your team get an o2?

Every 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. site should have one and every team can get one. If 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/ is currently released for 4.6, your o2 is already created. You can check if you have one by adding “/team” to the address of your Rosetta site. If you don’t already have one, please feel free to request one in a comment below this post.

The following 60 62 sites were created:

team-site

  • #ary: https://ary.wordpress.org/team/
  • #az: https://az.wordpress.org/team/
  • #bn_BD: https://bn.wordpress.org/team/
  • #bo: https://bo.wordpress.org/team/
  • #ca: https://ca.wordpress.org/team/
  • #cs_CZ: https://cs.wordpress.org/team/
  • #cy: https://cy.wordpress.org/team/
  • #da_DK: https://da.wordpress.org/team/
  • #de_CH: https://de-ch.wordpress.org/team/
  • #el: https://el.wordpress.org/team/
  • #en_AU: https://en-au.wordpress.org/team/
  • #en_CA: https://en-ca.wordpress.org/team/
  • #en_GB: https://en-gb.wordpress.org/team/
  • #en_NZ: https://en-nz.wordpress.org/team/
  • #en_ZA: https://en-za.wordpress.org/team/
  • #eo: https://eo.wordpress.org/team/
  • #es_AR: https://es-ar.wordpress.org/team/
  • #es_CL: https://cl.wordpress.org/team/
  • #es_GT: https://es-gt.wordpress.org/team/
  • #es_MX: https://es-mx.wordpress.org/team/
  • #es_PE: https://pe.wordpress.org/team/
  • #es_VE: https://ve.wordpress.org/team/
  • #eu: https://eu.wordpress.org/team/
  • #fa_IR: https://fa.wordpress.org/team/
  • #fi: https://fi.wordpress.org/team/
  • #fr_BE: https://fr-be.wordpress.org/team/
  • #fr_CA: https://fr-ca.wordpress.org/team/
  • #gd: https://gd.wordpress.org/team/
  • #gl_ES: https://gl.wordpress.org/team/
  • #gu: https://gu.wordpress.org/team/
  • #hau: https://hau.wordpress.org/team/
  • #hi_IN: https://hi.wordpress.org/team/
  • #hr: https://hr.wordpress.org/team/
  • #hu_HU: https://hu.wordpress.org/team/
  • #hy: https://hy.wordpress.org/team/
  • #id_ID: https://id.wordpress.org/team/
  • #is_IS: https://is.wordpress.org/team/
  • #ka_GE: https://ka.wordpress.org/team/
  • #km: https://km.wordpress.org/team/
  • #ko_KR: https://ko.wordpress.org/team/
  • #lt_LT: https://lt.wordpress.org/team/
  • #lv: https://lv.wordpress.org/team/
  • #mr: https://mr.wordpress.org/team/
  • #ms_MY: https://ms.wordpress.org/team/
  • #nb_NO: https://nb.wordpress.org/team/
  • #nn_NO: https://nn.wordpress.org/team/
  • #oci: https://oci.wordpress.org/team/
  • #pl_PL: https://pl.wordpress.org/team/
  • #pt_PT: https://pt.wordpress.org/team/
  • #ro_RO: https://ro.wordpress.org/team/
  • #sk_SK: https://sk.wordpress.org/team/
  • #sl_SI: https://sl.wordpress.org/team/
  • #sq: https://sq.wordpress.org/team/
  • #sr_RS: https://sr.wordpress.org/team/
  • #sv_SE: https://sv.wordpress.org/team/
  • #szl: https://szl.wordpress.org/team/
  • #te: https://te.wordpress.org/team/
  • #th: https://th.wordpress.org/team/
  • #tr_TR: https://tr.wordpress.org/team/
  • #uk: https://uk.wordpress.org/team/
  • #vi: https://vi.wordpress.org/team/
  • #zh_TW: https://tw.wordpress.org/team/

How does o2 work?

A new handbook page “Team o2” has been added to provide some details about the new site, how to manage and use it. Read it and ask any questions that remain in the comments here.

Who has access to the new o2s?

All locale managers get an Editor level access to the new o2s which allows them to customize the site and moderate content. o2s are separate WordPress installs from your Rosetta site, but all your current Locale Managers and Editors are added as users by default. All WordPress.org users can post and comment on locale o2s.

We’re delighted to finally be able to add this feature for all teams and we hope you find it useful to get new contributors and make communication about contributing to WordPress easier in your language.

#announcement, #dev-update

#rosetta

Asia Pacific meeting on Wednesdays

Starting this week, we are reviving the Asia Pacific weekly Polyglots meeting.

As mentioned in the polyglots chat last week, this will be an alternative opportunity for those who can’t attend the current meeting because of the timing.

When:
Wednesday at 6am UTC (Wednesday 6:00 UTC)

What:

  • Weekly polyglots meeting with more Asia-Pacific friendly time slot
  • Regular meeting topics plus announcements & discussion specific to the Asia-Pacific region

Who:

Anyone is welcome to attend!

I’m pinging GTEs of Asia & Pacific 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/, in case you are not closely following this P2p2 "p2" is the name of the theme that blogs at make.wordpress.org use (and o2 is the accompanying plugin). When asked to post something "on the p2" by a member of the Polyglots team, that usually means you're asked to post on the team blog https://make.wordpress.org/polyglots/..

Please let me know if you are pinged even though 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/ is not in the area (sorry!). And if anyone sees missing locales, please leave a comment as well 🙂

#announcement

#weekly-meetings

Translations for plugins and themes can now be imported with status waiting

I want to inform you about some recent changes to translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins.. 👀

See who approved/rejected your translation

It took a while but you can now finally see which user approved (or rejected) a translation. You’ll find the information in the metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. of a translation:

Approved by

Approved by

Rejected by

Rejected by

 

Import with status waiting

This was originally proposed by @akirk in #1654. This feature landed in GlotPress 2.1 but wasn’t available on translate.wordpress.org until now. Since today everyone can import translations with status waiting.

GTEs/PTEs can choose the status when importing a file. The import UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. looks like this:

import-status-both

A regular translators can’t choose the status. It’s set to waiting by defaut:

import-status-waiting

Regular translators can use the import functionality only for theme and pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party projects.

This is currently in a testing phase so any feedback is highly appreciated.

 

Other updates:

  • Support added for the Latin version of Hausa
  • Updated 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/ information for Kyrgyz
  • The native name for Tibetan is renamed to བོད་ཡིག
  • The “Project-Id-Version” for new PO filesPO files PO files are human readable files which contain translations we use. These files are not used by WordPress itself. Each language will have its own PO file, for example, for French there would be a fr_FR.po file, for german there would be a de_DE.po, for British English there might be en_GB.po. contains the full project name
  • Imported translations are now also checked for warnings
  • Translations which contain the placeholder for tab characters are automatically fixed

 

Let us know in the comments if you have any questions or found a bug in one of the recent changes. 🐛

#announcement, #dev-update

Faster deployment of language packs for themes and plugins

Since last Friday language packs for themes and plugins are no longer generated every 6-12 hours. Language packs are now build 30 minutes after a change to a translation or an import for new translations has happened.

This means that when you update a theme or a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party in the future it’s likely that WordPress will also download an up to date language pack. Or, ever had a critical typo in a translation? Just fix it and watch how fast your users will get the updated translation. 🚀

Because we all ❤️ SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.: Each build process is logged in the #meta-language-packs channel:

language-packs-slack-log-png

 

Expect similar changes to language packs for WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. soon.

P.S.: As always, all new code is open-sourced. You’ll find it in the metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. repositoryWordPress Localization Repository The WordPress Localization Repository at https://i18n.svn.wordpress.org/ is a Subversion repository where official WordPress translations are maintained. See Working with the Translation Repository for details. here, here and here.

#announcement, #dev-update

WordPress 4.6.1 has been released It is a…

WordPress 4.6.1 has been released. It is a security and maintenance release and there are no stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. changes.

In order to benefit from the automated release process make sure that 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/ is prepared.

Also released: 4.5.4, 4.4.5, 4.3.6, 4.2.10, 4.1.13, 4.0.13, 3.9.14, 3.8.16, and 3.7.16.

#announcement, #release

WordPress 4.6 has been released

WordPress 4.6 “Pepper”

Thanks to all translators for making WordPress 4.6 available in more than 50 languages! 🙌

#announcement

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

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

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 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!

Dev between 95% and 100% (35)

Dev between 90% and 95% (15)

Dev between 50% and 90% (29)

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

Strings for WordPress 4.6 are now frozen

Hello everyone,

as announced in the release post for the second release candidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. of WordPress 4.6, all stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. are now frozen, including the about page.

WordPress 4.6 RC2

You’ll find the strings in the admin project: https://translate.wordpress.org/projects/wp/dev/admin

WordPress 4.6 will be released next week on Tuesday, August 16th.

Happy Translating and thanks for your work!

 

P.S.: Don’t forget the subtitles for the release video. 📹

#announcement

Hello Polyglots you can start translating WordPress 4.6…

Hello Polyglots, you can start translating WordPress 4.6!

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

Stats:

  • wp/dev : 44 new stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. added, 1276 updated, 21 fuzzied, and 21 obsoleted.
  • wp/dev/admin : 79 new strings added, 943 updated, 37 fuzzied, and 76 obsoleted.
  • wp/dev/admin/network : 10 new strings added, 128 updated, 3 fuzzied, and 9 obsoleted.
  • wp/dev/cc : 32 new strings added, 460 updated, 0 fuzzied, and 0 obsoleted.

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

WordPress 4.6 is planned for August 16th. Happy Translating!

#announcement