On the behalf of the whole team I…

On the behalf of the whole team I would like to inform you all that we have successfully completed `Gujarati` Translation for WordPress 4.6 and now its available.

હવે વર્ડપ્રેસ ગુજરાતી બોલશે.

Thanks to all contributors who did amazing job.

#core, #gu, #gujarati

WordPress 4.5 Hard String Freeze

Hello Polyglots!

WordPress 4.5 RC2 has just been released, and with it, there is now a hard string freeze for WordPress 4.5 (including the About Page).

My apologies for the delay! I hoped to deliver this news much sooner.

Release proceedings for 4.5 are scheduled to start at April 12, 2016 at 0900 PDT.

Please let me know if you encounter any difficulties, or have any questions.

Thank you for all of your hard work!

#core, #release

Hebrew has own css declaration for font in…

Hebrew has own css declaration for font in core. Myanmar also should have css font family declaration. I’ve opened ticket #29664 since last year and no progress. There is no Myanmar glymps or characters in Open Sans font. Most operating system do not have proper Myanmar font.

#core, #myanmar, #my_mm, #request

“Hard” string freeze is now in effect for…

“Hard” string freeze is now in effect for 4.3.

The About page strings are now available for translation, and we expect to tag RC3 later today or tomorrow.

“Hard” freeze means that all core and About page strings are available for translation, and all other string changes have been frozen beyond this point.

#4-3, #core, #string-freeze

Hard string freeze is now in effect…

“Hard” string freeze is now in effect for 4.2.

The About page strings are now available for translation, and we expect to tag RC1 later today.

“Hard” freeze means that all core and About page strings are available for translation, and all other string changes have been frozen beyond this point.

According to the 4.2 release schedule, we’re right on track.

#core, #string-freeze

4.2: “soft” string freeze

“Soft” string freeze

This morning we released 4.2 Beta 4, and as promised, we’ve also reached soft string freeze.

“Soft” string freeze constitutes a freeze on all new strings, excluding the About page. You can expect a “hard” freeze once we tag RC1 in a week or so, and that will include the About page strings.

It’s likely you’ll be seeing some changes to existing strings trickling in over the next few days as @nacin goes through and audits changes from the release. We’ll do our best to keep that to a minimum.

According to the 4.2 release schedule, we’re right on track for an April 22nd release.

#core, #string-freeze

Font family for headings in RTL locales changed to Arial

A quick note, we’ve switched the font family for headings in all RTL locales to bold Arial, see ticket #30807. The change only affects the admin area.

If that affects your locale and you have any concerns regarding this change, please comment on the ticket. Thanks!

#4-2, #announcement, #core, #rtl

I’ve opened a ticket #29664 two month ago…

I’ve opened a ticket #29664 two month ago. No one response. Today I’ve attached a patch file to support Myanmar script font-family.
I’m looking for a way to embed google web font for Myanmar.
I want to know if it is possible to embed in WP core or do I need to release Locale specific Package with embedded fonts.
Is there a way to add Word Break rules js file in WP core?

#core, #my_mm, #request

WordPress 4.0 is out See full instructions here…

WordPress 4.0 is out. See full instructions here. When building, you can simply choose 4.0/4.0.x and HEAD and it will work.

#4-0, #core, #release

Instructions for 4.0 which will be released in…

