Locale 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/ stats
Releases: 160 locales 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/. 74 locales up to date. 0 locales behind by minor versions. 1 locale behind one major version. 16 locales behind more than one major version. 56 locales have a site but never released. 13 locales don᾿t have a site.
Translations: 160 locales. 60 locales at 100%. 3 locales have more than 95%. 4 locales have more than 90%. 24 locales have more than 50%. 58 locales have less than 50%. 11 locales don᾿t have a WP project.
There’s a plan to create a site for every existing locale and to create projects for these locales in preparation for the WordPress Global Translation day. Once they’re ready, we can actively look for contributors for those locales.
The first beta 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. of 4.5 is planned for next week, it’s usually the time where wp/dev gets the new strings A string is a translatable part of the software. A translation consists of a multitude of localized strings.. https://make.wordpress.org/core/version-4-5-project-schedule/
WordPress Global Translation Day
- We set the date for April 24th, 2016 – Sunday.
- We have more than 130 responses from 30 countries willing to participate. The poll will stay open and hopefully more people would get to fill it out.
- Petya will share results of the poll next week
We could do something very similar to WordSesh, but in different languages – 30 min/ 1h sessions on how to translate WordPress and things specific to every language. So at 9am for every timezone we would have a new session starting that would help people translate to a different language. These sessions will be recorded and published immediately so even if you missed the beginning, you would be able to watch it and join the team for a few hours.
То sum up:
- It’s a 24 hours sprint of WordPress related talks. I basically want to do the same but with a niche focus on Localizing WordPress. We can then use these resources for new PTEs
- We will need at least 24 GTEs to commit to doing this. If we have 30 min sessions instead of 1h, we can also have much more.
- We can have more than one GTE A General Translation Editor (often referred to as GTE) is a person, who has global access to validate strings on all projects for a specific locale. in a session and after your session is done, you can continue to work with translators on Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/./ your channel of communication of choice.
- You will be able to reuse a slide deck I’ve prepared to onboard new users (both contributors and GTEs), but the idea is for you to localize it
- We start at the East with first country to wake up. And we do a 24h sprint with sessions.
- Everyone is free to join whenever they like, but we get GTEs from different locales to commit to being online to help onboard people.
- I’m going to chat to Scott about lending us the Wordsesh setup. Not set in stone, but I don’t think they’d refuse.
- Some of us organise events on the ground and gather contributors in person.
- Others work remotely.
Ultimate goal – get more people on board, translate many many many strings and enjoy our global team building day.
@Chantalc brought up the loading time problem GTEs have when adding new PTEs. She’ll open an issue for @ocean90 to look into.