Category Archives: Post

Alin Marcu 5:59 am on October 27, 2015
Tags: , , , , ,   

Notes from the Polyglots chat on October 21st

  • 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/ stats
    • We have 157 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/, from which 60 locales are up to date, 1 locale is behind by a minor version and 4 locales are behind by one major version.
    • We have #te behind by a minor version and #cs_CZ, #ky_KY, #oci, #vi behind by one major version.
  • Technical updates
    • the target date for release of WordPress 4.4 is December this year.
    • the project for 4.4 will be available for translation soon
    • Twenty Sixteen is already available for translation here: https://translate.wordpress.org/projects/wp-themes/twentysixteen/
  • Feedback:
    • @gagan0123 would like to have aggregated result for a search on different projects for a particular locale. For details see ticket #1351.

#weekly-meetings

Alin Marcu 5:55 am on October 19, 2015
Tags: , , , , , ,   

Notes from the Polyglots chat on October 14th

  • 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/ stats
    • We have 157 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/, from which 60 locales are up to date, 1 locale is behind by a minor version and 4 locales are behind by one major version.
    • We have #te behind by a minor version and #cs_CZ, #ky_KY, #oci, #vi behind by one major version.
  • 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.-i18nInternationalization Internationalization (sometimes shortened to I18N , meaning “I - eighteen letters -N”) is the process of planning and implementing products and services so that they can easily be adapted to specific local languages and cultures, a process called localization. This is the process of making software translatable. Information about Internationalization for developers can be found in the Developer’s handbooks.
    • no new updates
  • Documentation for GTEs to add PTEs
    • We need to improve the Adding New Users page and add some screenshots to make it clear for GTEs how to add per Project 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; @netweb will have this updated.
    • @luisrull will make a draft with information we’re missing regarding the per Project Translation Editors.
  • Feedback:
    • @luisrull: I’d like to encourage Plugins / Themes authors to add 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/ usernames in 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/. / Polyglots requests. Some of them were using 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/ usernames instead.
    • @netweb: It would be great if ​all P2 / Polyglots post authors could edit their own posts to mark checkboxes.

#weekly-meeting-notes, #weekly-meetings

Alin Marcu 5:05 am on October 12, 2015
Tags: , , , , , ,   