Instructions for 4.0, which will be released in the next 15-30 minutes:

  • The need to create a localized build through the Rosetta form is unchanged for 4.0. This will go away very soon, but we couldn’t get all the ducks in a row to make this go away for 4.0. I’m trying for 4.0.1. Thank you so much for your patience as we work to make the experience painless for all of you.
  • As usual, you will build your release off the 4.0 tag, which will exist soon. Since you’re building off of 4.0, you don’t need the revision number (HEAD is fine), but it’s 29485.
  • CHECK YOUR BUILD FIRST. Especially $wp_version in wp-includes/version.php.
  • If you have WPLANG defined in wp-config-sample.php, the build will be rejected. If you don’t translate this file and this file is thus an exact copy of the core file, you may delete it. Only mess with trunk / 4.0, not dist directories from 3.9 or earlier.
  • Thanks to your feedback, the language chooser will not show for a localized build. For the regular build, it will show. These languages are via the API at https://api.wordpress.org/translations/core/1.0/?version=4.0 and reflect any translations that are 100% for all three projects (wp/dev, wp/dev/admin, wp/dev/admin/network). Percent completion is checked periodically and language packs are then built.
  • (This is mainly for @pavelevap…) If you are not at 100% for all three projects, you may ask for me to manually trigger an incomplete language pack, for the purposes of being available in the language chooser. I’d rather not, though — this is API-driven and we can always get the language in there once you finish your translation.
  • Do not forget to 100% translate Akismet. There were no string changes in the default themes.

If you have any questions, please leave a comment, and @ocean90 or I will address them. If there is an urgent issue, please ping me in #wordpress-polyglots or #wordpress-dev.

#4-0, #announcement, #core, #release

You have about 14 hours to complete your…

You have about 14 hours to complete your translations for WordPress 4.0.

I’ve added one last string, “Release Lead,” for use on the credits page. If you were at 100% for 4.0, don’t worry, you have a language pack built already, but it’d be nice if you could translate this.

Please ensure you are 100% for wp/dev, wp/dev/admin, and wp/dev/admin/network. Currently 19 languages have done this (minus the new string).

pl_PL, he_IL, my_MM, and eu (Basque) are all at 100% for wp/dev but are not at 100% for the administration projects. Another 30 languages are at 90% or higher for wp/dev — so close!

WPLANG should be removed from wp-config-sample.php. If you have a custom wp-config-sample.php file in your SVN trunk/dist directory, please update it. See how German did it here.

If you are translating via SVN please make sure you are importing each of your PO files into translate.wordpress.org, for language packs.

More launch day instructions to follow. Thanks for your patience. If you have any specific questions you’d like me to answer, please include them below so I can be sure to cover them in my instructions.

#4-0, #announcement, #core

WordPress 4.0 RC is out

WordPress 4.0 RC is out.

In a few hours I’ll be building new language packs for RC1 for any locale at 100% for the wp/dev project and all sub-projects (this includes the network admin). Each day as translations are completed, packs will be created or updated. We’ll work out some kinks over the next few days and hopefully have everything in order come September. Expect to hear more from me in the coming days and weeks as we begin a new journey. 🙂

@helen is targeting September 3 for release. The about page is done, help tabs are updated, and strings are frozen. You have one week to get everything in order, so good luck and happy translating!

#4-0, #core, #string-freeze

I’ve finally fixed a very broken translate wordpress…

I’ve finally fixed a very broken translate.wordpress.org and pushed 4.0 to https://translate.wordpress.org/projects/wp/dev. There are ~85 new strings, which you can now begin translating. (It should probably go pretty quickly.)

It’s safe to consider this a “string freeze” — with the exception of the about page, which will be finalized over the weekend.

#4-0, #announcement, #core

Internationalization goals for WordPress 4.0

Internationalization goals for WordPress 4.0

Hello all. Earlier today I published a post on make/core called Internationalization goals for WordPress 4.0. This of course affects you so I wanted to make sure you saw it and give you the opportunity to provide feedback. I am sure you will have questions as to how this will affect translation teams, which you can ask here if you’d like.

Let me outline the goals for WordPress 4.0. I’ll then answer what I anticipate will be some frequently asked questions.

  1. The first step installing WordPress should be to choose a language. The rest of the install process would then be in that language.
  2. You should be able to choose/switch a language from the general settings screen, after which the language pack should be downloaded.
  3. You should be able to search from the dashboard for plugins and themes that are available in your language.
  4. All localized packages should be able to be automatically generated and made available immediately as part of the core release process.
  5. Localized packages should only be used for initial downloads from WordPress.org. Instead, language packs should be transparently used for updates.

