Author Archives: Chris Trynkiewicz (Sukces Strony)

Chris Trynkiewicz (Sukces Strony) 5:48 pm on February 9, 2019
Tags:   

Ability to temporary block translators who submit garbage

I’m not sure if this is the case only for my 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/, but lately there’s been more & more submissions that are obviously just imported *.po filesPO files PO files are human readable files which contain translations we use. These files are not used by WordPress itself. Each language will have its own PO file, for example, for French there would be a fr_FR.po file, for german there would be a de_DE.po, for British English there might be en_GB.po., which were translated using Google Translate and with no further inspection.

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 / theme authors think that someone did a great job and ask for PTEProject Translation Editor A Project Translation Editor (often referred to as PTE) is a person, who has access to validate strings on a specific project (for example BuddyPress, WooCommerce or Twenty Fourteen) for one specific locale. A project translation editor can approve strings that are added by translation contributors. Per project translation, editors are appointed by a general translation editor after a request by the project author or by the contributors themselves. rights for such a person.

As most stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. are short, about 50% of such translations are correct, while the rest is garbage – totally wrong even for really easy & obvious strings (example: “Dashboard” was translated to “Dashboard of a car” in my language). That aside, no PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. context is considered for such translations.

This means that reviewing such submissions requires literally making the translation from the start, reviewing the context, fixing the lost letter capitalization, correcting inconsistencies. A 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. would therefore do the translation as if there was none. This does not help, it actually takes up the GTE’s and project author’s time. This is the opposite of what helping in translation is.

If such garbage is submitted and it’s obvious that it’s an automatic translation (not just a case of not sticking to the conventions), I myself reject all Waiting strings submitted by such a user for that project.

Here are my requests:
1. Easy: somewhere near the *.po import buttons, place a warning saying “If you submit a translation which was done automatically (like using Google Translate) and isn’t manually corrected, ALL the strings will be rejected, even if a lot of them came out correctly. If you did the whole translation manually, you don’t need to worry.”. Maybe even warn: “You will be blocked from further submission to all projects for 2 weeks.”.
2. Enable the GTEs to actually blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. translation submission from such accounts, for 2 weeks seems fine.
3. Enable GTEs to bulk-remove all non-accepted translations made by a user for all projects at once.

#request

Chris Trynkiewicz (Sukces Strony) 11:37 pm on July 6, 2018
Tags:   

Too many emails that don’t concern most GTEs

With the translation community growing, by subscribing to 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/. we, the GTEs, are getting more & more emails that don’t apply to our language. Currently I’m getting about 10 emails a day, with only 1 out of 20 concerning my language. I’m sure others also get irrelevant messages.

Though, subscription is needed to get important emails targeted to all GTEs (not having 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/ hashtag).

This is becoming more and more of an issue, taking up time of all 1000 subscribers to go through emails that don’t concern them. Every day. It’s discouraging and time is being wasted (which could be put into translation). Furthermore, it’s unscalable.

I feel like editor requests need to be taken out of p2 to a separate system. Or a simple JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. code that requires that a post has either an announcement or locale hashtag, but then the subscription box is not needed any more and we all only get notifications by hashtags (which would require some coding to add announcements and locale hashtags for all GTEs).

Hopefully we can find a better solution to make our lives easier 🙂

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.” @petya @ocean90

#request

Chris Trynkiewicz (Sukces Strony) 8:18 am on June 23, 2016  

New string up for translation in WordPress 4.5.3

Due to a seeming mistake WP 4.5.3 introduced a new stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. up for translation:
https://translate.wordpress.org/projects/wp/dev/admin/pl/default?filters[status]=either&filters[original_id]=2998716&filters[translation_id]=43663861
(if using this URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org, change “pl” to your language; otherwise find the string in the directory: 4.5.x / Administration)