Notes from the Polyglots chat on October 7

  • 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/ stats
    • We have 156 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/, from which 60 locales are up to date, 1 locale is behind by a minor version and 4 locales are behind by one major version.
    • We have #te behind by a minor version and #cs_CZ, #ky_KY, #oci, #vi behind by one major version.
  • 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.-i18nInternationalization Internationalization (sometimes shortened to I18N , meaning “I - eighteen letters -N”) is the process of planning and implementing products and services so that they can easily be adapted to specific local languages and cultures, a process called localization. This is the process of making software translatable. Information about Internationalization for developers can be found in the Developer’s handbooks.
    • The process of adding 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 got simplified! You no longer need to invite a user before making him a Translation EditorTranslation 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 – https://make.wordpress.org/polyglots/2015/10/06/update-you-no-longer-have-to-invite-a/. That’s awesome!
    • General Translation Editors are not opted-in, at this moment, for locale notifications (see #1274). All GTEs should add that notification to their profiles, here’s how.
    • Currently we don’t have a way to easily distinguish General Translation Editors from Project Translation Editors. Having #1234 implemented would be great.
    • When General Translation Editors are not responding to the Plugins/Themes TE requests on 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/./Polyglots, we should wait for two weeks and if there was no answer add the PTEs to locale and 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.”-back the GTEs.
  • Theme/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. directories
    • Please make sure that Theme Directory and Plugin Directory are translated. The projects are not auto-deployedDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. and you’ll have to request a deployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. for these. The site editors of your locale can send the request.
  • Feedback:
    • @luisrull: It would be great to have a solution where we only have to approve requests for Project Translation Editors.
    • @adrianpop: Is it possible to have the Waiting tab at the end, and to have little badges after each tab name with the number of not-100%-completed projects?

#weekly-meeting-notes, #weekly-meetings

Petya Raykovska 5:48 pm on September 24, 2015
Tags: , , , , , , , , , ,   

Notes from the Polyglots chat on Sep 23rd

  • 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/ stats

    • Releases: 155 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/. 52 locales up to date. 8 locales behind by minor versions. 4 locales behind by one major version. 20locales behind more than one major version. 56 locales have a site but never released. 15 locales don᾿t have a site.

    • Translations: 155 locales. 56 locales at 100%. 4 locales have more than 95%. 7 locales have more than 90%. 20 locales have more than 50%. 54 locales have less than 50%.

      We’re getting close to 60 locales at 100%. We’ve got Hindi, Occitan, Pashto and Spanish (Mexico) at 96-99%, so when those get to a 100% we will have 60 locales at 100%

    • We have 8 locales behind one major version – #ca, #ckb, #fa_IR, #es_MX, #te, #uk, #th, #cy
    • Have a request about an Emoji locale, no one’s willing to translate to Klingon and Pirate 🙂
    • Also two more are waiting to be researched and added this week – I’ll be doing the research and asking @ocean90 to finalise them
  • Tech updates – see #metai18n chat notes
  • Discussion – per locale notifications for GTEGeneral Translation Editor 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. for requests on adding per project TE – agreed 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 should be subscribed automatically to receive pings from #locale mentions on the P2s. There will always be an opt out option.
  • Attention Translation Editors! Set your notification preferences (you have to be logged in first, otherwise the link will get you to 404): https://profiles.wordpress.org/profile/notifications.
    The pound sign (#) in front of the locale name creates a unique stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. that can be followed across WordPress.org. You can follow any unique string by changing your notification settings from your profile page. 
  • Glossaries and style guides – agreed glossaries across projects are a top priority for a GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. feature at the moment and to work on creating an extended general one, using outside resources where needed. See this post for details.

 

#weekly-meeting-notes, #weekly-meetings

Petya Raykovska 3:19 pm on September 20, 2015
Tags:   

Translation style guides on Rosetta sites & Glossaries

Dear polyglots,

I had a chat with @jenia at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Switzerland’s Contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ today about improving the Glossaries and the translation style guides so we can help new contributors get started faster.

Improve the translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins. Glossaries

Jenia and the Global theme at WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/ have an amazing set of Glossaries already built which we can definitely reuse. They have glossaries for 22 languages and I thought that we could reuse them if that’s ok with the 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.

You can check them out at https://en.support.wordpress.com/translation-resources/. They also use GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org., so you can just export their Glossary and import it for your own 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/.

Translation Style Guides on 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. sites

With the upcoming wave of new contributors around plugins and themes, keeping consistency among translations for the same 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/ is essential. It all starts with a good instruction manual, so I thought we could make it a requirement for each team to create at least a short instruction manual with general guide lines for translating.

I know this is a lot to ask and hard work that many of you might be intimidated by. However, we don’t need to invent the wheel. Luckily we already have resources to help us out.

So here are a few resources you can benefit from before building a page

  1. Check out the style guides WordPress.com built for the same 22 languages
  2. Microsoft have super extensive guides for a lot of languages. Those are too long, but might be interesting for many of you anyway. We don’t need such extensive guides. Just general directions.
  3. Facebook have really nice style guides for translating too. They’re shorter and straight to the point.

Including a short introduction page for new translators on your Rosetta sites

Some teams have already done that, but it would be great to include it in most of the Rosetta sites for new contributors.

This is what I think each page should include, but you are welcome to modify depending on your locale requirements:

It would be good to have a discussion about it during the next polyglots chat and leave your comments below with your example pages if you already have one, it would be good to browse ideas and get more suggestions.

Thanks @jenia for all the tips!

Cheers!

Petya

#rosetta

Petya Raykovska 11:15 am on August 17, 2015  

Polyglots Handbook August sprint

Dear Polyglots,

As we head into a new era (plugins and theme in the repoWordPress 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., yay), we will need to improve documentation on how things are done in the team.

I’ve dedicated some time in August for working on the Handbook, but your help will be highly appreciated!

How can I help?

I’m so glad you asked! Here is how:

Read and suggest edits

  • Go to the handbook, read separate sections
  • Suggest edits in this Hackpad: https://hackpad.com/Polyglots-handbook-suggested-edits-5kK1odaUYu9 – suggestions might include changes like the name of the page, certain terms, wrong term corrections, typo fixes, consistency problems with other pages, missing content
  • In the Glossary part of the document, please add all terms that you were not familiar with and always wondered about, so we can explain them better (ex: soft, hard freezeHard freeze See String freeze. A hard string freeze or a hard freeze is announced when all the strings of the upcoming release are frozen including the strings of the About page. A hard freeze is the final string freeze before a release., release packageRelease package A 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., 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/., tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/., 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. trac, glotpressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org.). This is the team’s Glossary – for all terms we, as translators and 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, need to be familiar with.

Test the handbook using a persona

  • As a new translator, just starting to help out – look if it’s easy to understand how to
    • Find 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/ and start translating
    • Understand how your translations get online
    • Understand who is in charge of validating your suggestions
    • Find information about your locale translation editorTranslation 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
    • Contact your local translation editor
    • Contact the polyglots teamPolyglots Team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/
    • Find other polyglots to talk to, understand what channels we use to communicate
    • Become a part of the weekly Polyglots conversations
  • As an experienced translator, wishing to become a part of the translation editor team – look if it’s easy to understand:
    • What is the role of the translation editor
    • How to find out who the other contributors for your locale are
    • How to contact the translation editors for your locale
    • How to ask to become a part of the translation editors for your locale
  • As a new translation editor, who just got in charge of a new locale test if you can understand and enough information on:
    • What is the role of the translation editor and what your responsibilities will be
    • How to setup your local site – translate it, setup the main pages, setup RTL, etc.
    • How to validate stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings.
    • How to use the translation tools provided
    • How to communicate with translators
    • How to communicate with the Polyglots team
    • How to join the weekly chats and what are the communication channels the team uses
    • How a language gets into the WordPress installer
    • How to prepare and release a package
  • As a new contributor for a non exsitent locale who would like to translate WordPress in their language
    • How to request the new locale
    • Who to contact for help
    • What does the role of the translation editor include and what are the responsibilities

These are just some example questions, I am sure a lot of you who have experience with user testing will have more ideas about questions that can be included.

The main structure of the handbook will remain as is now, we can, however, add new pages and sections and expand current sections. The Hackpad includes all current pages – if you have an edit to suggest, please add it as a comment below the page’s name.

Screenshot 2015-08-17 14.10.54

Example of and edit suggestion for a page

If you’d like to suggest new pages, please do it at the bottom of the document below the “New pages suggestions” and provide the path to the new page you’re suggesting. Example: “Setting up your local site > Translating the interface – gives a link to the 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. project and a step by step guide about translating and requesting a deployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. of the translation on the site”.

If you feel you can dedicate more time for this and have sufficient experience with working on the team, please comment below and you can be added as an editor for the Handbook, so you can add and edit pages.

Thank you in advance for your help!

Cheers!

Petya

Petya Raykovska 6:47 pm on August 12, 2015
Tags: ,   

Notes from the Polyglots chat on Aug 12th

Logs: https://wordpress.slack.com/archives/polyglots/p1439373006001227

  • 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/ stats
    • 29 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/ at 100%. 28 locales have more than 95%. 5 locales have more than 90%. 22 locales have more than 50%. 54 locales have less than 50%.
    • 29 locales at 100% is already awesome, it would be great to get the 28 that have more than 95% to 100 before the 4.3 release
    • We’re hoping for 62 locales ready for 4.3, great job everyone
  • WordPress 4.3 translation progress
    • About page stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. are expected any day now, should be tomorrow or the day after
    • When they get in, there will be a translation editorTranslation 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 notification on the blog.
  • Translating themes and plugins – open discussion on adding per project editors and your overall experience
    • Very few people have tried adding project specific 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
    • The process of getting 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. / theme available for translation needs to be documented, so it’s clear what will be available on translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins. and what should plugin authors do to get their product in for translating
  • Handbook August editing sprint progress – the Polyglots handbook will be edited and expanded with new pages and sections.
    • The plan for the edits is here: https://hackpad.com/Polyglots-handbook-suggested-edits-5kK1odaUYu9
    • Feel free to add suggestions for edits and report on problems you find with the current pages
  • WordPress 4.3 video subtitles:
    • Check out Siobhan’s instructions on translating the subtitles for the 4.3 video
    • We will be able to have location specific locales in this time
    • Translating is done via Amara – a translation service and is a lot smoother/easier
  • Open discussion

Next polyglots chat will be next Wednesday, 10am UTC, 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/.

Cheers!

Petya

#weekly-meeting-notes, #weekly-meetings

Said El Bakkali 2:50 am on August 10, 2015
Tags: , ,   

Hello I write here to request a translation…

Hello

I write here to request a translation of WordPress to my local dialect.

I have a team ready and waiting for the request to be accepted to start working.

Our goal is to translate WordPress completely before version 4.4.

I hope you accept my request

Thanks.

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/: ar_MA
Country code: MA
Plural forms: nplurals=6; plural=(n==0 ? 0 : n==1 ? 1 : n==2 ? 2 : n%100>=3 && n%100=11 ? 4 : 5);
Language native name: العربية المغربية
Sub-domain: ar-ma.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 Title: العربية المغربية
Site Description: ووردبريس بالعربية المغربية
Admin Username(s): sa3idho
Admin Email: contact[at]saidelbakkali.com

#locale, #request, #translation

Petya Raykovska 12:40 pm on July 15, 2015
Tags: ,   

Notes from the Polyglots chat on July 15th

  • All TE of 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/ with language variants, please write a request on make/polyglots for the option to be added for 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/. Requests should include a slug (like `formal`), the english and native name of a variant.
  • Let’s document the different language variant usecases we have now, @alvarogois, @dimadin @gluekpress, could you describe your particular usecase and how you have handled things prior to this?
  • A quick reminder you can translate 4.3 stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. in the development project now. The teams page shows the progress of locales on the 4.3 dev branch. This, as mentioned last week, will also give you the opportunity to test translations if you have the 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. tester 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. running in your install
  • Themes and Plugins are coming to the repoWordPress 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. (https://make.wordpress.org/polyglots/2015/07/14/translating-themes-and-plugins/), minimal requirements for TE to be added as per project validators:
    • Description including projects and locales they’re taking care of
    • 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/ name (unless limited by a technical issue)
    • Other means of communication – email, twitter or other social account 
    • GravatarGravatar Is an acronym for Globally Recognized Avatar. It is the avatar system managed by WordPress.com, and used within the WordPress software. https://gravatar.com

  • Plugins and themes who do not want dotorg translations (language packs from translate.wordpress.org) can “opt-out.” The way for them to use their own translations, instead of ones from translate.wordpress.org is to… do nothing. Or, to keep doing what they’re currently doing. Translations that are shipped with themes/plugins take priority to language packs. WordPress will use them first and not download the language pack.

  • We’d love the accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) team’s input on these requirements – Taco to pint Rian for her opinion
  • The process for plugin/theme authors to request external validators for their plugins/themes to be added is described in https://make.wordpress.org/polyglots/handbook/rosetta/theme-plugin-directories/#requesting-new-translation-editors
  • Handbook updates: In august Petya will organise a handbook sprint for all handbook pages that have been reported to have issues. To help this process along, you can either report issues (slack or make/polyglots blog) or if you want to get involved more, request to be added as an editor to the handbook. The translation sprint will have tasks outlined for everyone who wants to join in to claim and work on. 
  • Polyglots teamPolyglots Team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/ volunteers – with a lot more people joining the polyglots community, we need all the help we can get to help people with locale requests, questions, new validators orientation, documentation. If you’d be interested in helping out with any of the tasks below, please raise your hand in the comments:
    • Answering people’s requests on the polyglots 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/.
    • Doing locale research for new locale requests – includes checking the request on the p2 and communicating with the person requesting the new locale, ensuring the ISO-3 codes are correct, adding information about how many people speak the language, double-checking plural forms, creating a ticket on the GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. track with all the information needed to add a new locale. (You will be trained by Petya)
    • Monitoring feature requests/bug reports from polyglots and filing those as issues on 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. track

 

Cheers!

Petya

#weekly-meeting-notes, #weekly-meetings

Petya Raykovska 7:08 am on May 27, 2015
Tags: ,   

Translating documentation

In last week’s Polyglots chat (logs) we briefly discussed translating documentation, how it was done in the past and how it should be done in the light of localizing the 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. and theme directories and making 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/ better fitted for non-English users.

How do we translate documentation now

In the past the Codex has been translated by simply creating new wiki pages and duplicating and translating the content of current pages manually.

The obvious downside of this is that there’s no version control and translators need to check all pages for changes to be able to bring those changes to the translated documents.

Now that Codex is on it’s way to be replaced by the Handbooks, it would be really handy to have those available locally.

So let’s discuss how we can make that happen.

Localizing the handbooks

A couple of options mentioned during the meeting:

“I agree, that it should be handled via WordPress itself, not GlotPress, because you can do quicker previews, add translated screenshots etc. We still can/should show the English text on the same page, maybe side by side so we could track out of date translations.”

  • Adding the handbooks plugin to the 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/ sites so editors can build there own handbooks – the easiest way to go, but would have no version control so will basically replicate the old way of copy pasting the Codex with no way to track changes in the original documents
  • Adding the handbooks plugin to the locale sites and including an “Import original content” with an active relation of each duplicate with the original. A way for the editors to pull changes from the original (doesn’t have to be automatic, can be done manually, just as long as editors don’t have to go check every page for changes).
  • One option is something @zodiac1978 pointed out is already being done on wordpress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/: “I am doing this for the support pages for wordpress.com. They use a plugin which send you an email for every change (with a revision diff view of the changes). Then we have to manually add these changes to our localised post/page. This could be one way. But much work …”

Let’s discuss the options above and see what ideas the #metai18n team will have too.

Cheers!
Petya

#documentation, #translation

Drew Jaynes 7:05 pm on April 15, 2015
Tags: ,   

Hard string freeze is now in effect…

“Hard” string freezeString freeze The term "string freeze" is used by the core team to mark the end of changes to the strings of an upcoming release. A string freeze also means that there will be no more strings added to the core project. Sometimes a string freeze has two phases a soft freeze and a hard freeze. A string freeze is announced on the Polyglots blog by the current release lead. is now in effect for 4.2.

The About page stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. are now available for translation, and we expect to tag RC1 later today.

“Hard” freeze means that all coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and About page strings are available for translation, and all other stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. changes have been frozen beyond this point.

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

#core, #string-freeze

Dominik Schilling 10:24 pm on March 19, 2015
Tags: , ,   

Per-project permissions for Translation Editors (previously Validators)

Author shouldn’t show as validators or be able to validate stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. – Meta Ticket 741

I’m happy to announce that we finally have a more granular system to manange permissions for translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins.. 🎉🎊

Previously anyone with the role of ValidatorValidator See translation editor., Contributor, Author or Editor had the ability to validate strings for a language. Now we have a new role 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. The role is a complementary role and can be assigned to editors, authors, contributors or subscribers.
The Users list table has a new column which will display all roles of a user.

user-roles

Only users with the Translation Editors have the the ability to validate and approve strings. To promote a user to a translation editorTranslation 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 you can use the action link in the Users list table (see screenshot above) or use the new page Users > Translation Editors.

The page is similar to the Users list table but lists only translation editors.

translation-editors

Here you can also add new translation editors. This form allows you to specify for which projects the editor should get access. With All Projects selected, the translation editor will have validation permissions for all projects, including newly-added projects.

If you select Custom you will be redirected to an Edit Translation Editor screen.

edit-translation-editors

Here you can select one or more projects. The list includes all 12 “master projects”. The editor will have access to all sub projects and newly-added sub projects of a selected “master project”.

With this update badges for translation editors are now automated too. ~300 users have already a new badge! 💥
(Badges are visible at profiles.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//yourname)

The migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. process has moved all validators to the new Translation Editor role, same for editors. Users with the Validator role now have the Subscriber role. All translation editors were whitelisted for all projects, which can be changed as needed. Contributors and authors are untouched. Each team should do a case-by-case review if a contributor/author should be able to approve strings.

I hope you enjoy the update as much as I do. 😀
If you have any questions feel free to use the comments or 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.” @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/.

(Badges for translation contributors will come soon.)

#announcement, #glotpress, #rosetta

Petya Raykovska 9:46 pm on February 24, 2015
Tags:   

Polyglots Team Badges

You can find the current profile badge criteria for Polyglots TeamPolyglots Team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/ contribution on this meta team handbook page.

Dear Polyglots,

We’ve discussed Polyglots badges for a while now during weekly chats. As we want to move things forward, we need to make some decisions.

Overview

The current suggestion is that Translation Contributors (translators) and 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 (validators) get a separate badge.

In the weeks and months to come with the expectation for more and more projects in Translate.WordPress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins., we will need to find mechanisms to onboard new Translation Contributors faster and integrate them better into the existing teams.

If badges help this process along, I believe we should try to keep the barrier for getting a translation badge low.

At the same time Translation Editors are dedicating a lot of time and effort to keep translations consistent, they’re actively involved in the Polyglots team and put a lot more time into validating translation suggestions and generally taking care of a 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/.

This is the reason behind the two separate badges for Translation Contributors and Translation Editors.

Things to consider

1. We need a simple automated principle for rewarding a contributor with a badge, manually adding badges will require resources the team doesn’t have. A lot of teams are doing badges manually now for a lack of a better option, but we have a way to reward automatically and it would be great if we could take advantage of that.

2. Current badges don’t have an expiration date for any of the existing teams.

What we need to decide

1. How many approved stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. should a contributor have to receive the Translation ContributorTranslation Contributor Translation Contributors (formerly known as Translators) are volunteers that focus on translating projects into their language. They contribute to improving their language either in a small way, like fixing a typo, or a large way, likes translating entire projects. badge?

2. Do contributor badges need to expire and what would the principle be

Please fill out this two question poll and help us make a decision.

Earlier today Sergey suggested we only have one badge for Polyglots for Translation Editors. If any of you is strongly in favour of this suggestion, please comment below.

Cheers!

Petya

#polyglots

Petya Raykovska 10:26 am on December 17, 2014  

Agenda for the Polyglots chat this Wednesday and Thursday

Agenda for the Polyglots chat this Wednesday and Thursday

As most of us will probably have our hands full with testing 4.1, let’s try to keep this week’s chats short and on the subject

  • WordPress 4.1 will be here on Wednesday afternoon – current status on most 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/
  • Polyglots badges – there’s a suggestion about team badges, let’s discuss it and make a decision so translators and validators can get their contributor badge
  • Open discussion

As always, if anyone has any suggestions for the agenda, please feel free to add them in the comments.

Wed chat, Dec 17 at 11:00 UTC | Thur chat, Dec 18 at 2:00 UTC | #Polyglots Channel on Slack

 

Petya Raykovska 10:38 am on December 11, 2014
Tags: , , ,   

Notes – Polyglots chats on Dec 10 & 11

 Notes – Polyglots chats on Dec 10 & 11

Archive: Wednesday chat | Thursday chat

New information on WordPress 4.1 RC1, string freeze and release dates

  • RC1 is coming on Dec 11th – (there will be a post on make/coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., we will post a channel announcement in 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/ too)
  • Final date for WordPress 4.1 release – Tuesday, Dec 16th
  • Keep an eye on Translate.WordPress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins. in the next three days, the stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. for the About page should get in at some point
  • Stats: 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/ up to date, locales behind and their progress, 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/ requests, new locales:
    • http://wpcentral.io/internationalization/ – let’s aim for at least 43/50 locales to be ready for the 4.1 release, it would be amazing if experienced polyglots kept an eye on the P2 for requests and help build, test and release packages
    • An idea from @nao: maybe we should do a translation sprint for next cycle or something and get translators to get on #polyglots (or even a separate channel exclusively for translation questions)

Hide Windows Phone App from GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org.

  • (thanks to @garyj for bringing it up)
  • @garyj‘s original thought: Propose to drop (hide rather than delete) the WordPress for Windows Phone item off of the https://translate.wordpress.org/languages/en-gb and similar pages. The project is no longer listed on https://wordpress.org/mobile/, hasn’t been updated in the Windows app store (http://www.windowsphone.com/en-us/store/app/wordpress/5f64ad85-f801-e011-9264-00237de2db9e) since June 2013, and the official blog at wpwindowsphone.wordpress.com is closed. We shouldn’t be encouraging folks to spend time translating an abandoned project that is never going to incorporate their efforts into a new release.
  • let’s confirm status on the App with the mobile team and then decide if we want to hide or at least unmark the project as active and add a note in the description that the app is no longer being developed
  • We need guidelines for projects that get into GlotPress

Community hub project & Polyglots

  • @miss_jwo is leading the Community Hub project that has a lot in common with the ideas about Rosetta sites, discussed at the community summit. Let’s see who’s already involved and what the Polyglots teamPolyglots Team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/ can help with. See archives of the Wednesday chat discussion on the subject.
  • A lot of the things on the wish list for the Community hub overlap with ideas about improving Rosetta.
  • A lot of the things are already being done outside the .org ecosystem – on meetup.com and external community sites – let’s help the Community team figure out which features would be needed by voting for them. Is there anyone interested in joining the Community Hub discussion? They can use our knowledge of the existing local sites (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.)
  • It’s a must for polyglots to make use of it over/along with whatever local hub they are already using
  • They’re trying to set a meeting to discuss it. For anyone interested, here’s the Doodle. The Polyglots community leads will coordinate with the team creating the hub. Anyone else interested is more than welcome to participate.
  • @mayuko is going to check if the hub itself is going to be localized.

 

Glossary – let’s communicate it and encourage teams to use it

  • Glossary: Talked about a ticket regarding to the glossary #361 (Glossaries should be by locale instead of by project).
  • Japan and en-au sets a master and export/import to other projects when something added/changed, which is pain. It’s much easier if we have it per locale. We pass it forward to the next “Technical Polyglots Meeting”.
  • A new handbook page “GlotPress Glossary Feature” has been added by @nao
  • We can add an instruction for import/export of Glossaries there as suggested by @deconf

Open discussion

Next scheduled chats will be on Wednesday, Dec 17 and Thursday, Dec 18.

Meanwhile if you need help with incoming translations, packaging and releasing translations or GlotPress, there’re always people available for advice at the #Polyglots slack channel. Don’t be shy to ask 🙂

Cheers!

Petya & Shinichin

#polyglots-meeting, #weekly-meeting-notes, #weekly-meetings