Please add me as editor…

Please add me as editor of the Chinese (Taiwan) translation theme for
https://translate.wordpress.org/projects/wp-themes/pixgraphy/ at the request pixgraphy
Chinese (Taiwan) #zh_TW @cras4202tw

Thank you,
cras4202tw

#editor-requests

BuddyPress PTE request

Please add me as editor of the Chinese (Taiwan) translation plugin for https://translate.wordpress.org/projects/wp-plugins/buddypress at the request BuddyPress.
Chinese (Taiwan) (#zh_TW) (@kaiconan)

Thank you,
kaiconan

#editor-requests #request

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

Hueman addons plug PTE request

Please add me as editor of the Chinese (Taiwan) translation plug for https://translate.wordpress.org/projects/wp-plugins/hueman-addons at the request Hueman addons plug.
Chinese (Taiwan) (#zh_TW) (@kaiconan)

Thank you,
kaiconan

#editor-requests #translation-editor

Hueman theme PTE request.

Please add me as editor of the Chinese (Taiwan) translation theme for https://translate.wordpress.org/projects/wp-themes/hueman/ at the request Hueman.
Chinese (Taiwan) (#zh_TW) (@kaiconan)

Thank you,
kaiconan

#editor-requests #translation-editor

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!

Hello Polyglots! Please add me as editor of the Chinese (Taiwan)

Please add me as editor of the Chinese (Taiwan) translation plugin for https://wordpress.org/plugins/bbpress/ at the request bbPress.
Chinese (Taiwan) (#zh_TW) (@kaiconan)

Thank you,
kaiconan

#editor-requests, #request

Hello Polyglots! Please add me as editor of the Chinese (Taiwan)

Please add me as editor of the Chinese (Taiwan) translation plugin for https://wordpress.org/plugins/wp-statistics/ at the request WP Statistics.
Chinese (Taiwan) (#zh_TW) (@kaiconan)

Thank you,
kaiconan

#editor-requests, #request

Hello Polyglots! Please add me as editor of the Chinese (Taiwan)

Please add me as editor of the Chinese (Taiwan) translation plugin for https://wordpress.org/plugins/wp-pagenavi/ at the request WP-PageNavi.
Chinese (Taiwan) (#zh_TW) (@kaiconan)

Thank you,
kaiconan

#editor-requests, #request

Hello Polyglots! Please add me as editor of the Chinese (Taiwan)

Please add me as editor of the Chinese (Taiwan) translation plugin for https://wordpress.org/plugins/custom-login/ at the request Custom Login.
Chinese (Taiwan) (#zh_TW) (@kaiconan)

Thank you,
kaiconan

#editor-requests, #request

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

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 locales, in case you are not closely following this P2.

Please let me know if you are pinged even though your locale is not in the area (sorry!). And if anyone sees missing locales, please leave a comment as well 🙂

#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 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 all I want to be a zh…

Hi, all.
I want to be a zh_TW(Chinese (Taiwan)) Validator
Reason:
Now Chinese translation team Validator :@levinng has left the team
and I hope to replace levinng position and make a contribution for the Chinese translation,
BTW,a few days ago. I submit be more than 400 strings translated .po file out,
all correct(There are also translated another strings
so I think I have the ability to do the Chinese (Taiwan)Validator.

I will be active and check all the words. I will translate absolutely all the projects in my (a lot) spare time.

Having said that,may i join the validator’s team in order to improve the translating speed?

#request, #validator, #zh_tw

Hi all I have translated zh TW for…

Hi, all.
I have translated zh_TW for android since a few month ago.
the latest translation haven’t approve for a month.
Some help me to approve it ?
And may i join the validator’s team in order to improve the translating speed?

#request, #zh_tw