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

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

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.org site.

How does your team get an o2?

Every Rosetta site should have one and every team can get one. If your locale 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

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)

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

Hi Currently I’m the only active administrator validator…

Hi,

Currently I’m the only active administrator/validator for galician language (gl_ES). I wish to relieve this activity and let others to engage in administrative tasks. For now, we have a volunteer, which currently is the most active performing translations.

I added this user, @egalego, as Editor on Galician Rosseta site: http://gl.wordpress.org

I don’t know if it is necessary to grant access elsewhere, as the svn repository or the codex. I leave this in the hands of administrators.

Thanks.

#administrator, #codex-translation, #glotpress, #gl_es, #rosseta, #validator

Hi Could you include Galician language into Rosetta…

Hi,

Could you include Galician language into Rosetta forums translation project?

Language code: gl_ES
Language name: Galician
Validator: pcgaldo

Thanks a lot!

#forums, #glotpress, #gl_es, #request, #rosetta, #validator

Where we can find a pot file to…

Where we can find a .pot file to update the rosetta using previous translations?

#gl_es, #question, #rosetta

Hi We have a little problem automatic traslation…

Hi,

We have a little problem: automatic traslation is not working in GlotPress for galician language, although our language is supported in the Google tool.

Error in translating via Google Translate: undefined!

Can you solve this problem, please?

#glotpress, #gl_es, #google-translate, #request

We have a little problem with the community…

We have a little problem with the community forum of galician translators. Currently we are using a BuddyPress support forum thread: https://buddypress.org/support/forum/plugin-forums/wordpress-en-galego/

Paul Gibbs have sent us this notice:
“Why are we discussing translation of WordPress on the BuddyPress.org support forums?
This is probably better discussed on your WordPress.org i18n site, or on https://make.wordpress.org/polyglots/.”

Our community is very small and has few contributions lately. Today we only have time to do some work on the translations of WordPress. The translation of BuddyPress and other additions are waiting, and we don’t know when we will be able to take them again.

Until now, maybe by carelessness or lack of time, we have no forum in the galician WordPress i18n site.

Under this circumstances, we continue to work as before, waiting for better times with complete translations and enough time to have a forum on our WordPress i18n site.

I contact polyglots forum in order to see what we need to have updated site and forum.

When I have an answer, I will post in the galician translators BuddyPress site, in order to leave the BuddyPress thread as soon as possible, when any of the Contributors commit to undertake the changes.

#forum, #gl_es, #request

Hi Zé Can you grant me admin rights…

Hi, Zé,

Can you grant me admin rights with my WP.org account (pcgaldo) into the galician localization group?
https://buddypress.org/community/groups/wordpress-en-galego/

Thanks.

#admin, #buddypress, #gl_es, #request

Hello Zé We have a little problem with…

Hello, Zé,

We have a little problem with the credits page, in the translators section.

The system reflects the profiles of the translators that had any approved translation in GlotPress. In our case, it only appears one translator. We omit, therefore, all the translators who make great contributions through the translation of .po files, leaving aside the GlotPress platform.

Another problem we have is that some translators do not want to be in the credits page.

Maybe in the future you could develope a privacy tool, eg. in the profile configuration of the WP.org account, allowing us to choose if we want to appear in the credits pages. Or, if it is not possible, a tool or a file on the svn to manually configure the translators that will appear on the credits page for each language.

Thanks in advance.

#credits, #gl_es, #wordpress-org

Hello Zé I am testing the Twety Eleven…

Hello, Zé,

I am testing the Twety Eleven theme and I found two problems:

  • When compiling the 3.2-beta2 version on gl.wordpress.org, it does not include the translation files for twentyeleven.
  • Once uploaded on the site manually, I see that some strings of the theme are not translated.

You can see a screenshot here: http://db.tt/nvhIBGB
The gl_ES translation files are here: http://svn.automattic.com/wordpress-i18n/gl_ES/trunk/messages/twentyeleven/gl_ES.po

I know it is only a beta and many things are changing, but I notify it to bring you the opportunity to make corrections if necessary.

Thanks a lot.

#3-2, #beta, #gl_es, #request, #rosetta, #twenty-eleven

Hi Galician translation SVN repositories updated with the…

Hi,

Galician translation: SVN repositories updated with the 3.1.1 version. Downloadable package compiled on gl.wordpress.org. Release announced on galician language.

WordPress 3.1.1 en galego

#3-1-1, #galician, #glotpress, #gl_es, #new, #release, #wordpress

Good night Zé Currently I have access to…

Good night, Zé.

Currently I have access to the gl_ES branch of BuddyPress in GlotPress. There I can upload .po files in order to update the translation of multiple lines together.

I need access to the gl_ES branch of the other projects in the same way.

One question:
Why DEV version of WordPress (future 3.2) do not show the lines translated previously? Many lines that were translated in 3.1 go away in the development of 3.2.

Thanks.

#glotpress, #gl_es, #request, #validator

Hello I wish to participate with the WordPress…

Hello,

I wish to participate with the WordPress translators community.

I have prepared, awaiting proofreading, a translation of the BuddyPress plugin and I am also willing to do more translations and reviews, in Galician (gl_ES), Portuguese of Portugal (pt_PT) Brazilian Portuguese (pt_BR) and Spanish of Spain (es_ES).

Please, give me SVN commit privileges.
WP Forums user: pcgaldo

I am translating the theme-specific .pot file to galician locale.

I also want to create a new galician site:

Locale: gl_ES.
URL: https://gl.wordpress.org/
Site Title: WordPress Galego
Site Description: “WordPress en galego.”
Admin Usernames: pcgaldo

I am waiting for your answer. Thanks a lot!

#galician, #gl_es, #locale