This new string is exactly the same as the one already existing in previous and current WP versions ( https://translate.wordpress.org/projects/wp/dev/admin/pl/default?filters[status]=either&filters[original_id]=27222&filters[translation_id]=1259303 ) – only the %1$s was mistakenly typed in by someone as %s, so a new string was generated. The %2$s was left unchanged,.

You can translate this extra string. It should remove itself with the next WP version (assuming someone changes back %s to %1$s).

Chris Trynkiewicz (Sukces Strony) 10:02 am on August 16, 2015  

Local WordPress News in Dashboards

During the last polyglots chat a seldom known feature has been brought up – *WordPress in all languages can have the WordPress News widget in the Dashboard display news from local sites (like http://pl.wordpress.org).*

This wasn’t really documented anywhere AFAIK so *plase push this post to the handbook*. The 2 stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. described below should also have comments added, which I ask anyone to do.

In every install of WordPress there’s a WordPress News widget in the Dashboard (you can show and hide it under the Screen Options), which always displays 1 expanded, most recent post from the 1st RSS feed source (by default: blog post from https://wordpress.org/news/) and 3 post titles from the 2nd RSS feed source (by default: blog posts from https://planet.wordpress.org/).

You can change both of those RSS feedRSS Feed RSS is an acronym for Real Simple Syndication which is a type of web feed which allows users to access updates to online content in a standardized, computer-readable format. This is the feed. URLs to fetch news from other sources, like your local WordPress website.

The 2nd site is a “Planet” service, which is an automatic aggregator of blog posts from various WordPress sites. It’s not very likely that you have a Planet set up for your language – if not, you can eighter create it or provide the same URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org for both sources, which results in 1 expanded post from that feed and – below – 3 most recent blog posts from the same feed (1st of which will be the same as the expanded one, but it’s the best option we’ve got). You can also set the 2nd feed URL to the English 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/ blog, but then the expanded post will be in your local language, and 3 post titles that follow will be in English. It’s your call.

To set the feed URLs, go to https://translate.wordpress.org/ and navigate to your language. Then, you will see all currently maintained versions of WordPress. Do the following steps for *all versions:* click the title that represents a version -> Administration -> Filter -> type “feed” in the Term field -> click the Filter button -> scroll down to see 2 strings that are URLs of feeds.

*Note:* do NOT set the translation of these strings to an empty string, a space bar, a # sign or the URL of your local WordPress site (like http://pl.wordpress.org for Polish). Read on.

The original “https://wordpress.org/news/feed/” string is the 1st described feed source. The 1st post from it is displayed in the Dashboard widget, in an expanded fashion. You most likely want to set this to your local, official WordPress site feed URL. Navigate to your local WordPress site to discover this URL (you might need to search for it in the site’s source code in the head section). For Polish, the feed URL is https://pl.wordpress.org/feed/

The original “https://planet.wordpress.org/feed/” string is the 2nd described feed source. The 3 most recent post titles from it are displayed in the Dashboard widget. You can translate this string to any other RSS or Atom feed URL. You most likely want to consider using:

  • a Planet for WordPress feed in your language, if there is one,
  • the same URL as for the 1st feed source, so pointing to the local WordPress.org site feed,
  • the feed for the official English WordPress.org blog, which is: https://wordpress.org/news/feed/
  • leaving the English Planet URL feed as it was: https://planet.wordpress.org/feed/

Remember to change these for all current WordPress versions, as described above.

After approving the stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. change, wait about 12-24 hours for translation propagation. After you update your translation files in WordPress, see if it works. If you still see the news in English, wait another 12 hours for the caching mechanism to refresh that content.

Chris Trynkiewicz (Sukces Strony) 11:52 am on August 12, 2015
Tags:   

Translating update announcement posts

TLDR:
1. Please make the new version announcement post content (HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites.) available for translation before launch.
2. Please change the list of changes link in the WP admin -> Updates section to the announcement post.
3. Try to make the announcement post link redirect to a local 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. translation of it if available.

Main idea: With incoming WP versions, it would be great if we could also have the announcement post content (HTML) available for translation, so that when a new version launches, we just push the Publish button. Thanks to that, whenever a new version comes, there’s already an announcement post in local languages ready for people to see.
An idea for automation in the future: It would be even better if the local Rosetta sites would have a dropdown menu 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 could choose, which English 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/ blog post is the current post a translation of (like in WPML), even if its status is set to Draft. Then, publishing the main English post would also publish all connected posts which have a status of “Auto-publish with original post” (a new status would have to be created).

2nd thing: in the WP admin panel, there’s a notification with each new version available. Under the Update section, there’s a link to the English wordpress.org site for a list of changes. That post is technically translatable (example: https://codex.wordpress.org/Version_4.2.4 ), but the languages menu isn’t clearly visible and people are likely to leave when they see English instead of their local language. Another issue is that this is a highly technical post, not user-friendly like the announcement posts. We should change this link to the announcement post, would be great if it could even be a localized version from Rosetta sites.
For this to work with Rosetta sites, we would have to have a small script which could check a database for local translations of the announcement post, and – if they exist – redirect accordingly. A simple implementation would require Translation Editors to add the URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org manually, while a more automated solution would have to implement the dropdown translation menu, which is described above.

Maybe there’s an easier way to get all these things to work. Open for discussion.

#request

Chris Trynkiewicz (Sukces Strony) 11:20 am on January 21, 2015  

With the translation auto update in play I…

With the translation auto-update in play, I assume backups of translations are being made and kept for a period of about 1 week to account for hacked validatorValidator See translation editor. accounts which could mess up stuff? This didn’t happen, just asking.

Chris Trynkiewicz (Sukces Strony) 9:45 pm on December 21, 2014  

Hey can we have these blog styles implemented…

Hey, can we have these blog styles implemented on language-specific sites? https://wordpress.org/style/blog-wp4.css?ver=12
Would help a lot.

Chris Trynkiewicz (Sukces Strony) 8:54 pm on December 15, 2014  

@nacin We still have a few strings that…

@nacin We still have a few stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. that aren’t translatable.

https://core.trac.wordpress.org/browser/trunk/src/wp-admin/about.php#L94
https://core.trac.wordpress.org/browser/trunk/src/wp-admin/about.php#L99
https://core.trac.wordpress.org/browser/trunk/src/wp-admin/about.php#L103
https://core.trac.wordpress.org/browser/trunk/src/wp-admin/about.php#L124

What about them for 4.1?

Chris Trynkiewicz (Sukces Strony) 6:32 pm on September 13, 2014
Tags: ,   

We have a situation for pl PL Polish…

We have a situation for pl_PL (Polish). It seems that for a couple of hours (around 1:30 to 3:30 GMT 12. Sept.) the translation files were messed up. If WP auto-downloaded them during this time, the main translation admin-pl_PL.po (and .moMO files MO, or Machine Object is a binary data file that contains object data referenced by a program. It is typically used to translate program code, and may be loaded or imported into the GNU gettext program. This is the format used in a WordPress install. These files are normally located inside .../wp-content/languages/) would have a few hundred bytes instead of kB. The admin-pl_PL.po was not possible to open. Also, the multisiteMultisite Multisite is a WordPress feature which allows users to create a network of sites on a single WordPress installation. Available since WordPress version 3.0, Multisite is a continuation of WPMU or WordPress Multiuser project. WordPress MultiUser project was discontinued and its features were included into WordPress core.https://codex.wordpress.org/Create_A_Network. translation files for 4.0 weren’t downloaded. It was a mess, resulting in half of the admin panel defaulting to English.

After those 2 hours, the translation files seemed to refresh and WP installs that made updates later on were fine. The ones that dl-d the bugged files did not update them, however.

We need someone ( @nacin @ocean90 ) to push an update. Probably just changing the update date in https://api.wordpress.org/translations/core/1.0/?version=4.0 should work.

The maintainer of the pl_PL translation will confirm this below.

#pl_pl, #request