Does this mean I will no longer need to create builds and releases?
That’s the idea. If at time of core release you are 100% translated, then I’d want everything to be packaged up automatically. Ideally, the Rosetta builder will go away entirely.

The builder will go away? But what about alpha/beta/RC releases?
We’ll make it possible to build these.

What if my locale doesn’t make any modifications?
Once this goes into effect, you won’t be able to make local modifications anymore. The whole process is being simplified. We’ll be retiring the ability to ship a {$locale}.php file or to add files to dist/. Future adjustments will need to go through WordPress core.

What if my locale currently requires local modifications?
We’re not going to make the experience worse for your users by preventing you from making these modifications. As I noted in the post, about 14 locales make changes that WordPress core will need to account for first, not including readmes, licenses, and the sample config file. This is going to be similar to my efforts in 3.4 to reduce the number of hacks you needed to make. Once your locale no longer requires modifications, legacy modification support will be disabled for your locale.

So, how are we going to translate readmes, licenses, and sample config files?
I don’t know yet. They will either continue to be done in SVN, incorporated into the Rosetta dashboard, or somehow imported into translate.wordpress.org. You won’t need to update the readme with each version, though; we’ll be sure of that.

Does this mean SVN won’t be needed anymore?
The idea is to simplify the entire process down to translation. You shouldn’t need to be a developer, or know how to use version control, or be awake to immediately push a build, or be responsible for issues like this.

What if I want to use SVN still?
I plan to drop support for building packages directly from SVN. This isn’t just simplifying the process. It will also drastically simplify the complex build system behind Rosetta (yes, the rest of it will be open-sourced) and improve maintainability. If you’re one of the three or so translation teams that make liberal use of SVN, I imagine we can work something out. (After all, GlotPress makes it easy to import PO/MO files.)

Will this eliminate the double-upgrade annoyances?
You bet. There will no longer be irrelevant “in English” warnings. Automatic background updates will “just work” without leaving you confused.

Do language packs mean I can fix a typo post-release?
Yes! Language packs for core WordPress releases will mean that updating the strings will be separated from updating the software itself. We don’t typically change strings in a point release because it slows you down in shipping a package (which is sometimes a security fix), but we might do that in the future with enough warning. And if you have a typo in a translated string, you could fix it whenever, and the language pack would simply be rebuilt and re-served to installs — no need to wait (or hope) for a point release.

This post mentions plugins and themes, but when is all of that coming?
Basic language pack support is live for a few select plugins (bbPress, BuddyPress, Akismet) and I expect to have a wider pilot program ready in the coming weeks. More details to follow, promise.

Nacin, you forgot about X!
The post and its comments mention a few things that aren’t going to happen for 4.0, like “Admin in English,” per-user languages, per-post languages. (We need to walk before we can run.) If something is missing that should probably be in 4.0, please mention it. Or if I over-simplified something in that post (as in, it doesn’t look like I accounted for how complex something is going to be to do), please enlighten me.

Bonus: How can I help build all of this?
Great question! I’ll be shifting tasks into tickets on both core and meta Tracs in the coming days. If there is something in particular you want to help with, please let me know.

#4-0, #announcement, #core

WordPress 3.9.1 is out There are no string…

WordPress 3.9.1 is out. There are no string changes.

You may have noticed the 3.9.x project in translate.wordpress.org is not yet functional, due to some ongoing GlotPress development work. (You’ll find it doesn’t work.) The “wp/dev” project is frozen to the 3.9 branch and is the proper project to use.

With regards to SVN: there is a core 3.9.1 tag already created, so no revision number is necessary, though the proper revision to use is 28182.

3.9.x releases will be the last set of releases with all of these hoops to jump though. It’ll be made much easier in the coming few weeks/months.

Thanks all and happy translating.

#3-9, #core, #release