Tag Archives: i18n

Samuel Sidler 5:33 pm on July 20, 2015
Tags: i18n,   

Translation Project Sorting Ideas

We’ve been collecting some ideas for sorting all of the projects that are being imported (themes and plugins). I want to collect some of the ideas here, along with my thoughts on them. If you have other ideas, we’d love to hear them!

  • Prioritizing by popularity: Projects could be organized by how popular they are, that is, how many users and/or downloads they have. For translators, the projects that are used the most by users are often considered the most important.
  • Prioritizing by fewest strings remaining: If a project is almost complete – e.g., just a few strings away – it can be considered higher priority. By enabling this option, we’d give translators a way to complete more projects faster. Personally, I think this is better than doing by percentage because 1 string remaining in a project of 10 is fewer than 10 strings remaining in a project of 1000, despite the latter being a lower percentage.
  • Prioritize by permissions: If a translator is the translation editor for a specific project – or a few specific projects – we could show those projects first, since they have permission to approve translations for that project.
  • “Hide” fully translated projects: If a project is fully translated and strings are fully approved, we could “hide” those projects or at least put them at the very bottom of the list. For themes and plugins, this will put them on the last page of results. Searching will still find them, of course.
  • Starring or Favoriting: Everyone has one or two themes/plugins that they really love and want to see available in their language. Giving translators the ability to “favorite” a project and have it raise to the top would make it easier to keep track of new strings in their favorite projects. We could even create a new “tab” for “Favorites” that could be the default if a translator has favorites.
  • Sort by waiting: Translation editors should be able to see which projects have waiting strings so they can approve them. Within this view, we should probably prioritize projects based on some of the ideas above.
  • Improved search: Translators should be able to search by author name (theme or 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 see a list of their projects, for example.
  • Consider “alerting” when changing a translation: It’s hard to explain this, but if I, as a translation editor, change the translation of “gallery” in one project, GlotPress should alert me to the fact that other projects have a translation of “gallery” that is the “old one” and possibly even offer to update all projects with the new translation.

The ideas above are just that: ideas. We may not implement any of them or all of them. But it’s important to list them and think through how we can improve the translation experience.

What other ideas do people have on sorting, prioritizing, and generally improving the translation experience of translate.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/?

#i18n, #translations

Samuel Sidler 10:50 pm on July 14, 2015
Tags: , i18n, , , , ,   

Weekly i18n Chat Notes – July 14, 2015

We had our weekly chat today and talked about a few things.

  • Forums: We’re still waiting for one issue to get fixed in bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org. before we can enable initial forums for the Italian community.
  • Translate: Lots of great progress.
    • Design implementation is done.
    • Paging is done. Basic search is part of it as well.
    • Import scripts are done for themes and in-progress for plugins.
    • @dd32 tested an import of all themes and it works! 🎉
    • Role 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 design changes are still pending, but the design is ready, so it’s just a matter of implementation.

Because of the progress on themes, we think we can do the initial import for themes very soon. It’s know that there will be issues, especially in categorizing and sorting through all ~1500 active themes that will be imported. We’ll work through those issues, fix them, and be ever-more ready for plugins.

Also, because we’re so close, I posted on make/polyglots and make/themes to give them the heads up and added some documentation to the translator handbook to walk through how some of this will work on their end.

As we get closer to the initial import of plugins, there will be a post on make/plugins and we will email plugin authors ahead of time, with a specific date, so they have an opportunity to commit any missing translations to SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/..

(See also: the meeting notes from last week.)

#forums, #i18n, #l10n, #meeting-notes, #plugins, #rosetta, #themes

Samuel Sidler 11:02 pm on July 10, 2015
Tags: i18n, , , , ,   

Plugins, Themes, and Translate.WordPress.org

As mentioned a few times, we’re going to be enabling the translation of active plugins and themes in the 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/ repositories on translate.wordpress.org. Today, we had a chat in #meta-i18n (logs) about how the non-technical side of this will work.

As a quick recap: We’re making good progress on the relevant pieces of Rosetta, GlotPress, and all the related scripts needed to import plugins and themes that are in the WordPress.org directories into translate.wordpress.org and make them available for translation. Every 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 will then be able to take advantage of languages packs, meaning no more delay in language updates and smaller plugin downloads.

Here are a few of the points we discussed on how this process will work:

  • Eventually, all active themes and plugins in the WordPress.org directories will be imported into translate.wordpress.org and made available for translation. The “eventually” is important to note as we will be importing a few at a time to ensure GlotPress can scale accordingly. It’s also important to note that “active” is a theme or plugin that has been updated in the last year. Further, even plugins and themes that are not i18n-ready will be imported so that their descriptions can be translated.
  • Additionally, any plugins or themes that do not live in the WordPress.org directories will not be allowed on translate.wordpress.org. For example, commercial plugins.
  • During the initial import, we intend to import all strings – included translations – directly from the plugin’s svn repository on WordPress.org. We will not continuously import these strings, however. Ideally, after the initial import, a plugin would then delete the strings from the svn repository, making their download smaller and immediately taking advantage of the language packs generated by translate.wordpress.org.
  • For a language pack to be updated, the string must be updated in translate.wordpress.org.
  • The above point means that if a theme or plugin author uses a different site for translations, those translations must be brought over to translate.wordpress.org. If the theme or plugin has an active translation community, they can work with the polyglots team to bring translation editors over to the community. These translation editors can be limited to specific plugins, at the discretion of the locales translation editors. These translation editors can import strings for the plugin/theme, should they wish to continue using a different site for translations. (When we get closer to this, I’ll create a sample post that theme and plugin authors can use.)

That’s a lot to take in, so please let it digest. 🙂

One thing we also discussed was the possibility of enabling GlotPress installations to “talk to” each other, such that translate.wordpress.org could import strings from another GlotPress site (for example, translate.yoast.com), whether as a feature of GlotPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. or a plugin. Currently, this is an open question. We plan to discuss the technical questions of this possibility at next week’s #meta-i18n chat (Tuesday, July 14 2015 11:00 UTC). Note that we will not wait for this feature before continuing with our planned import.

A few other notes:

  • We discussed the possibility of adding a banner to the specific plugin/theme’s page on translate.wordpress.org pointing the external site where translations are active, should a plugin/theme not use translate.wordpress.org as the canonical source for their translations. Currently, I believe the answer is “no banner” but it’s a conversation we should have and re-evaluate over time.
  • Outside of that, it occurred to me after our chat that we will need to add translation editors to the relevant theme/plugin page. For example, if a translator editor only has permissions to approve translations for Hello Dolly, we should note that on the Hello Dolly page within translate.wordpress.org. Example: “Strings for [project name] are approved by the German translation editors [link], as well as username, username, and username.”

If you’re interested in any of this topic, we’d like to get some feedback on any/all of the above. Please leave your comments here, not in #meta-i18n, so others can see your feedback. We’re especially interested in feedback from plugin and theme authors who do not currently have translations and one’s who use an existing product for their translations.

#i18n, #meeting, #plugins, #themes, #translations

Samuel Sidler 1:36 pm on July 7, 2015
Tags: , i18n, , , , ,   

Weekly i18n Chat Notes – July 7, 2015

After a four week hiatus (!) we had our weekly i18n chat today. We’ll be continuing these chats every week on Tuesday 11:00 UTC 2015, just like before.

This week, we discussed the following:

  • Forums: While the bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org. 2 forums aren’t quite ready yet (literally no plugin has been ported to bbPress 2 yet), we’re going to move ahead anyway. @ocean90 is going to work on setting up forums for the Italians within the next week, but is running into permissions issues with bbPress.
  • Translate: @ocean90 implemented most of the @isaackeyet‘s design for translate.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/. With the new designs, there’s only a handful of technical things left before we can start adding additional plugins or themes:
    1. Finish design implementation: The big piece that’s left is adding the sub-project drop down in the top right box, which is needed to allow switching between sub-projects. Additionally, a green outline needs to be around the box if a project is at 100%, but this isn’t blocking anything.
    2. Paging. Without paging, the list of plugins will grow unwieldy. @dd32 is going to work on paging (which needs to be done here).
    3. Roles 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 Changes: The roles plugin won’t scale if we add hundreds (thousands!) of new projects. We need a UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. here – designers wanted! See #1101.
    4. Search: Not needed for an initial import of the top n plugins, but required for when we add all plugins. We’re putting this on hold for now as paging will suit our needs for the foreseeable future.

Beyond the technical list above, we need to talk about how plugins will be imported. Let’s chat this Friday July 10 13:00 UTC 2015 about importing plugins into translate.wordpress.org. If you’re interested in this topic, join us in #meta-i18n.

(As a reminder, all WordPress community meetings are listed on the meeting calendar.)

#forums, #i18n, #l10n, #meeting-notes, #plugins, #rosetta

Samuel Sidler 10:00 am on May 19, 2015
Tags: i18n, ,   

Weekly i18n chat

Just a reminder that the weekly i18n chat will happen in 1 hour from this post at 11:00 UTC. If you haven’t joined us before, we discuss progress on a number of fronts for i18n on 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/. We’ll likely be discussing the forums plugins audit today, in addition to other things, so read through that post ahead of time.

#i18n, #l10n, #rosetta

Samuel Sidler 11:47 pm on April 20, 2015
Tags: i18n, ,   

Weekly i18n Chat

As a reminder, we have a weekly i18n chat this coming April 21st, at 11:00 UTC, which is just over 11 hours from now.

Last week, we discussed a number of things, but mostly forums and Rosetta generally. There was no direct outcome last week, except that we will be setting up individual sites for each part of “Rosetta.” That is, the theme directory on de.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/ (for example) will be its own WordPress site, while a local P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. will be its own site.

We did go into depth on the forums a bit. The next steps there are:

  • Port bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org. 1.x plugins to bbPress 2.x
  • Turn on bbPress 2.x site for a locale and test

The plugins (which are currently private) changed hands to bbPress developers shortly after last week’s chat.

#i18n, #l10n, #rosetta

Stephane Daury (stephdau) 8:11 pm on April 7, 2015
Tags: chat, i18n, ,   

Internationalizing it all

There are a number of internationalization projects going on towards localizing most of our web properties, along with providing localized assets for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. users (localized plugins, etc).

I have and am working on providing a translation platform for all plugins (code and readmes), and the related internationalization of the plugins directory and APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways..

@nacin has done some work on being able to install plugins (and themes?) in the same locale as a WordPress install, when set.

I’ve read that @dd32 has been looking into translating the new themes directory (info in theme headers, from styles.css) and probably API.

@samuelsidler (who is away this week) and I would like to organize a general chat in #meta-i18n sometimes during the week of April 13th, so we can map out everything in front of us, and push on all of them together.

To be discussed: Rosetta, forums, theme directory, 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 directory, themes, plugins, local P2s, GlotPress (soft and install).

Chat date/time suggestions: April 14th, at 2000 UTC (same time range as core chat, 1 day before).

cc @obenland, @ocean90

#chat, #i18n, #l10n, #rosetta